This question is for Sander Mak & Paul Bakker . First of all , thanks for this book . For me , Java 9 and jigsaw impact in my projects architecture, but I need a little help to change my way of programming and to change my point of view .
I want to know if this book focus on java 9 design patterns , and the best way to handle modules , instead of a jigsaw introduction . I understand modules ( well , understand enough to start using it ) , but I don't know how to play dividing tiers, modules, projects, ... I don't know if a java 9 module should have the scope of one tier ( one module for persistence, another module for business, ... ) , one module should have the scope of a library, or maybe the scope of a microservice, .... Of course , it depends on the architecture of my project and the goals I want to achieve, but I want to know if this book talks about this topics in deep .
First of all; thanks for stopping by! We wanted the book to be a practical guide. Therefore it includes both a discussion of the module system concepts (and you'd be surprised about the depth of some of them!) and discussion around modularity patterns (especially Chapters 5 and 6 as you can see here: https://javamodularity.com/#features). However, what constitutes a good modular breakdown of an application really depends on the requirements of your domain, so don't expect any silver bullets in that area. As a general guideline though, I'd advise you think in terms of domain boundaries rather than technical boundaries. And, as discussed in the book, a good analyses of changeability can help in establishing the right boundaries as well. Hope you enjoy reading it, definitely let us know how you think!