MongoDB Polling Replaces RabbitMQ to Scale Push and SMS at Wheely
Wheely moved its notification logic from a Ruby monolith into a stateless Go service, but RabbitMQ choked on campaign spikes. By swapping the broker for a MongoDB‑backed polling queue with atomic claims, retries and dead‑letter handling, they processed multiple times their previous peak volume. The trade‑off: added polling latency and DB overhead, but elimination of broker‑related failures.