Find a lesson, question or project

Start typing to search published content and planned structures.

↑ ↓ moveEnter openEsc close

SYSTEM DESIGN / DECISION LIBRARY

Choose architecture from constraints, not habit.

This is the structure for concise decision guides. The comparisons are planned and will become available as each guide is researched and reviewed.

01 Context02 Constraints03 Options04 Benefits05 Costs06 Failure behaviour07 Decision checklist

PLANNED / 10 GUIDES

Decisions the library will cover.

Planned items are intentionally not links. They will become clickable only when a complete guide has been published.

01PLANNED

SQL vs NoSQL

Which data model and guarantees fit the access pattern?

Relational databaseNon-relational database
Decision factorsrelationshipstransactionsquery patternsscale
02PLANNED

REST vs messaging

Should the caller wait for the work to finish?

Synchronous APIAsynchronous message
Decision factorscouplinglatencydeliveryfailure
03PLANNED

Cache-aside vs write-through

Who owns cache population and consistency?

Cache-asideWrite-through
Decision factorsread ratiostalenesscomplexityfailure
04PLANNED

Strong vs eventual consistency

How soon must every reader observe a write?

Strong consistencyEventual consistency
Decision factorscorrectnesslatencyavailabilityconflicts
05PLANNED

Horizontal vs vertical scaling

Should capacity grow through larger machines or more machines?

Scale upScale out
Decision factorslimitscostavailabilityoperations
06PLANNED

Replication vs partitioning

Is the primary pressure availability, reads or total data size?

ReplicatePartition
Decision factorscapacityfailoverhotspotsrebalancing
07PLANNED

Offset vs cursor pagination

How should clients move through a changing result set?

Offset paginationCursor pagination
Decision factorsconsistencyrandom accessquery costAPI design
08PLANNED

Optimistic vs pessimistic locking

How likely is concurrent modification?

Optimistic lockingPessimistic locking
Decision factorscontentionretrieslatencycorrectness
09PLANNED

Monolith vs microservices

Does distribution solve a current organisational or scaling constraint?

Modular monolithMicroservices
Decision factorsteam boundariesdeploymentdata ownershipoperations
10PLANNED

Round robin vs least connections

Are requests similar enough to distribute evenly by count?

Round robinLeast connections
Decision factorsrequest durationserver healthstatefairness