Decision tools
Most architecture choices come down to a handful of questions about your team, your data and your constraints. These tools ask those questions and explain what follows from your answers. They run in your browser; nothing you enter is sent anywhere.
Decision guides
Section titled “Decision guides”| Guide | It helps you decide |
|---|---|
| Monolith or microservices? | Whether to build a modular monolith, extract a few services, or go fully to microservices |
| Which messaging style? | Whether two systems should use a direct API call, a work queue, publish/subscribe events or an event log |
| Which data platform? | Whether you need a data warehouse, a data lake or a lakehouse, and whether data mesh fits your organization |
| Find your architect path | Which kind of architect role suits you |
References and templates
Section titled “References and templates”| Tool | Use it to |
|---|---|
| Cloud service map | Find the equivalent service on AWS (opens in a new tab), Azure (opens in a new tab) and Google Cloud (opens in a new tab), plus an open-source option |
| ADR generator | Write an architecture decision record and download it as Markdown |
How to use the results
Section titled “How to use the results”A guide’s recommendation is a starting point. It can’t see your organization’s history, skills, contracts or politics, all of which matter. Use the result to structure a discussion with your team, then record the decision and its reasons in an architecture decision record so the next person understands why.
Written and edited by Abhinav Taduka, enterprise software architect.