D8LooP - Practise Data Engineering

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You've joined GoRide. The same person can be a rider on Monday and a driver on Tuesday, and their history should be one history. Either side can cancel, with a fee depending on who and when. And dispatch has already shipped one bug where a driver got assigned two trips at once — it must not be possible again.

your model must answer

01Which trips are in progress right now?
02Every trip involving one person, whether they rode or drove?
03Assign a driver such that two racing dispatchers cannot assign the same driver twice?

out of scopeFare breakdown · surge · payouts · ratings · live location

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.Dispatch that can't double-book a driver

Design review

The reviewer reads your model.

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

your model must answer

01Which trips are in progress right now?
02Every trip involving one person, whether they rode or drove?
03Assign a driver such that two racing dispatchers cannot assign the same driver twice?

out of scopeFare breakdown · surge · payouts · ratings · live location

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.Dispatch that can't double-book a driver

Design review