• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Tim Cooke
  • Devaka Cooray
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Mikalai Zaikin
Bartenders:
  • Carey Brown
  • Roland Mueller
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Image from Amazon
Title: Java Application Architecture: Modularity Patterns with Examples Using OSGi
Author(s): Kirk Knoernschild
Publisher: Prentice Hall
Category: Design Patterns, UML, and Refactoring


Summary

Prentice Hall wrote:“I’m dancing! By god I’m dancing on the walls. I’m dancing on the ceiling. I’m ecstatic. I’m overjoyed. I’m really, really pleased.”

–From the Foreword by Robert C. Martin (a.k.a. Uncle Bob)

This isn’t the first book on Java application architecture. No doubt it won’t be the last. But rest assured, this title is different. The way we develop Java applications is about to change, and this title explores the new way of Java application architecture.

Over the past several years, module frameworks have been gaining traction on the Java platform, and upcoming versions of Java will include a module system that allows you to leverage the power of modularity to build more resilient and flexible software systems. Modularity isn’t a new concept. But modularity will change the way we develop Java applications, and you’ll only be able to realize the benefits if you understand how to design more modular software systems.

Java Application Architecture will help you

* Design modular software that is extensible, reusable, maintainable, and adaptable
* Design modular software today, in anticipation of future platform support for modularity
* Break large software systems into a flexible composite of collaborating modules
* Understand where to place your architectural focus
* Migrate large-scale monolithic applications to applications with a modular architecture
* Articulate the advantages of modular software to your team

Java Application Architecture lays the foundation you’ll need to incorporate modular design thinking into your development initiatives. Before it walks you through eighteen patterns that will help you architect modular software, it lays a solid foundation that shows you why modularity is a critical weapon in your arsenal of design tools. Throughout, you’ll find examples that illustrate the concepts. By designing modular applications today, you are positioning yourself for the platform and architecture of tomorrow. That’s why Uncle Bob is dancing.




Book Preview (when available)



From the publisher
  • Introduction (HTML or PDF)
  • Chapter 3: Architecture and Modularity (HTML or PDF)



  • Where to get it?
  • Amazon.com
  • InformIT



  • Related Websites
  • Article: Paradoxes of Software Architecture
  • Twitter: Kirk Knoernschild
  • Website: Java Application Architecture: Modularity Patterns with Examples Using OSGi
  • COMMENTS:
     
    Bartender
    Posts: 3225
    34
    IntelliJ IDE Oracle Spring Chrome Java
    • Mark post as helpful
    • send pies
      Number of slices to send:
      Optional 'thank-you' note:
    • Quote
    • Report post to moderator
    Rating: I give this book 8 out of 10 horseshoes

    This book consists of two parts:
    1. Deals with the basic concepts related to modularity
    2. Patterns dealing with modularity.

    The book deals at the architecture level and the patterns described therein are more suited to building a good architecture and also a great class design.

    The first part deals with building the base for understanding the patterns described in the later part of the book. It doesnt require any prior experience in OSGi and there are around 2 chapters which are very specific to OSGi. The patterns are well described and each has a description, consequences, sample implementation of the pattern.

    The content is quite easy to understand and all the concepts are very well depcited using informative images.

    I would not recommend this book for someone not well versed with basic OOP concepts, code level design patterns. If you have quite a bit of experience and are in a mid-senior level developer then you can really appreciate the content of the book. And its not necessary for you to read through all the patterns in depth, but its useful if you are aware of what patterns are available so that you can refer to it when ever required.

    In short this book tries to bridge the gap between architectural design and the class level design in Java based applications.

    ---
    Disclosure: I received a copy of this book from the publisher in exchange for writing this review on behalf of CodeRanch.
     
    Bartender
    Posts: 2856
    10
    Firefox Browser Fedora Java
    • Mark post as helpful
    • send pies
      Number of slices to send:
      Optional 'thank-you' note:
    • Quote
    • Report post to moderator
    Rating ; I give this book 7 out of 10 horseshoes.
    When we speak of architecture of Java applications, be it desktop or web, we start with the high level specifications, impart service level or functional patterns and move on to the UMLs.
    I have rarely seen any design worrying about modules in the system since we take for granted that our design decouples them implicitly.
    This book was my first encounter with modules with Java and I was surprised to read the importance of modularity in Java applications.
    The first section introduces to the modularity concepts. If you are already familiar with them, you can directly head to patterns in section 2 after taking a brief look at chapter 7.
    The section 2 on patterns is divided into types of patterns making it easy for the reader to focus on what exactly he needs.
    Most of the base patterns stuff I believe is imparted by the design itself, even if its not given special treatment. Module facade was a totally new thing for me, I always thought facade is meant for some service.
    The next section talks of OSGi, which was interesting again because my view of OSGi was that its more into services.
    To put it together it is a good book, with real world examples for novice through intermediate readers and a handy reference for experts. One go-through of the book will certainly bring up better designs and add another facet to the application architecture.

    ---
    Disclosure: I received a copy of this book from the publisher in exchange for writing this review on behalf of CodeRanch.
     
    I'm thinking about a new battle cry. Maybe "Not in the face! Not in the face!" Any thoughts tiny ad?
    We need your help - Coderanch server fundraiser
    https://coderanch.com/wiki/782867/Coderanch-server-fundraiser
    reply
      Bookmark Topic Watch Topic
    • New Topic