Monoliths to Modular: Navigating the Transition

on YouTube ↗43m

" summary

Compares Java Platform Module System (JPMS) and OSGi and gives concrete trade-offs: JPMS (Java 11+) is static, reduces JRE footprint for cloud, and suits single-team ownership; OSGi supports runtime dynamism and hot-reload, with PDE (manual manifest bumps) versus BND (automatic bytecode-driven manifest updates). Recommends tools such as Monoto micro, Transformation Advisor, and Azure Migrate for binary and runtime analysis, shows refactor vs rearchitect vs lift‑and‑shift outcomes, and stresses observability and team composition as decisive factors.

AI-written summary · about

" chapters (6)

1. 0:00Introduction to modernization
2. 5:02Why modernize legacy systems
3. 13:22Modernization strategies overview
4. 21:15Modularity types explained
5. 31:59Best practices for modularization
6. 40:01Key takeaways and conclusion

" related talks

• 52mMonoliths to Modular: Navigating the TransitionGireesh Punathil, Elsa Zacharia · Voxxed Days Luxembourg 2024
• 33mPanel Session - Modularity Futures: OSGi and Java 9+EclipseCon Europe 2018
• 51mJava Modularity: Life After Java 9Sander Mak, Paul Bakker · J-Fall 2015
• 32mOSGi and Java 9+BJ Hargrave · EclipseCon Europe 2018
• 59mMajestic Modular MonolithsAxel Fontaine · W-JAX 2018
• 50mRefactoring your code to Java 9 modulesRabea Gransberger · JDD 2017
• 47mModular MonolithsSimon Brown · GOTO Berlin 2018
• 59mDecomposing Java applicationsMilen Dyankov · JPoint 2019