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
1
Section 1: Introducing Design Patterns
4
Section 2: Original Design Patterns
8
Section 3: New Design Patterns

Understanding the fan-out and quickest-reply design pattern

The fan-out and quickest-reply reactive design pattern emphasizes rapid processing. Financial software that provides real-time, or near real-time, stock information uses this design pattern. The concept is to provide sufficient processing instances so requests can be processed without waiting in a queue.

To implement the fan-out and quickest-reply design pattern, we send each request to multiple processing modules. Each of those modules would process the request and send the results back to the requestor. The requestor would use the quickest reply, the first one received, and simply ignore the rest:

Fan-out and quickest-reply design pattern

As you would expect, the extra processing could make it a costly use of resources, so this approach should only be used when quick replies are of utmost importance.

This section...