Quiz
2667 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.
All areas2667
Architecture Fundamentals81
Distributed Systems101
Data Architecture90
Cloud Architecture87
Networking86
API & Integration Architecture78
Reliability & Resilience88
Observability81
Performance & Capacity Engineering90
Security Architecture95
Cost Architecture & FinOps92
Business Architecture93
Architecture Communication91
Enterprise Architecture91
Legacy Modernization92
AI-Era Architecture86
Software Architecture & Engineering84
Architecture Patterns84
Architecture Decision-Making91
The Architect's Meta-Skills92
Delivery & Release Engineering93
Platform Engineering & Developer Experience92
Testing & Quality Architecture90
Data Platform Architecture88
Streaming & Real-Time Data93
Data Governance & Semantics81
Frontend & Experience Architecture91
Edge, Mobile & IoT88
Regulatory & Data Protection Architecture90
Assurance, Audit & Model Risk88
5 questions in Saga.
-
Saga advanced
A multi-party booking saga is running in production and support cannot answer where a particular booking is. What is missing from the implementation?
2 min answer shiprocketsagaobservabilitystate -
Saga advanced Multiple choice
An order flow spans several services and cannot use a distributed transaction. What decides between orchestration and choreography for the saga?
2 min answer sagaorchestrationchoreographycompensation -
Saga advanced
An order spans payment, inventory and shipping, each in its own service with its own database. How do you keep them consistent?
3 min answer sagaconsistencycompensationoutbox -
Saga advanced
Design an order saga: reserve inventory, take payment, dispatch shipment, send confirmation. What ordering problem do you see?
2 min answer sagacompensationdesign -
Saga intermediate
Review this. A grocery-fulfilment platform in the mould of Instacart runs an orchestrated saga over five steps - cart freeze, pricing, promotion, loyalty accrual, order creation - each with a compensating action, driven by an orchestrator with its own saga log. All five services are owned by one team, deployed as one binary, and write to five schemas in one Postgres cluster. What would you remove, and what would you leave alone?
3 min answer sagacompensationtransactionssimplification