D8LooP - Practise Data Engineering

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You've joined GoRide. Drivers go online, take a trip, go offline and come back dozens of times a day. Dispatch needs to know who is free right now; analytics wants utilisation — what fraction of the time drivers were online but idle; and support regularly has to explain a fare line by line.

your model must answer

01Drivers currently free in a given city?
02The full fare breakdown for one trip?
03Trips, revenue and total driver idle hours per city yesterday?

out of scopePayouts · surge rules · ratings · promotions · inspection

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.Live dispatch and daily KPIs

Design review

The reviewer reads your model.

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

your model must answer

01Drivers currently free in a given city?
02The full fare breakdown for one trip?
03Trips, revenue and total driver idle hours per city yesterday?

out of scopePayouts · surge rules · ratings · promotions · inspection

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.Live dispatch and daily KPIs

Design review