Design a strongly consistent store for fleet validation results
I was asked this
No reports yet. Sign in to say where you were asked it.
Two internal services share a database: one validates the operating system on every machine in a large fleet and writes the outcome per machine, and the other reads those outcomes to decide which machines may take production work. Design the storage layer between them.
The interviewer gives almost no feature requirements beyond that; the point is that the data must be strongly consistent and keep working when nodes fail. Cover the data model and its versioning, how writes are replicated and agreed on (leader election, quorums, fencing a stale leader), what a reader is guaranteed to see, how the system behaves during a failover or a network partition, and how you would recover or audit a wrong decision.
No official answer yet. Draw yours on the right; publish it and it shows under Community.
Nothing published yet. Publish your canvas and it shows here for others to open and remix.