Optimistic versus pessimistic locking for a limited-stock SKU on a sale day?
PICTURE THIS: STACK VS QUEUE
Simple meaning
Optimistic uses a version column and fails on conflict, which is great for rare collisions.
WHY — JPA instead of guessing?
Why interviewers care about JPA:
contrast on JPA, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Optimistic uses a version
column and fails on conflict, which is great for rare collisions.
- 2Flash-sale stock needs a
single source of truth: UPDATE stock SET qty = qty - 1 WHERE qty > 0, or pessimistic row locks, or an inventory service with a queue.
- 3Retrying optimistic lock failures
in a hot loop just amplifies load.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Optimistic uses a version column and fails on conflict, which is great for rare collisions. Flash-sale stock needs a single source of truth: UPDATE stock SET qty = qty - 1 WHERE qty > 0, or pessimistic row locks, or an inventory service with a queue.