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

Explaining the Session Façade pattern


Before we introduce the Session Façade pattern, it is important to cover the façade patterns, which are one of the structural design patterns mentioned in the Gang of Four (GoF) book.

The main goal is to encapsulate the complexity of business logic in a business interface. Broadly speaking, this interface only exposes a small number of coarse-grained methods to the client. Each of these interface methods is responsible for controlling the underlying complexity of business logic. In this way, the internal services of finer granularity can be combined into a set of services that are exposed by the interface method.

The benefits of using a façade pattern are as follows:

  • It provides coarse‐grained methods for available services.
  • It reduces remote calls. A remote client does not need to call many fine-grained business objects. Instead, it executes a remote call to the exposed interface method, which is responsible for making local calls to the fine-grained objects...