Application Modernization: From Concept to Kubernetes
Talkat AppDeveloperCon Europe 2024 · on Tuesday, 2024-03-19· at 11:05· Pavilion 7 | Level 7.3 | Room S04·
summary
Concrete migration paths with tradeoffs: refactor for biggest benefit but highest risk, replatform to gain infra features with moderate code changes, or rehost as a quick lift‑and‑shift. Uses strangling the monolith (carve auth first), applies DDD to define bounded contexts, and recommends a modular monolith when teams are small. Builds an internal developer platform using Dapr for state and pub/sub plus Backstage, ArgoCD, Crossplane and Kubernetes operators; MongoDB operators reconcile Community/Enterprise/Atlas resources and this approach proves operationally effective.
AI-written summary · about
chapters (14)
- 0:00Application modernization intro
- 1:04Modernization and legacy systems
- 3:12Modernization drivers and 7 Rs
- 3:55Refactoring vs rehosting repurposing
- 5:20Monoliths to microservices macroservices
- 7:28Modernization architectural tools
- 9:34Strangling monolith backing services
- 11:49Microservice modernization challenges
- 13:15Dapper for service management
- 13:35Microservices vs modular monoliths
- 15:59Replatforming for developer experience
- 17:03Internal developer platform
- 18:05Kubernetes as platform
- 19:29Kubernetes operators example
related talks
44mMigrating a Monolith to Kubernetes
35mModernize Legacy Systems with Kubernetes
18mRe-Architecting Monoliths Into Kubernetes Microservices at Million-User Scale: Hard...
39mUsing Kubernetes to Change Legacy Systems and Processes in the Public Sector
24mFrom Lift-and-Shift to K8s: A Two-Phase DevOps Modernization
48mFrom Monolith to Micro-services with Kubernetes
26mOn Prem to Cloud Native
38mThe Good, the Bad & the Ugly of Migrating Hundreds of Legacy Applications to Kubernetes