Migrating a Mission Critical Monolith to a #CloudNative Architecture
summary
An Oracle Order and Service Management monolith remains live while new features use the strangler pattern as Java microservices deployed on Kubernetes, keeping the original WebLogic domain containerized via a Kubernetes toolkit and WebLogic operator. New services use Helidon (SE and MicroProfile), adopt OpenTelemetry/Prometheus and gRPC, and apply bulkhead/retry/timeout to preserve JMS ordering, throttling external calls to five concurrent threads and reporting internal tests of 63% fewer platform threads and 30% less CPU compared to the prior stack.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:07Monolith goals and challenges
- 7:13Migration strategy and constraints
- 12:00Cloud native and microservices journey
- 15:36Challenges in microservices adoption
- 22:14Choosing Helidon framework
- 28:02Integrating microservices with monolith
- 31:53Fault tolerance strategies
- 40:23Current status and future plans
- 41:51Summary and key technologies
- 42:55Q&A
related talks
34mFrom monolith to Cloud Native
57mSplitting Monolith Application to Microservices
12mTen Things I Hate About Microservices
32mSplitting the monolith
28mThe journey from monolith to microservices
39mHybrid Cloud Applications for the Enterprise – Evolving Traditional Applications with Microservices
18mRe-Architecting Monoliths Into Kubernetes Microservices at Million-User Scale: Hard...
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies