Centralised vs Distributed
Shared platform leverage against team autonomy.
5 to work through
-
intermediate
When is a centralised architecture with a single relational database and vertically scaled application the right answer?
2 min answer -
advanced
A marketplace expanding across cities must decide what is centralised and what is devolved. What principle draws the line?
2 min answer -
advanced
Eight product teams each call a shared entitlements service on every request. A four-person platform team owns it. It measured 99.95% availability over the last year and answers in 8 ms at p99. Leadership now wants feature-flag evaluation moved into the same service because it would be one place to change. What does that centralisation buy, and when does the bill arrive?
2 min answer -
advanced
Lyft open-sourced Envoy in September 2016 after running it internally, moving retries, timeouts, service discovery and network telemetry out of its services and into a sidecar proxy. Which problem did centralising the network layer solve that a shared client library could not, and what did the sidecar cost?
2 min answer -
advanced
When does a shared platform stop helping and start constraining, and what signal tells you?
2 min answer
2 terms in this topic
Centralisation Trade-off
The exchange between consistency and control gained by centralising a capability and the autonomy and speed retained by distributing it.
conceptCentralised versus Distributed
Whether a capability should be one shared thing or many independent ones — a recurring decision whose answer changes with organisation size.
Neighbouring topics
Architecture Decision-Making
General material on making and recording architectural decisions.
Architecture Decision Records
One decision, its context, alternatives and consequences, kept immutable.
Reversibility
One-way and two-way doors, and buying optionality deliberately.
Build vs Buy
Differentiation, five-year TCO, and the exit cost of each option.
Monolith vs Microservices
A team-topology decision far more often than a technology one.
SQL vs NoSQL
Decided by access patterns and query flexibility, not by data volume.
Sync vs Async
Whether the caller's outcome depends on the callee's response.
Strong vs Eventual Consistency
A per-operation decision, resolved by what a stale read would cost.
Managed vs Self-Managed
Trading control and unit cost against operational attention.
Serverless vs Containers
Spiky and event-driven versus sustained throughput.
Single vs Multi-Region
Driven by RTO, RPO and residency rather than by ambition.
Performance vs Cost
Buying latency, and knowing what the last millisecond is worth.
Reliability vs Complexity
Mechanisms that add availability and add failure modes.
Security vs Usability
Varying control by the value of the action rather than uniformly.
Delivery vs Maintainability
Fast in the cheap places, careful in the expensive ones.
Deciding Under Uncertainty
Bounding the downside and buying information cheaply.
Trade-off Analysis Methods
ATAM, scenarios, and naming the points where qualities conflict.
Technology Selection
Evaluating options against drivers rather than against enthusiasm.
Decision Practice
Thresholds, review, supersession and keeping the log alive.