This is a newsletter send engine I built on SES to stay within its rate limits, along with an Instagram analytics pipeline that warns me before its own access token expires.
Email platforms charge by subscriber, so the price climbs at exactly the point the list becomes valuable. I also wanted analytics that answered my questions rather than whichever ones a dashboard had decided to show me.
Sending email properly is harder than it looks. Send too fast and the provider throttles you, and ignore bounces and suppressions and deliverability degrades quietly until very little is landing.
Subscribers are paginated out of Firestore in pages of 500 and sent in parallel batches deliberately held under the provider rate ceiling, rather than sent as fast as the code can manage.
The analytics pipeline pulls per-post metrics on a schedule, computes the derived numbers I care about, and emails me when its own access token is within two weeks of expiring.
Batches are sized and parallelised to sit under the provider ceiling by design, rather than hitting the limit and retrying the failures. A send that stays under the ceiling finishes cleanly, whereas one that hits it ends up partially delivered and is difficult to reason about afterward.
Subscribers are cursored in pages rather than loaded at once, so the send behaves the same at a thousand subscribers as at fifty thousand, inside a function execution ceiling that does not move.
The Instagram integration emails me when its access token is within fourteen days of expiring. Scheduled integrations tend to die on an expired credential and stay dead until someone happens to check, so it tells me first.
Bounces and complaints are reconciled against the provider suppression list rather than left sitting in the subscriber table, because the cost of ignoring them shows up slowly in deliverability.
I run my own newsletter and my own growth analytics on infrastructure I control, at the cost of the underlying services rather than per subscriber.
It is also a good example of the backend work I do, since I am the one who has to fix it when something breaks.