book

Microservices in .NET, Second Edition

by Christian Horsdal Gammelgaard

October 2021

Intermediate to advanced

328 pages

9h 18m

English

Manning Publications

Read now

Unlock full access

prefaceacknowledgmentsabout this bookWho should read this bookAbout the codeliveBook discussion forumabout the authorabout the cover illustration
1.1 What is a microservice?1.2 What is a microservices architecture?1.2.1 Microservice characteristics1.3 Why microservices?1.3.1 Enabling continuous delivery1.3.2 High level of maintainability1.3.3 Robust and scalable1.4 Costs and downsides of microservices1.5 Greenfield vs. brownfield1.6 Code reuse1.7 Serving a user request: An example of how microservices work in concert1.7.1 Main handling of the user request1.7.2 Side effects of the user request1.7.3 The complete picture1.8 A .NET microservices technology stack1.8.1 ASP.NET and MVC1.8.2 Kubernetes1.8.3 Setting up a development environment1.9 A simple microservices example1.9.1 Creating an empty ASP.NET application1.9.2 Adding ASP.NET MVC to the project1.9.3 Adding an MVC controller with an implementation of the endpointSummary
2.1 Overview of the Shopping Cart microservice2.1.1 Components of the Shopping Cart microservice2.2 Implementing the Shopping Cart microservice2.2.1 Creating an empty project2.2.2 The Shopping Cart microservice’s API for other services2.2.3 Fetching product information2.2.4 Parsing the product response2.2.5 Adding a failure-handling policy2.2.6 Implementing a basic event feed2.3 Running the codeSummary
3.1 Choosing a production environment3.2 Putting the Shopping Cart microservice in a container3.2.1 Adding a Dockerfile to the Shopping Cart microservice3.2.2 Building and running the shopping cart container3.3 Running the shopping cart container in Kubernetes3.3.1 Setting up Kubernetes localhost3.4 Creating Kubernetes deployment for the shopping cart3.5 Running the shopping cart container on Azure Kubernetes Service3.5.1 Setting up AKS3.5.2 Running the shopping cart in AKSSummary

4.1 The primary driver for scoping microservices: Business capabilities4.1.1 What is a business capability?4.1.2 Identifying business capabilities4.1.3 Example: Point-of-sale system4.2 The secondary driver for scoping microservices: Supporting technical capabilities4.2.1 What is a technical capability?4.2.2 Examples of supporting technical capabilities4.2.3 Identifying technical capabilities4.3 The tertiary driver for scoping microservices: Supporting efficiency of work4.4 What to do when the correct scope isn’t clear4.4.1 Starting a bit bigger4.4.2 Carving out new microservices from existing microservices4.4.3 Planning to carve out new microservices later4.5 Well-scoped microservices adhere to the microservice characteristics4.5.1 Primary scoping to business capabilities leads to good microservices4.5.2 Secondary scoping to support technical capabilities leads to good microservices4.5.3 Tertiary scoping to support efficiency of workSummary
5.1 Types of collaboration: Commands, queries, and events5.1.1 Commands and queries: Synchronous collaboration5.1.2 Events: Asynchronous collaboration5.1.3 Data formats5.2 Implementing collaboration5.2.1 Setting up a project for the loyalty program5.2.2 Implementing commands and queries5.2.3 Implementing commands with HTTP POST or PUT5.2.4 Implementing queries with HTTP GET5.2.5 Implementing an event-based collaboration5.2.6 Deploying to Kubernetes5.2.7 Building a Docker container special offers microservice5.2.8 Building a Docker container for both parts of the loyalty program5.2.9 Deploying the loyalty program API and the special offers5.2.10 Deploy EventConsumerSummary
6.1 Each microservice has a data store6.2 Partitioning data between microservices6.2.1 Rule 1: Ownership of data follows business capabilities6.2.2 Rule 2: Replicate for speed and robustness6.2.3 Where does a microservice store its data?6.3 Implementing data storage in a microservice6.3.1 Preparing a development setup6.3.2 Storing data owned by a microservice6.3.3 Storing events raised by a microservice6.3.4 Setting cache headers in HTTP responses6.3.5 Reading and using cache headersSummary
7.1 Expect failures7.1.1 Keeping good logs7.1.2 Using trace IDs7.1.3 Rolling forward vs. rolling backward7.1.4 Don’t propagate failures7.2 The client side’s responsibility for robustness7.2.1 Robustness pattern: Retry7.2.2 Robustness pattern: Circuit breaker7.3 Implementing robustness patterns7.3.1 Implementing a fast-paced retry strategy with Polly7.3.2 Implementing a circuit breaker with Polly7.3.3 Implementing a slow-paced retry strategy7.3.4 Logging all unhandled exceptions7.3.5 Deploying to KubernetesSummary
8.1 What and how to test8.1.1 The test pyramid: What to test in a microservices system8.1.2 System-level tests: Testing a complete microservice system end to end8.1.3 Service-level tests: Testing a microservice from outside its process8.1.4 Unit-level tests: Testing endpoints from within the process8.2 Testing libraries: Microsoft.AspNetCore.TestHost and xUnit8.2.1 Meet Microsoft.AspNetCore.TestHost8.2.2 Meet xUnit8.2.3 xUnit and Microsoft.AspNetCore.TestHost working together8.3 Writing unit tests using Microsoft.AspNetCore.TestHost8.3.1 Setting up a unit-test project8.3.2 Using the TestServer and HttpClient to unit-test endpoints8.3.3 Injecting mocks into endpoints8.4 Writing service-level tests8.4.1 Creating a service-level test project8.4.2 Creating mocked endpoints8.4.3 Executing the test scenario against the microservice under testSummary
9.1 Monitoring needs in microservices9.2 Logging needs in microservices9.2.1 Tracing requests across microservices9.2.2 Structured logging with Serilog9.3 Implementing the monitoring endpoints9.3.1 Implementing the /health/live monitoring endpoint9.3.2 Implementing the /health/startup monitoring endpoint9.4 Implementing structured logging9.4.1 Adding a trace ID to all log messages9.4.2 Trace ID is included in outgoing HTTP requests9.4.3 Logging unhandled exceptions9.5 Implementing monitoring and logging in Kubernetes9.5.1 Configure monitoring in KubernetesSummary
10.1 Microservice security concerns10.1.1 Authenticating users at the edge10.1.2 Authorizing users in microservices10.1.3 How much should microservices trust each other?10.2 Implementing secure microservice-to-microservice communication10.2.1 Accessing the user identity in the loyalty program10.2.2 Limiting which microservices can communicateSummary
11.1 Creating a new microservice should be quick and easy11.2 Handling cross-cutting concerns11.3 Creating a reusable microservice platform11.4 Packaging and sharing cross-cutting code with NuGet11.4.1 Creating a logging package11.4.2 Creating a package with monitoring endpoints11.5 The ASP.NET pipeline11.5.1 What belongs in middleware?11.6 Writing middleware11.6.1 Middleware as lambdas11.6.2 Middleware classes11.7 Testing middleware and pipelinesSummary
12.1 End user applications for microservice systems: One or many applications?12.1.1 General-purpose applications12.1.2 Specialized applications12.2 Patterns for building applications over microservices12.2.1 Composite applications: Integrating at the frontend12.2.2 API Gateway12.2.3 Backend for frontend (BFF) pattern12.2.4 When to use each pattern12.2.5 Client-side or server-side rendering?12.3 Example: A shopping cart and a product list12.3.1 Creating an API Gateway12.3.2 Creating the product list GUI12.3.3 Creating the shopping cart GUI12.3.4 Letting users add products to the shopping cart12.3.5 Letting users remove products from the shopping cartSummary
A.1 Setting up an IDEA.1.1 Visual StudioA.1.2 Visual Studio CodeA.1.3 JetBrains RiderA.2 Setting up the dotnet command-line interfaceA.3 Setting up REST client in VS CodeA.4 Docker and KubernetesA.5 Azure CLI

Overview

In Microservices in .NET, Second Edition you will learn how to:

Build scalable microservices that are reliable in production
Optimize microservices for continuous delivery
Design event-based collaboration between microservices
Deploy microservices to Kubernetes
Set up Kubernetes in Azure

Microservices in .NET, Second Edition is a comprehensive guide to building microservice applications using the .NET stack. After a crystal-clear introduction to the microservices architectural style, it teaches you practical microservices development skills using ASP.NET. This second edition of the bestselling original has been revised with up-to-date tools for the .NET ecosystem, and more new coverage of scoping microservices and deploying to Kubernetes.

About the Technology
Microservice architectures connect independent components that must work together as a system. Integrating new technologies like Docker and Kubernetes with Microsoft’s familiar ASP.NET framework and Azure cloud platform enables .NET developers to create and manage microservices efficiently.

About the Book
Microservices in .NET, Second Edition teaches you to build and deploy microservices using ASP.NET and Azure services. It lays out microservice architecture simply, and then guides you through several real-world projects, such as building an ecommerce shopping cart. In this fully revised edition, you’ll learn about scoping microservices, deploying to Kubernetes, and operations concerns like monitoring, logging, and security.

What's Inside

Optimize microservices for continuous delivery
Design event-based collaboration between microservices
Deploy microservices to Kubernetes
Set up Kubernetes in Azure

About the Reader
For C# developers. No experience with microservices required.

About the Author
Christian Horsdal is an independent consultant with more than 20 years of experience building projects from large-scale microservice systems to tiny embedded systems.

Quotes
A clear presentation of the latest best practices. A highly recommended read.
- David Paccoud, Bioclinica

Recommended for all developers and software architects looking to jump into the microservices world.
- Emanuele Origgi, Datlas

This book is the best guide to learn about microservices and how to implement on .NET framework.
- Jeff Smith, Agilify Automation

Well-written, concise, and comprehensive. I could not put it down and would definitely recommend it.
- Tanya Wilke, Sanlam