Design / A decision workbench

Let constraints
shape the system.

A good architecture starts with better questions. Describe your context. Explore the trade-offs. Find a direction worth testing.

CONSTRAINTSREASONINGDIRECTIONAuthored rules. Transparent choices.

Your system brief

Start with your reality.
Change one constraint.
See what follows.

Every input is editable.
Nothing is sent to a server.

Step 01 of 03

Start with the people.

Architecture has to fit the team that will build and operate it.

How big is the team?

People actively building and operating this system.

Small1–8 peopleMedium9–30 peopleLarge30+ people

How complex is the domain?

Business rules and boundaries, rather than lines of code.

SimpleOne clear purposeModerateSeveral capabilitiesComplexMany business contexts

How mature are your operations?

Be honest about the capacity available for production.

DevelopingBasic deployment & logsEstablishedCI/CD, metrics & on-callAdvancedPlatform & incident practice

What are you building toward?

Organizational reach is different from request volume.

One productMultiple teamsAn ecosystem

Sensible defaults. Make them yours.

Software architecture, made visible.
A free, independent project by Abel.

An independent project about how software systems behave.