Zipwhip was the first company to enable texting on existing business phone numbers, and today is the world’s leading business‑texting software and API provider. More than 35,000 companies use Zipwhip to increase customer engagement and drive growth through texting on their existing landline, VoIP, or toll‑free phone number.
To achieve this scale, Zipwhip transformed its traditional core architecture (physical data centers, VMware clusters, storage arrays, firewalls, and switches) to a modern architecture that incorporates cloud providers, Infrastructure as Code, repeatability, and Kubernetes. In building out this large, complex infrastructure, Zipwhip prioritized simplification whenever possible, choosing NGINX Ingress Controller as the main ingress into its Kubernetes environment and so much more.
In this webinar, Zipwhip’s Principal Architect, Kolby Allen, describes:
We also demo how easy it is to deploy NGINX Ingress Controller in Amazon EKS.
How NGINX Ingress Controller supported Zipwhip’s rapid growth – 280% in just 9 months
About simplifying Kubernetes with an infrastructure-agnostic solution that can be used for load balancing, advanced health checks, and more
Ways to increase uptime and resiliency
Why using NGINX Ingress Controller reduces costs and saves time
Jenn Gile
Head of Product Marketing, NGINX
Amir Rawdat
Solutions Engineer
Kolby Allen
Principal Architect, Zipwhip