Book Image

Microservices Design Patterns in .NET

By : Trevoir Williams
Book Image

Microservices Design Patterns in .NET

By: Trevoir Williams

Overview of this book

Are you a developer who needs to fully understand the different patterns and benefits that they bring to designing microservices? If yes, then this book is for you. Microservices Design Patterns in .NET will help you appreciate the various microservice design concerns and strategies that can be used to navigate them. Making a microservice-based app is no easy feat and there are many concerns that need to be addressed. As you progress through the chapters of this guide, you’ll dive headfirst into the problems that come packed with this architectural approach, and then explore the design patterns that address these problems. You’ll also learn how to be deliberate and intentional in your architectural design to overcome major considerations in building microservices. By the end of this book, you’ll be able to apply critical thinking and clean coding principles when creating a microservices application using .NET Core.
Table of Contents (21 chapters)
1
Part 1: Understanding Microservices and Design Patterns
8
Part 2: Database and Storage Design Patterns
11
Part 3: Resiliency, Security, and Infrastructure Patterns

Index

As this ebook edition doesn't have fixed pagination, the page numbers below are hyperlinked for reference only, based on the printed edition of this book.

Symbols

.NET

advanced logging options 261

.NET Core

using, as development stack for microservices 12, 13

.NET logging API

using 234-239

A

aggregate ID 73

aggregate pattern

purpose 19

usage 19

aggregate roots 19, 20

aggregates 19, 20

relationships 20

relationships, handling that span 21

versus entities 21

aggregator pattern 15, 249

Amazon Web Services (AWS) 128

anemic domain model

versus rich domain model 23-26

Apache Kafka 47

API gateway pattern 152, 153

advantages 153-155

cache management, adding 164

client (fronted) 152

database 152

disadvantages 155

implementing 155

implementing, with Azure API Management 156

rate limiting, adding 165-167

response aggregation, adding 167-169

server (backend) 152

...