Food delivery orders · Data Modeling scenario

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You just joined Tiffin, a food-delivery app. Restaurants edit their menus constantly — prices up, dishes renamed, items pulled — while orders placed yesterday must still read exactly as they did. Design the first simple database behind it.

your ERD must answer

01What was in this order, and what did each item cost?
02What is the restaurant owed for that order?
03What has this customer ordered before?

out of scopeRatings · promo codes · rider tracking · refunds · payment gateway

This exercise’s brief could not be loaded.The guided questions and their model answers come from the review service. It looks like it is not reachable — start it with pnpm dev:api and reload.The canvas below still works, so you can model now and run the review once the service is up.

Build starts here

The brief becomes the left drawer. The canvas stays the build surface.Study is done above. Build the tables here, hit review to validate, then use follow-ups to defend the model.

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

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.

68%

You built the model in the Studio. Now defend it.Food delivery orders

Design review

The reviewer reads your model.

Desktop only

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.

Read the library instead Back to modules

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You just joined Tiffin, a food-delivery app. Restaurants edit their menus constantly — prices up, dishes renamed, items pulled — while orders placed yesterday must still read exactly as they did. Design the first simple database behind it.

your ERD must answer

01What was in this order, and what did each item cost?
02What is the restaurant owed for that order?
03What has this customer ordered before?

out of scopeRatings · promo codes · rider tracking · refunds · payment gateway

This exercise’s brief could not be loaded.The guided questions and their model answers come from the review service. It looks like it is not reachable — start it with pnpm dev:api and reload.The canvas below still works, so you can model now and run the review once the service is up.

Build starts here

The brief becomes the left drawer. The canvas stays the build surface.Study is done above. Build the tables here, hit review to validate, then use follow-ups to defend the model.

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

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.

68%

You built the model in the Studio. Now defend it.Food delivery orders

Design review

The reviewer reads your model.

Desktop only

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.

Read the library instead Back to modules