The Java Module System

Lists of Figures, Tables and Listings

List of Illustrations

Figure 1.1: If the checkout service and its dependencies are jotted down, they naturally form a small graph that shows their names, dependencies, and features.

Figure 1.2: In software development, graphs are ubiquitous. They come in all shapes and forms: for example, UML diagrams (left), Maven dependency trees (middle), and microservice connectivity graphs (right).

Figure 1.3: Two systems’ architectures depicted as graphs. Nodes could be JARs or classes, and edges are dependencies between them. But the details don’t matter: all it takes is a quick glance to answer the question of whether there is good separation of concerns.

Figure 1.4: A system where high-level code depends on low-level ...