To be a good architect, you have to possess a wide array of tools that help you design architecturally resilient software. The modularity patterns are but one of these tools. Other tools include other types of patterns (GOF patterns), SOLID principles, SOA principles. You also have to possess relatively deep technical understanding of how things work so you understand the impact of your design decisions. Social skills are also important to help you communicate the architectural vision to the development team.
Visit the book's website at modularity.kirkk.com where you can review all 18 patterns and download an excerpt of the book. There is also a mobile web application available that you can take with you wherever you go.
can you elaborate how will an application architecture(especially a Java one) would generally fit in an enterprise architecture?
A Java-based application architecture is for an application. The application is a software application, it can be an application that is included in an "enterprise" architecture. In this scenario, it could be referred to as an enterprise application.
However, an "enterprise architecture" is the blueprint for an "enterprise." There are many, many things involved, business processes, humans, organizations, financial resources, hardware, software applications, operating systems, suppliers, partners, regulations, etc.
I visited your book's website at modularity.kirkk.com, you wrote modularity is a critical weapon in your arsenal of design tools.
Because i can not buy your book, can you tell me more about that critical weapon?
How can i apply OSGi and your modularity patterns to architect and design an application using (JSP/Servlet, JSF)/EJB/(JPA, Java Web Services)? What advantages and disadvantages?