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 concept of blue/green deployment


Blue/green deployment is very similar to canary deployment in the sense that it deploys new versions of an application using the process of partition. The blue/green method deploys the application into a subset of servers in the production environment and then propagates the new version to the remaining servers. This deployment pattern differs from canary deployment with regard to its goals, because the blue/green deployment aims to reduce an application's downtime during deployment. With canary deployment, however, the goal is to reduce the occurrence of an error in the production environment associated with the new version. Furthermore, with canary deployment, the production environment can stay with both a new version and an old version and receive requests simultaneously, while in a blue/green deployment, only one version responds to requests.

The blue/green deployment is a deployment pattern that makes it possible to deploy a new version...