Running a Notification System with BullMQ, Part 3 - Where to Store Delivery History
Where should delivery history live? The trade-offs weighed across a dedicated relational DB, a serial S3 pipeline, SNS fan-out, and a Firehose route.
3 posts

Where should delivery history live? The trade-offs weighed across a dedicated relational DB, a serial S3 pipeline, SNS fan-out, and a Firehose route.

Quota was 100 messages per 5 seconds, average 20 req/s, yet 429s still fired. Misaligned fixed windows and a shared account forced a new sending path.

Sending AlimTalk, email, and push as HTTP calls hits limits fast. Why BullMQ takes on rate limits, scheduling, and delivery history.