Building a scalable email infrastructure takes a lot of thought, testing, and planning. For some businesses, the thought of scaling your email from thousands of emails a day to hundreds of millions per day is not only daunting, but challenging. Rather than building your own datacenter and email infrastructure, many companies are turning to providers who offer email as a service.
Our VP of Engineering, Chris McFadden, recently sat down with Software Engineering Daily podcast host, Jeffrey Meyerson, to talk about what it’s like to architect and scale an email service that grows with its customer base.
In this podcast, Chris talks about the layers of infrastructure that a message passes through before it makes it into the recipient’s inbox. He also goes in depth with how SparkPost’s infrastructure is set up, why we’re built on AWS, and the importance of micro-services in our deployment process.
Meyerson delves into what it’s like to a be a developer using email as a service, what are the different conditions and configuration points in the API that a developer would want to interact. Hear first hand how we made the decision to move to the cloud and the thought process behind developing our API. You’ll also gain insights on how we handle burst rates and the tooling around our compliance and deliverability.
Whether you’re a developer, responsible for scalable email infrastructure at your company, or interested in what’s in other people’s tech stacks, you’ll want to listen to this podcast.
Listen now: Software Engineering Daily Podcast
Interested in more information on building a scalable email infrastructure? Check out these other posts: