Engineering Team Replaced 3 Microservices and 4,100 Lines of Code With One Postgres Table

A software team eliminated three separate microservices — a notification service, a scheduler, and a retry handler — totaling over 4,100 lines of code, replacing them with a single 41-line Postgres table and a 560-line worker. The services were well-built but had been architected around an unnecessary boundary, as all three ultimately existed to move data from one state to another at a scheduled time. The original setup relied on RabbitMQ queues and Redis, introducing a classic distributed systems risk known as the transactional outbox problem, where a failure between a database write and a queue publish could silently drop events. By storing jobs directly in the database alongside application data, the team ensured all state changes remain in a single transaction, eliminating drift between systems. The refactor reduced operational overhead — including separate deployments, dashboards, and on-call runbooks — while retaining scheduling, retry, and delivery logic through simple SQL columns and queries.