The Data Foundry is improving every week. If something feels unclear, broken, or missing, tell us and we will use it to improve the platform.
System Design Studio
Turn system design theory into architecture reps: choose trade-offs, review a broken design, write your answer, get a rubric score, and reveal a production-grade model answer.
Cases
10
Free
4
Completed
0
A growing e-commerce company wants reliable order, payment, and refund reporting. Finance needs daily revenue by 8 AM, operations needs order status visibility, and analysts need two years of history.
Functional requirements
Non-functional requirements
Interactive system map
Select any stage to inspect its responsibility. Animated edges show the direction of data movement through the platform.
Source APIs
Produces the events or records entering this design.
Broken architecture review
A single Python cron job pulls only today's orders, overwrites one CSV, and the dashboard reads that CSV directly. No raw history, no reconciliation, no retry safety.
Task: Design a production-ready batch architecture and explain how you would handle retries, corrections, and revenue reconciliation.
Decision questions
What should be the first durable landing zone?
How should daily Gold partitions be updated?
Your architecture answer
Write like an interview: requirements, architecture, trade-offs, failure handling, monitoring, and why your choices fit the SLA.