Book Image

Hands-On Design Patterns with C# and .NET Core

By : Gaurav Aroraa, Jeffrey Chilberto
Book Image

Hands-On Design Patterns with C# and .NET Core

By: Gaurav Aroraa, Jeffrey Chilberto

Overview of this book

Design patterns are essentially reusable solutions to common programming problems. When used correctly, they meet crucial software requirements with ease and reduce costs. This book will uncover effective ways to use design patterns and demonstrate their implementation with executable code specific to both C# and .NET Core. Hands-On Design Patterns with C# and .NET Core begins with an overview of object-oriented programming (OOP) and SOLID principles. It provides an in-depth explanation of the Gang of Four (GoF) design patterns, including creational, structural, and behavioral. The book then takes you through functional, reactive, and concurrent patterns, helping you write better code with streams, threads, and coroutines. Toward the end of the book, you’ll learn about the latest trends in architecture, exploring design patterns for microservices, serverless, and cloud native applications. You’ll even understand the considerations that need to be taken into account when choosing between different architectures such as microservices and MVC. By the end of the book, you will be able to write efficient and clear code and be comfortable working on scalable and maintainable projects of any size.
Table of Contents (19 chapters)
Free Chapter
1
Section 1: Essentials of Design Patterns in C# and .NET Core
4
Section 2: Deep Dive into Utilities and Patterns in .NET Core
10
Section 3: Functional Programming, Reactive Programming, and Coding for the Cloud

Use case discussion

Put simply, a use case is a pre-creation or a symbolic representation of a business scenario. For example, we can represent our login page use case in a pictorial/symbolic representation. In our example, users are trying to log into a system. If the login succeeds, they can enter the system. If it fails, the system informs the users that the login attempt failed. Refer to the following diagram of a login use case:

In the preceding diagram, users called User1, User2, and User3 are trying to enter the system using the login functionality of the application. If the login attempt is successful, the user can access the system. If not, the application notifies the user that login wasn't successful and the user can't access the system. The preceding diagram is much clearer than our actual verbose description, where we are describing this diagram. The diagram...