Backend engineering from first request to production · check

Know Identity and changes over time 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 9: Whose bookmark may this request read?

Which owner should a write use?

Not quite. A body field can name another person. Learn it in puzzle 9 →

Right. Every read and write needs an ownership decision based on the authenticated caller.

Puzzle 10: Who vouched for the caller?

The session expired but the owner still matches. What happens?

Not quite. The earlier identity check has expired. Learn it in puzzle 10 →

Right. Session expiry and resource ownership answer different questions.

Puzzle 11: When does a reader see yesterday’s list?

Which cache key keeps two owners separate?

Right. A cache entry needs a suitable key and a freshness policy.

Not quite. Both owners share that route. Learn it in puzzle 11 →

Puzzle 12: Can two releases share one schema?

A backfill finished but an old writer still runs. What can happen?

Not quite. The backfill touched only the rows present at the time. Learn it in puzzle 12 →

Right. An additive migration gives old and new application versions a period of compatibility.

Back to the overview →