Panel: The Microservices Stack: Are We There Yet? What’s Missing?
summary
Argues that Cloud Foundry plus Spring Boot/Cloud proves the runtime but the big gap is the data tier: teams must apply microservice patterns to storage, break monolithic databases into distributed, polyglot stores and cope with service discovery and API versioning. Recommends service protocol (service broker binding), consumer-driven tests via Spring Cloud Contract, and warns that many orgs converge on a single stack; Spring Boot reports 19 million downloads a month as evidence of standardization.
AI-written summary · about
chapters (9)
- 0:00Introduction of panelists
- 2:29Evolution from LAMP to microservices
- 6:17Data tier challenges in microservices
- 8:07Team autonomy vs API ownership
- 10:40API versioning and standardization
- 13:30Cultural barriers to adoption
- 16:36Asynchronous APIs and education gaps
- 18:21Homogeneous vs heterogeneous platforms
- 21:52Closing remarks and thanks
related talks
31mCloud Foundry and Microservices: A Mutualistic Symbiotic Relationship
43mPanel: Microservices, Where Did It All Go Wrong
01h 29mDeveloping Microservices for PaaS with Spring and Cloud Foundry
27mManaging the Complexity of Microservices Deployments - Prithpal Bhogill, Google & Kenny Bastini
31mDeploying Microservice Architectures with Cloud Foundry
36mTools that will help you survive in the micro-service architecture
20m3 reasons why micro-services aren't the miracle cure
38mMicroservices, a bittersweet symphony