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

Difficulty Any beginner intermediate advanced

5 questions in WebSockets & Realtime.

Quiz

2.4 million live WebSocket sessions sit on a gateway fleet being retired this quarter, with a replacement fleet ready in the same region. Sequence the cutover so no session is forced to reconnect more than once and the subscription path is never asked to absorb a storm.

A chat platform's websocket edge gateways lose a region to a cloud networking failure. How should reconnect storms, session resumption, message-gap recovery and gateway draining be designed so a 30-second outage does not become a 3-hour one?

A dashboard product uses WebSockets for live updates. It works at 5,000 concurrent users and falls apart at 50,000. Diagnose the architectural issues.

A deployment drops 200000 WebSocket connections at once. Describe what happens next and how you would make it safe.

A trading platform must push live prices to hundreds of thousands of concurrent connections. What are the architectural constraints of that fan-out, and how does it differ from the order path?