Loadingone moment…
You just joined Marquee, which sells cinema tickets. Someone picks a movie and a time, picks a seat from the map, and pays. Here is the thing to get right: two people must never turn up holding a ticket for the same seat. If both tap “pay” for seat 12F at the same instant, one of them has to be told it has gone — and it is the database that has to stop it, not the app. Design the first simple database behind it.
out of scopePayment gateways · seat holds · refunds · loyalty points · food orders
pnpm dev:api and reload.The canvas below still works, so you can model now and run the review once the service is up.Practice studio
Start with the data model, then layer system context
Use entities and relationships for the real ERD. Add notes, containers, or curated cloud shapes only when they sharpen the story you are architecting.
This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.