TOPIC

Microservices

These are the same questions found in the library, grouped here by the capability each one mainly examines.

11 questions

A · Professional problem solving and implementation11

Two services write directly to the same business table, and an immediate shutdown is impossible. How would you gradually establish a single data owner?System design
An order is updated successfully, but a cross-service report reflects it minutes later. The product asks for “real-time status.” How would you define and implement consistency expectations?System design
A cross-service flow includes payment, inventory reservation, and shipment. How would you define compensations and irreversible boundaries when later steps fail?System design
Incidents recur at service boundaries. Each team can show its service is healthy, but nobody owns end-to-end recovery. How would you repair accountability?System design
Several services have separate owning teams, yet a small change often requires three or four teams to release together. How would you assess whether the service boundaries have failed?System design
Several tenants share an asynchronous job platform, and some submit many long-running tasks. How would you design scheduling, isolation, quotas, and use logs, metrics, and call records to understand queue behavior?System design
Some objects become hot, degrading reads while writes must remain ordered. How would you divide caching, partitioning, and write coordination?System design
The business needs every state change to be traceable and safely replayable, but some old events lack fields. How would you design event versions, retention, and replay boundaries?System design
A multi-region service must preserve critical functions during a regional outage, but some data cannot tolerate conflicting overwrites. How would you choose degradation, replication, and recovery policies?System design
A real-time collaboration service has many long-lived connections, and slow clients accumulate updates. How would you choose between dropping, combining, limiting updates to slow clients, and resynchronizing?System design
An entry service calls several downstream systems. One noncritical dependency occasionally slows down, exhausting request threads and affecting unrelated features. How would you design timeouts, concurrency isolation, degradation, and recovery?System design