Replaced a fragile nightly batch with a 28-second sync
Inventory and orders were synced to a legacy ERP by a nightly batch that broke weekly and left data a day stale. I replaced it with an event-driven pipeline.
// The problem
A nightly cron synced inventory and orders to an ERP. It failed often, was hard to debug, and meant the storefront showed day-old stock — causing oversells.
// The approach
- Mapped the failure modes of the existing batch and the ERP’s brittle API limits.
- Introduced an event stream: domain events published on every inventory and order change.
- Built an integration service with idempotency, retries with backoff, and a dead-letter queue.
- Added an outbox pattern so events are never lost even if the ERP is down.
- Wired tracing and alerts so a stuck sync pages someone with the exact failing record.
Our storefront finally tells the truth about stock. The whole thing just works, and when it hiccups we know exactly why.
Case studies, metrics, prior companies, and testimonials in this template are illustrative and anonymized for demonstration; they do not name or represent any real client or employer and are not a guarantee of future results. Outcomes vary by system, team, and constraints.