Verizon's Cloud Native Transformation - Syam Suri, Verizon
summary
Verizon migrates a customer-facing stack from monoliths to an API-driven, cloud-native microservices platform using Pivotal Cloud Foundry, Spring Boot/Spring Cloud, Apigee gateway, Redis cache and Cassandra datastore, with Swagger-generated docs and CI/CD pipelines. Outcome-based product teams own features end-to-end. The first MVP runs entirely in cloud, scales automatically for peaks (tested to 30,000 orders per minute), eliminates ~30–40% annual dev capacity spent on infra refresh, and yields marked reductions in time-to-market through an API-first design.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker intro
- 1:04Verizon’s transformation vision
- 3:14Problem challenges and goals
- 7:50Cloud native and microservices strategy
- 10:24Development culture shift
- 13:22Solution architecture overview
- 14:27API platform and API-first approach
- 19:56Microservices layered architecture
- 23:06Platform-as-a-service with PCF
- 26:18Scaling for high-demand events
- 30:05Data store transformation to Cassandra
- 32:42Real-time data streaming and CI/CD
- 34:09Key takeaways and lessons learned
- 43:55Q&A and legacy code migration
related talks
24mNext gen eCommerce and Web Applications: Building on a Composable Cloud
03h 04mHow We Evolve Clever Cloud – Postmortem on a 10‑Year Project
43mAPIs Are the Backbone of Every Company
25mChanging the Development Culture at Comcast and Our Evolution from Legacy SOA to Cloud Native
01h 00mEvolving to Cloud Native
23mOn the road from Monolith to Micro
18mKeynote: To Change a Huge Company: Volkswagen's Way to Renew Its Software Development
09mAjay Patel at SpringOne 2020