UniSender Architecture: Growth from 100M to 1.5B Monthly Emails
summary
UniSender's architecture evolution from 2013 to 2020, focusing on how the team refactored a legacy monolith into microservices starting in 2015 to handle a traffic growth from ~100M to 1.5B emails per month. The talk covers why they chose refactoring and microservices over SOA/keeping the monolith, how they prioritized which components to split, their migration choices (notably choosing AWS S3 over Ceph for storage), and which system components enabled 10–15x growth without proportional vertical-scaling cost increases.
AI-written summary · about
related talks
44mEmail at Scale: How We Survived 800M Emails/Year (and DNS)
28m10 Billion Messages in a Day, How We Built the Infrastructure That Delivers
10mMicroservices, Messaging, and Failure: How Simplifying Our Architecture Saved Us
30mMonolith-ifying perfectly good microservices
35mLegacy Monolith to Microservices
28mThe journey from monolith to microservices
23mMicroservices – Diptanu Choudhury
51mMicroservices and Microfrontends: Scaling, Learning, Growing