Read waits-for cycles, choose safe victims, retry complete transactions, and prevent recurring deadlocks.
Interactive scenario
Use the controls below. Feedback appears immediately and final scores stay in this browser.
Concept notes
Deadlock Detective is focused practice for Database deadlocks and lock ordering. It explains why each answer is safe, risky, or production-ready.
Use lock evidence to turn a concurrency incident into a predictable recovery path.
A deadlock is a cycle of transactions waiting on one another.
Databases break cycles by aborting a victim; applications must retry the whole transaction when safe.
Use the main site for deeper reading after playing.
Use tools from the main site when you want to inspect real inputs.
Short answers for how this game fits backend interview and study practice.
No. They are expected concurrency outcomes that systems should minimize and recover from.
No. They only delay detection or failure.
Top 10 scores for the current ruleset. No account required.
Loading leaderboard...
Finish the game to load your latest local score.