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

3 questions in Design Patterns.

  1. Design Patterns advanced

    A collaborative whiteboard supports hundreds of concurrent editors on one board. Compare OT and CRDT for a canvas with object hierarchies, and describe board sharding and catching up after ten minutes offline.

    3 min answer mirocrdtoperational-transformcollaboration
  2. Design Patterns advanced

    At 09:14 a document-processing platform of JetBrains' shape starts returning wrong results for about 3% of requests. No errors, no latency change. The stack traces contain three frames of framework code and a lambda. It takes eleven hours to find. The code is a textbook strategy-and-registry design. What made this undiagnosable, and which design decision would you change?

    2 min answer jetbrainsdesign patternsdynamic dispatchregistry
  3. Design Patterns advanced

    At 10:04 one dependency slows from 40 ms to 900 ms. By 10:06 the service is saturated, the dependency is receiving 14 times its normal request rate, and nothing in the code review that introduced the retries looks wrong. What failed, and which design decision made it possible?

    3 min answer retriesdecoratoramplificationcascading-failure