book

Microservices Design Patterns in .NET

by Trevoir Williams

January 2023

Intermediate to advanced

300 pages

7h 36m

English

Packt Publishing

Read now

Unlock full access

ContributorsAbout the authorAbout the reviewer
Who this book is forWhat this book coversTo get the most out of this bookDownload the example code filesDownload the color imagesConventions usedGet in touchShare Your ThoughtsDownload a free PDF copy of this book
A deep dive into microservices and its key elementsBuilding a monolithBuilding microservicesAssessing the business need for microservicesScalabilityAvailabilityDevelopment speedImproved data storageMonitoringDeploymentDetermining the feasibility of implementing microservicesMicroservices and .NET CoreSummary
Technical requirementsExploring DDD and its significanceExploring the pros and cons of DDDDDD and microservicesThe purpose and use of aggregate patternsAggregates and aggregate rootsRelationships in aggregatesHandling relationships that span aggregatesAggregates versus entitiesEntities and why we need themPractical uses of entities in codeA rich domain model versus an anemic domain modelUnderstanding and using value objectsSummary
Technical requirementsUse cases for synchronous communicationChallenges of microservice communicationImplementing synchronous communicationImplementing HTTP synchronous communicationImplementing gRPC synchronous communicationHTTP versus gRPC communicationDisadvantages of synchronous communication between microservicesSummary
Technical requirementsFunctioning with asynchronous communicationHTTP asynchronous communicationUnderstanding Pub-Sub communicationUnderstanding message queuesUnderstanding message bus systemsUnderstanding eventual consistencyConfiguring a message bus (RabbitMQ or Azure Service Bus)Implementing RabbitMQ in an ASP.NET Core web APIImplementing Azure Service Bus in an ASP.NET Core APIDisadvantages of asynchronous communication between microservicesSummary
Technical requirementsWhy use CQRS for microservices development?Benefits of the CQRS patternDisadvantages of the CQRS patternUsing the Mediator pattern with CQRS in .NETImplementing a commandCreating a command modelCreating a command handlerInvoking a commandImplementing a queryCreating a query modelCreating a query handlerInvoking a querySummary
Technical requirementsWhat are events?Key attributes of eventsWhat can event sourcing patterns do for me?Pros of event sourcingCons of event sourcingWhat are domain events?Domain events and event sourcingExploring domain events in our applicationCreating an event storeHow to store eventsImplementing event sourcing using a relational databaseImplementing event sourcing using a non-relational databaseReading state with CQRSSummary

Technical requirementsHow to make use of the Database-Per-Service patternA single database technology per serviceUsing different database technologies per serviceDisadvantages of this patternDeveloping a databaseRelational databasesNon-relational databasesChoosing a database technologyChoosing an ORMChoosing a database development techniqueImplementing the repository patternSummary
Exploring the Saga patternIssues and considerationsUnderstanding and implementing choreographyRolling back on failurePros and consUnderstanding and implementing orchestrationRolling back on failurePros and consSummary
Technical requirementsThe importance of service resiliencyPossible failure scenarios and how to handle themImplementing resiliency with caching and message brokersUsing a message brokerUsing a caching layerUsing Redis CacheImplementing retry and circuit breaker policiesRetry policy with PollyCircuit breaker policy with PollySummary
Technical requirementsHealth checks and microservicesThe liveness health checkReadiness health checksImplementing ASP.NET Core health checksAdding liveness health checksAdding readiness health checksConfiguring health probes in orchestratorsSummary
Technical requirementsWhat is the API gateway pattern?Advantages of an API gatewayDisadvantages of an API gatewayImplementing the API gateway patternThick API gatewaysImplementing an API gateway using Azure API ManagementImplementing an API gateway using OcelotAdding cache managementAdding rate limitingAdding response aggregationBackend for Frontend patternBFF pattern using OcelotSummary
Technical requirementsBearer tokens for securing communicationsUnderstanding bearer tokensImplementing bearer token securitySecuring API with bearer tokensGenerating and issuing bearer tokensUsing IdentityServer4 to secure microservicesConfiguring IdentityServerSecuring an API using IdentityServerSecuring the Ocelot API gateway with IdentityServerAdditional API security considerationsSummary
Technical requirementsUsing containers in microservices developmentWhat can containers do for me?Understanding DockerUnderstanding container imagesPros and cons of containersAuthoring a DockerfileLaunching a containerized applicationUsing native .NET container supportUnderstanding docker-compose and imagesAdding docker-compose to a projectPublishing containers to a container registryPublic versus private container registriesCreating and uploading custom imagesSummary
Technical requirementsLogging and its importanceChoosing what to logUsing the .NET logging APIAdding SerilogLog aggregation and its usesIntegrating with SeqDistributed log tracingEnhanced logging for distributed tracingSummary
Aggregator patternSynchronous and asynchronous communicationCQRSEvent sourcing patternsDatabase per service patternRelational databasesNon-relational databasesOne database for all servicesOne database per serviceUsing the saga pattern across servicesResilient microservicesImportance of health checksAPI Gateways and backend for frontendBearer token securityContainers and microservicesCentralized loggingSummary
Other Books You May EnjoyPackt is searching for authors like youShare Your ThoughtsDownload a free PDF copy of this book

Overview

Microservices Design Patterns in .NET is your comprehensive guide to effectively designing microservice architectures using .NET Core. Throughout this book, you will learn foundational and advanced design patterns, implement scalable architecture principles, and address common challenges encountered in microservices development. This is your step-by-step journey to mastering microservices in .NET.

What this Book will help me do

Master applying Domain-Driven Design (DDD) principles to microservice development
Learn and apply structural patterns such as event sourcing and CQRS
Understand and implement resilient design like circuit breaking and fault tolerance
Ensure data consistency across microservice boundaries
Secure your microservices infrastructure using best practices and industry standards

Author(s)

Trevoir Williams is a seasoned software architect and developer with years of expertise in designing and implementing microservices-based solutions. His experience within the software industry spans creating scalable and robust distributed systems using modern technologies. His pragmatic approach to teaching helps developers solve real-world challenges in designing microservices-based systems.

Who is it for?

This book is designed for .NET developers, software architects, and DevOps engineers at intermediate to advanced levels. Readers should be familiar with application and API development in .NET Core and have interest in mastering microservices architecture. If you aim to design resilient and efficient distributed systems, this book will be an invaluable resource.