Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
An Atypical ASP.NET Core 6 Design Patterns Guide

You're reading from   An Atypical ASP.NET Core 6 Design Patterns Guide A SOLID adventure into architectural principles and design patterns using .NET 6 and C# 10

Arrow left icon
Product type Paperback
Published in Mar 2022
Publisher Packt
ISBN-13 9781803249841
Length 678 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Carl-Hugo Marcotte Carl-Hugo Marcotte
Author Profile Icon Carl-Hugo Marcotte
Carl-Hugo Marcotte
Arrow right icon
View More author details
Toc

Table of Contents (31) Chapters Close

Preface
1. Section 1: Principles and Methodologies
2. Introduction FREE CHAPTER 3. Automated Testing 4. Architectural Principles 5. Section 2: Designing for ASP.NET Core
6. The MVC Pattern Using Razor 7. The MVC Pattern for Web APIs 8. Understanding the Strategy, Abstract Factory, and Singleton Design Patterns 9. Deep Dive into Dependency Injection 10. Options and Logging Patterns 11. Section 3: Designing at Component Scale
12. Structural Patterns 13. Behavioral Patterns 14. Understanding the Operation Result Design Pattern 15. Section 4: Designing at Application Scale
16. Understanding Layering 17. Getting Started with Object Mappers 18. Mediator and CQRS Design Patterns 19. Getting Started with Vertical Slice Architecture 20. Introduction to Microservices Architecture 21. Section 5: Designing the Client Side
22. ASP.NET Core User Interfaces 23. A Brief Look into Blazor 24. Assessment Answers 25. Acronyms Lexicon
26. Other Books You May Enjoy
27. Index
Appendices
1. Appendix A 2. Appendix B

Implementing the Composite design pattern

The Composite design pattern is another structural GoF pattern that helps us manage complex object structures.

Goal

The goal behind the Composite pattern is to create a hierarchical data structure where you don’t need to differentiate groups of elements from a single element, making the hierarchy easy to use for its consumers.

You could think of the Composite pattern as a way of building a graph or a tree with self-managing nodes.

Design

The design is straightforward; we have components and composites. Both implement a common interface that defines the shared operations. The components are the single nodes, while the composites are collections of components. Let’s take a look at a diagram:

Diagram, schematic  Description automatically generated

Figure 9.7: Composite class diagram

In the preceding diagram, Client depends on an IComponent interface. By doing so, it is unaware of the implementation it is using; it could be a Component or a Composite....

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime