Book Image

Java EE 8 Design Patterns and Best Practices

By : Rhuan Rocha, Joao Carlos Purificação
Book Image

Java EE 8 Design Patterns and Best Practices

By: Rhuan Rocha, Joao Carlos Purificação

Overview of this book

Patterns are essential design tools for Java developers. Java EE Design Patterns and Best Practices helps developers attain better code quality and progress to higher levels of architectural creativity by examining the purpose of each available pattern and demonstrating its implementation with various code examples. This book will take you through a number of patterns and their Java EE-specific implementations. In the beginning, you will learn the foundation for, and importance of, design patterns in Java EE, and then will move on to implement various patterns on the presentation tier, business tier, and integration tier. Further, you will explore the patterns involved in Aspect-Oriented Programming (AOP) and take a closer look at reactive patterns. Moving on, you will be introduced to modern architectural patterns involved in composing microservices and cloud-native applications. You will get acquainted with security patterns and operational patterns involved in scaling and monitoring, along with some patterns involved in deployment. By the end of the book, you will be able to efficiently address common problems faced when developing applications and will be comfortable working on scalable and maintainable projects of any size.
Table of Contents (20 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
5
Aspect-Oriented Programming and Design Patterns
Index

Microservices architecture patterns


So far, we have seen that microservices architecture is based on the functional decomposition that produces independent, self-sufficient services that may have different ways of communicating with the outside world using well-defined interfaces. This favors low coupling and well-defined functions, allowing high cohesion (well-defined responsibilities with a reduced number of functions).

Although the services act independently, the purpose of these services is to create an application—that is, a set of business-related functionalities. 

Based on these characteristics, we can extract some patterns that can be used for the implementation of the microservices architecture. Here are some of these patterns:

  • Aggregator pattern
  • Proxy pattern
  • Chained pattern
  • Branch pattern
  • Asynchronous messaging pattern

 

Aggregator pattern

As the name itself suggests, this pattern establishes the existence or creation of a somewhat more complex service that invokes the functions of more...