Decomposing Java applications
summary
A concrete claim: decomposing by components and processes rather than only by libraries avoids accidental cross-access. Demos implement a house‑cleaning company across six iterations, using module-info with Java 9 / JPMS to block direct access (the “borrow van” bug stops compiling) and then using ServiceLoader and an OSGi example to swap a broken transport implementation at runtime. The code lives on GitHub, the Java 9 modular build fails fast for illegal access, and the OSGi demo successfully replaces services without restarting.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 6:05The Hero
- 10:33Smart Garage
- 13:49Smart Company
- 21:20Processes vs Assets
- 28:51JPM
- 35:33Service Loader
- 39:28OSGi
- 45:47Microservices
related talks
59mDecomposing Java applications
50mRefactoring your code to Java 9 modules
52mMonoliths to Modular: Navigating the Transition
01h 02mJava 9 Modularity in Action
51mThe Java 9 Module System Beyond The Basics
51mJava Modularity: Life After Java 9
46mBeyond Jigsaw
33mPanel Session - Modularity Futures: OSGi and Java 9+