Portfolio ↗

Quiz

2988 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 areas2988 Architecture Fundamentals91 Distributed Systems111 Data Architecture100 Cloud Architecture97 Networking96 API & Integration Architecture97 Reliability & Resilience99 Observability92 Performance & Capacity Engineering100 Security Architecture105 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization102 AI-Era Architecture106 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

5 questions in Legacy Integration Patterns.

  1. Legacy Integration Patterns intermediate

    A fourteen-year-old policy system sustains roughly 350 transactions per second at its measured peak and the business peak already consumes about 260 of them. Four new services want to call it directly. Roughly how much of that system can you sell them, and what does the number decide?

    3 min answer legacy integrationcapacityquotasretries
  2. Legacy Integration Patterns beginner

    A new notifications service needs customer contact data that only a twelve-year-old billing system holds. The team points it at a read replica of the billing database and ships in a week. Why does this work, and why is it still the most expensive integration they could have chosen?

    3 min answer integrationshared-databasecouplingschema-change
  3. Legacy Integration Patterns advanced

    A new platform must integrate with legacy systems that only support batch file exchange. How should the boundary be designed so the new system is not constrained by it?

    2 min answer elasticrunlegacybatchanti-corruption
  4. Legacy Integration Patterns advanced

    At 21:40 a schema change on the legacy order database makes the change-data-capture connector feeding the new analytics store crash-loop. At 23:10 the connector is still down and nobody has been paged, because the analytics store is not customer-facing. At 04:55 the order database refuses writes — its data volume is full. What failed, and which design decision made it possible?

    3 min answer cdcreplication-slotwaloffload
  5. Legacy Integration Patterns intermediate

    New services must interact with a legacy system that cannot handle their load or their pace of change. Which integration patterns apply?

    2 min answer legacy-integrationanti-corruption-layercdcbuffering