System design from first principles to design review · check

Know Operating and defending a design already?

One question for each of the 4 puzzles in this module. A right answer marks that puzzle as passed, so you can jump ahead. A wrong one tells you which puzzle to start with. Nothing is sent anywhere: it's saved in this browser.

Puzzle 11: What if the space expires before payment is confirmed?

What does a missing provider reply mean?

Not quite. The charge may already have completed. Learn it in puzzle 11 →

Right. The charge may already have completed.

Puzzle 12: Is the database slow, or is the request waiting to reach it?

What does this objective measure?

Right. The contract concerns the driver's result.

Not quite. The contract concerns the driver's result. Learn it in puzzle 12 →

Puzzle 13: Can you recover the right history after a bad release?

What can damage all current replicas logically?

Not quite. Replication propagates unwanted changes too. Learn it in puzzle 13 →

Right. Replication propagates unwanted changes too.

Puzzle 14: Does the design survive a changed assumption?

What protects an assigned ticket?

Not quite. Two tickets could name the same seat. Learn it in puzzle 14 →

Right. Two tickets could name the same seat.

Back to the overview →