13.8. Benefits of JPMS

• Reliable Configuration: No more JAR conflicts or classpath issues.

JPMS provides a reliable configuration by organizing code into modules, which prevents issues like JAR conflicts that were common in previous versions of Java. In the past, multiple libraries might contain classes with the same names, leading to confusion regarding which version of a class is being used at runtime. By defining clear boundaries, JPMS ensures that each module manages its dependencies more effectively.

Think of a library system where each book is clearly labeled and categorized into specific shelves (modules). If books were placed randomly or had similar titles, it would be hard to find the right one. JPMS organizes these books, so each one is found in its proper place, avoiding confusion.

• Strong Encapsulation: Prevents unwanted access to internal APIs.

Encapsulation in JPMS means that a module can restrict access to its internal code. This leads to better security and fewer chances of accidental interference from other modules or applications. If a module is designed to expose certain packages, it can hide its internal implementation from outside users, which reduces bugs and enhances the stability of the application.

Imagine a high-security facility where certain areas are only accessible to authorized personnel. Just like how only specific individuals have access to sensitive information or machinery, JPMS restricts access to internal module functionalities, allowing only selected parts to be opened to others.

• Improved Performance: JVM can optimize startup and memory use.

By organizing code into modules, JPMS allows the Java Virtual Machine (JVM) to load only the required modules at startup, instead of loading everything into memory. This results in faster startup times and better memory management, as unnecessary code is not loaded, leading to a more efficient application overall.

Consider an online shopping website that only loads product categories that a user is interested in instead of all items at once. This targeted approach not only speeds up browsing but also uses less memory, akin to how JPMS enhances Java application performance by loading only the needed components.

• Security: Explicit access control reduces attack surfaces.

JPMS improves security by enforcing explicit access controls, meaning that modules must declare which elements are accessible to other modules. By limiting exposure to only necessary parts of a module, it minimizes potential vulnerabilities and reduces the risk of attacks that target the codebase.

Imagine a bank where customers can access their accounts through a secure app that only reveals certain information. By controlling what data is visible to customers, the bank reduces the risk of data breaches. Similarly, JPMS helps developers control how much of their code is accessible to others.

• Maintainability: Clear boundaries and dependencies.

With JPMS, the clear definition of module interactions and dependencies contributes to easier maintenance of applications. When changes are made to one module, it is clear which other modules might be affected due to their declared dependencies, simplifying the process of updates and debugging.

Think of a car assembly line where each section focuses on a specific part of the car and communicates with clearly defined specifications. If you want to upgrade the engine, you know exactly which sections will be affected. This organized approach in modular programming similarly eases the process of maintaining and updating code.

--