Monoliths to Modular: Navigating the Transition
summary
Argues that refactoring a monolith into modules is the safest modernization path, demonstrated by a working Java demo that splits a greetings app into JPMS vs OSGi modules and by building OSGi plugins with PDE and BND. Shows tools that analyze and generate partitions—Mono to Micro, Transformation Advisor, and Watson Code Assistant—and explains BND’s automatic manifest and semantic versioning versus PDE’s manual approach. Claims JPMS needs Java 9+, and recommends selective microservices for hot components.
AI-written summary · about
chapters (18)
- 0:00Introduction to modernization
- 1:50Modernization strategies overview
- 3:37Why modernize legacy apps
- 8:38Continuous modernization benefits
- 10:45Modernization techniques types
- 13:11Refactoring into microservices
- 16:45Modularity introduction
- 19:20Modularity demo with Java
- 22:18JPMS vs OSGi comparison
- 25:41Modularity use cases and types
- 29:57PD vs BND tool differences
- 34:51Modularity dependency factors
- 37:18Modularity best practices
- 39:27Modernization tools overview
- 43:20Methodologies for modernization
- 45:48Best practices summary
- 49:23Conclusion and key takeaways
- 49:44Q&A on data migration risks
related talks
43mMonoliths to Modular: Navigating the Transition
50mRefactoring your code to Java 9 modules
47mModular Monoliths
59mMajestic Modular Monoliths
59mDecomposing Java applications
50mImplement the monolith - the one well modularized
33mPanel Session - Modularity Futures: OSGi and Java 9+
50mDecomposing Java applications