D8LooP - Practise Data Engineering

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You've joined SeatBook, which sells cinema tickets. When a customer picks seats, those seats are held for ten minutes while they pay — and if payment fails or they close the tab, the seats have to free themselves without anyone intervening. On a Friday release, thousands of people tap the same seat inside the same second.

your model must answer

01Which seats are still available for a given showtime?
02Place a ten-minute hold on three specific seats for one customer?
03Confirm the booking after payment, or release the hold if payment never arrives?

out of scopePayment gateway · refunds · loyalty · pricing rules · food orders

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.Seat holds and the release-night race

Design review

The reviewer reads your model.

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

your model must answer

01Which seats are still available for a given showtime?
02Place a ten-minute hold on three specific seats for one customer?
03Confirm the booking after payment, or release the hold if payment never arrives?

out of scopePayment gateway · refunds · loyalty · pricing rules · food orders

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.Seat holds and the release-night race

Design review