Book Image

An Atypical ASP.NET Core 5 Design Patterns Guide

By : Carl-Hugo Marcotte
Book Image

An Atypical ASP.NET Core 5 Design Patterns Guide

By: Carl-Hugo Marcotte

Overview of this book

Design patterns are a set of solutions to many of the common problems occurring in software development. Knowledge of these design patterns helps developers and professionals to craft software solutions of any scale. ASP.NET Core 5 Design Patterns starts by exploring basic design patterns, architectural principles, dependency injection, and other ASP.NET Core mechanisms. You’ll explore the component scale as you discover patterns oriented toward small chunks of the software, and then move to application-scale patterns and techniques to understand higher-level patterns and how to structure the application as a whole. The book covers a range of significant GoF (Gangs of Four) design patterns such as strategy, singleton, decorator, facade, and composite. The chapters are organized based on scale and topics, allowing you to start small and build on a strong base, the same way that you would develop a program. With the help of use cases, the book will show you how to combine design patterns to display alternate usage and help you feel comfortable working with a variety of design patterns. Finally, you’ll advance to the client side to connect the dots and make ASP.NET Core a viable full-stack alternative. By the end of the book, you’ll be able to mix and match design patterns and have learned how to think about architecture and how it works.
Table of Contents (27 chapters)
1
Section 1: Principles and Methodologies
5
Section 2: Designing for ASP.NET Core
11
Section 3: Designing at Component Scale
15
Section 4: Designing at Application Scale
21
Section 5: Designing the Client Side
25
Acronyms Lexicon

Anatomy of a web API

Now that we have explored the basics of ASP.NET MVC in Chapter 4, The MVC Pattern using Razor, and a way to render web pages, it is time to jump into web APIs and return data instead of a user interface. In the past few years, the number of web APIs just exploded from a few to a gazillion of them; everybody does that nowadays. In this case, I don't think that's because people are blindly following a trend, but based on good reasons that make web APIs so appealing, such as the following:

  • It is an efficient way of sharing data between systems.
  • It allows interoperability between technologies by dialoguing in universal languages, such as JSON or XML.
  • It allows your backend to be centralized and shared with multiple frontends such as mobile, desktop, and web applications.

Those reasons make it easier to reuse backend systems and share them with multiple user interfaces or other backend systems. For example, think of any mobile app that...