How rapid growth accelerated Zipwhip's move to AWS
summary
A three‑engineer team redesigns Zipwhip’s stack in nine months to handle a reported 280% message surge, migrating carrier backhaul, API and integrations into AWS. They run Amazon EKS with Kubernetes ingress via NGINX, use F5 BIG-IP VE for centralized visibility, shift databases to Aurora, and deploy Nitro‑based m5d EC2 for high I/O ActiveMQ brokers; deployments are Terraform‑driven, monitored with Prometheus and protected by CloudFront + AWS Shield. Result: multi‑AZ active/active carrier legs, on‑demand scaling and sustained four nines uptime.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:50Customer challenges
- 5:02And a diferent set of vendors for each application architecture
- 5:48Creating operational silos, complexity, and cost
- 8:13Early 2000s: Hardware load balancers
- 22:31Our migration
- 46:28Operational changes
related talks
22mFireside Chat with AWS
29mAccelerate Innovation with Hybrid Capabilities and Infrastructures
31mDevOps in the Cloud: Case Studies of Amazon.com teams and their resilient architectures
43mFast and Furious: Startup scaling with Kubernetes
49mHardware to AWS, EC2 to EKS: Two Years, Two Epic Migrations
29mHow local businesses are rapidly achieving global scale on AWS
34mHow AWS powers Delivery Hero's Logistics Optimization Process
38mInfrastructure and AWS at scale: The story of Posti