Where do you stand?

01The questions

1. 1When a prompt is vague, can you get to a few must-haves, some rough numbers and an out-of-scope list in about five minutes?

   YesSomewhatNot yet
2. 2Can you estimate peak requests and storage from a few assumptions, and say which number shapes the design?

   YesSomewhatNot yet
3. 3Can you sketch the API and the core entities, and name the queries the data model has to serve?

   YesSomewhatNot yet
4. 4Can you pick a store for each kind of data, and defend it by how that data is read and written?

   YesSomewhatNot yet
5. 5Can you scale reads and writes with caches, replicas and partitions, and say how each one fails?

   YesSomewhatNot yet
6. 6Can you say which data must be exact and which can lag, and how a retried request stays safe?

   YesSomewhatNot yet
7. 7Can you move slow work off the request path, and keep it correct when a message repeats or arrives late?

   YesSomewhatNot yet
8. 8Can you walk your design one component at a time, say what breaks, and say how you would notice?

   YesSomewhatNot yet

02What to read first