Outbox Pattern
Also written as Transactional Outbox, Outbox Table
A way to make sure a service never saves a change without telling other services about it, or announces a change it didn't save. The event is written to an 'outbox' table in the same database transaction as the change, and a separate process then publishes it to Kafka or a queue.
Think of it like
Putting the letter in the office out-tray as part of finishing the job; the post room collects from the tray, so no letter is lost even if the post room was closed that day.
Junior or senior?
A senior microservices signal: it shows they've met the problem of lost or duplicate events.
Senior sounds like
Can explain why 'save, then publish' isn't safe, and how receivers cope when the same event arrives twice.
Ask them
“How did your services make sure an event was published every time the data changed, and what happened when the same event arrived twice?”
Reading Outbox Pattern on a resume
- High signal
- Outbox Pattern genuinely separates candidates, so it is worth leading a screening call with it. Its presence is a reason to talk; the question above tells you whether the experience is real.
Sourcing for Outbox Pattern
Every way it's written
("Outbox Pattern" OR "Transactional Outbox" OR "Outbox Table")Paste into LinkedIn Recruiter, Naukri or your ATS. Combine with a job title and location.
Job titles to search alongside it
Backend Engineer · Backend Developer · Backend Software Engineer · Server Side Engineer · API Developer
Where this talent works in India — Backend & Distributed Systems
Target companies with high transaction volume or hard latency budgets — payments, commerce, trading and global SaaS. Scale, not stack, is what separates a real senior backend engineer here.
For example: Flipkart, PhonePe, Razorpay, Zerodha, Groww, Zoho, Freshworks, Atlassian.