Moving from monolithic to microservices
summary
Enterprises move a monolith to microservices either by a risky big rewrite or strangler style incremental extraction, typically pulling components out first in the same language then later rewriting them in lighter stacks. OpenShift is presented as the single platform that manages lifecycle, scaling and HA for both monoliths and services, letting teams operate uniformly. Tradeoffs include memory‑local calls becoming network calls with added latency, and the need to implement patterns like circuit breakers and failover and better protocol/tooling support.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 2:31Success patterns
- 4:25Microservices and architecture
- 7:04Future of software architecture
- 8:48Whats next for Jorge
related talks
42mQ&A - Monolith to Microservices
38mFrom Monolith to Microservices
52mMicroservice Migration Roadmap
37mEvolutionary Architecture & Microservices
32mSplitting the monolith
57mSplitting Monolith Application to Microservices
01h 03mFrom Monolith to Microservices: Story and Practice
39mConsidering Migrating a Monolith to Microservices?
