Book Image

Hands-On Design Patterns with Java

By : Dr. Edward Lavieri
2 (1)
Book Image

Hands-On Design Patterns with Java

2 (1)
By: Dr. Edward Lavieri

Overview of this book

Java design patterns are reusable and proven solutions to software design problems. This book covers over 60 battle-tested design patterns used by developers to create functional, reusable, and flexible software. Hands-On Design Patterns with Java starts with an introduction to the Unified Modeling Language (UML), and delves into class and object diagrams with the help of detailed examples. You'll study concepts and approaches to object-oriented programming (OOP) and OOP design patterns to build robust applications. As you advance, you'll explore the categories of GOF design patterns, such as behavioral, creational, and structural, that help you improve code readability and enable large-scale reuse of software. You’ll also discover how to work effectively with microservices and serverless architectures by using cloud design patterns, each of which is thoroughly explained and accompanied by real-world programming solutions. By the end of the book, you’ll be able to speed up your software development process using the right design patterns, and you’ll be comfortable working on scalable and maintainable projects of any size.
Table of Contents (15 chapters)
Free Chapter
Section 1: Introducing Design Patterns
Section 2: Original Design Patterns
Section 3: New Design Patterns

Introducing reactive design patterns

Reactive design patterns exist to provide system architects, engineers, and developers with the ability to create systems that are, at their core, responsive and scalable. Using a reactive design pattern helps ensure that a system will be both maintainable and able to react to external changes such as resource changes and new connectivity. One of the goals of creating systems with one of these design patterns was to avoid redesigning the system because it was not responsive to change.

The concept of designing systems that are reactive to change can be considered an approach to future-proofing a system. We want, as much as possible, to design our systems so they can react to events and changes for the foreseeable future.

Reactive design patterns were generated from reactive programming and documented in the form of a Reactive Manifesto. This...