Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Hands-On Design Patterns with Java
  • Toc
  • feedback
Hands-On Design Patterns with Java

Hands-On Design Patterns with Java

By : Dr. Edward Lavieri Jr.
2 (1)
close
Hands-On Design Patterns with Java

Hands-On Design Patterns with Java

2 (1)
By: Dr. Edward Lavieri Jr.

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

Understanding the self-containment design pattern

Systems that employ the self-containment reactive design pattern are not reliant on non-system components. This design pattern can also be applied at the system component level. In that instance, a system component would be self-contained and not rely on other system components.

To examine the self-containment reactive design pattern, let's first consider a system diagram depicting a lack of self-containment. As you can see from the next diagram, the Financial Services API is the only system component with access to the Payment Gateway and the related database. Both the New Vehicle Sales and service department sales shown by Service Dept Sales nodes, rely on the Financial Services API for access to its sub-components:

System in need of the self-containment design pattern

This architecture is not advised, as the reliance that...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete