Backend engineering from first request to production · check

Know API contracts and relational databases 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 5: Can an old client read the new response?

Which change can break an old reader expecting text?

Not quite. The reader still finds its original text field. Learn it in puzzle 5 →

Right. An API contract specifies methods, fields, validation, status codes and compatibility.

Puzzle 6: Can a bookmark point to a missing owner?

Ben has no bookmarks. What should his count be?

Not quite. The account exists but has no matching bookmark. Learn it in puzzle 6 →

Right. A foreign key enforces a relationship; a left join can include owners with zero bookmarks.

Puzzle 7: What if the service stops between two writes?

The worker loses the acknowledgement. Which value should a second delivery reuse?

Not quite. The consumer needs a stable identity to recognize redelivery. Learn it in puzzle 7 →

Right. A transaction can commit both the bookmark and a pending event, or roll back both.

Puzzle 8: Why does the same page cost less to read?

Two bookmarks share a time. What belongs in the page cursor?

Not quite. A timestamp alone cannot distinguish the tied rows. Learn it in puzzle 8 →

Right. An index matching the owner and sort order can serve the same page with less searching and sorting.

Back to the overview →