A consistent key-value store like etcd: Raft across three AZs, MVCC revisions in bbolt, watches, leases and compare-and-swap, run as a fleet behind Kubernetes.
Infrastructure, platform and reliability engineers.
Your approach: Use diagrams or prose to explain responsibilities, state, capacity and failure behavior. Show the calculations requested by the question.
Design a Consistent Key-Value Store like etcd. A consistent key-value store like etcd: Raft across three AZs, MVCC revisions in bbolt, watches, leases and compare-and-swap, run as a fleet behind Kubernetes. Work from the scoping questions below. State assumptions for any unspecified load, guarantee or target, then trace your design end to end. Explain one difficult case and a credible alternative; the worked example is a reference, not a required implementation.
Resolve the scoping questions for a Consistent Key-Value Store like etcd. Separate stated behavior from assumptions, and identify what is outside your design.
Declare relevant volume, latency, freshness, quality or cost targets with units. Show calculations or an evaluation plan that can test them; unspecified targets are your assumptions, not hidden pass criteria.
Explain how your guarantees hold in a difficult case relevant to this subject. Address: Membership changes? Regions?
Identify users, required behavior and exclusions. Answer: Size and rate? Consistency?
Define the information owned by the system and the inputs, outputs and errors at its boundaries. Resolve: Failures to survive? Latency?
Estimate the dominant workload and resource demand with units and explicit assumptions. For a learned system, also state how quality is measured and what data is available.
Draw or describe the responsibilities needed for a Consistent Key-Value Store like etcd. Trace a representative request, event or job from its input to a visible result; identify durable state owners.
Walk through a difficult case step by step, including detection and recovery. Consider: Who are the clients? Membership changes? Regions?
Compare a credible alternative using your chosen workload and guarantees. Explain a remaining risk, a signal to watch and when you would change the design.