JAVIS Technologies
Async Execution Framework
A Spring Boot starter that gave every backend service correctness by default
every backend service in the org adopted it
Built with
JavaSpring BootMySQLResilience4j
- The problem
- Every team was writing its own async plumbing — job lifecycle, retries, idempotency, completion callbacks. Each implementation was subtly different, each had its own crash-window bugs, and correctness depended on whichever engineer wrote it that quarter.
- My role
- Designed the library and drove adoption across all backend services.
- Approach
- Pushed the hard guarantees into a platform library rather than a set of guidelines, so domain teams implement only a business handler and get the rest structurally. Effectively-exactly-once falls out of at-least-once delivery plus idempotent effects: idempotency keys, compare-and-set state transitions, lease/heartbeat/reaper crash recovery, and zombie-write protection. The constraint is that handlers must be written to be replayable, which is a real thing to ask of every team.
- Outcome
- Adopted by every backend service in the org. Async boilerplate disappeared from domain code, and the crash-recovery guarantees are validated by CI chaos tests across all three dual-write crash windows.
What I built
- A Spring Boot starter that handles async work for every backend service: job lifecycle, retries, idempotency, and completion callbacks.
- Correctness built in. Every job takes effect exactly once, even when workers crash or messages are delivered twice.
- Proof in CI. Chaos tests crash the system mid-operation and check that no work is lost or done twice.
Questions about this one? Email me, or ask my AI assistant.