Table of Contents
Stackitecture draws all of the major cloud components from Amazon Web Services.
If you were building a home, creating it from scratch without any architectural plans would be risky. The plans are important for a lot of reasons. Starting out, they enable quick iteration on the key services and components you’ll need for your application. They also enable cost estimation and basic “what if” analysis to see what your operational spend will be for various loads.
Plans also enable coordination between various teams – without a map of what’s being built, it’s hard to determine who’s doing what and when.
Example Use Cases
The following are examples of use cases where Stackitecture can provide value:
Every development team runs on hiring the best talent, and once you have those folks hired, you’ll want them to be as effective as possible in the least amount of time. Understanding the overall architecture enables quicker onboarding.
You can use Stackitecture to help determine vulnerability, encryption, and privacy concerns. It may be necessary to show that the logs are access controlled and least privilege is setup such access to production data is secure.
An audit may need to be done to make sure that services utilized are covered under a Business Associates Agreement (BAA) and that the architecture supports HIPAA regulations.
The system that is being built will need logging, monitoring, alerting, and observability integrations and diagnostics to enable realtime monitoring for site reliablity teams and production support.
An architectural model can callout integrations with external services that might be used for customer enagement and analytics.
Data Science / Analytics
It’s important to know how the system is setup and how data flows through the system, possibly into a data lake, so that analytics can be setup to enable application measurement and customer analytics.
Customer Engagement & Success Teams
A high level view of the system enables customer discussions for nontechnical customer success teams.
Understand what’s being tested, what needs to be tested, and what a test environment setup would be needed to replicate the system.
It’s easier to setup either a cold standby, a pilot light system (warm standby), or an active-active system to minimize the amount of downtime an application may have during an outage.
An overall view of the system will help the incident response teams as they “fight” the incident and work to get the system back online as fast as possible, reducing the mean-time-to-recover (MTRR).
How to Buy
Currently, Stackitecture is available on the MacOS App Store. You can download the free trial and choose one of the following:
- Test Drive - this includes the ability to use all of the app, but you can’t save files.
- LT Monthly Subscription - This is a monthly subscription to all light features in the application.
- LT Yearly Subscription - This is a yearly subscription (at a discounted rate compared to purchasing all months on the monthly plan).
Major Parts of Stackitecture
Stackitecture is composed of four major parts:
- Model Browser - the Model Browser displays the Stackitecture model as you’re building it. You can select components via the Model Browser and inspect their data.
- Component Palette - the Component Palette contains all the stock components that can be put on the canvas
- Canvas - the Canvas is the drawing part of Stackitecture. Aside from components, you can also add graphical shapes and text to help you with creating your model.
- Inspectors - these let you see data on the components and graphical objects on the canvas. For graphical objects, you can change the stroke and fill settings. For text shapes, you can change the font settings.
Ability to Save Files Locally
Stackitecture saves all files locally, under your direct control. You can choose to save them to any device or service under your control (e.g. external drive, iCloud folder, etc.). It is very important for us that our customers be able to maintain custudy of all their intellectual property. Other cloud drawing tools require that you either trust them to not inspect your files or they require you to constantly manage uploading and downloading your files. Our approach means you can use all your normal tooling (like encrypted hard drives) and it’s your choice as to who has access to your data.
The list of all releases is documented in our Release Notes document.
If you need more help, please see our Help documentation (which includes who to contact for additional help).