Sean Whitesell - Pro Microservices in .NET 6: With Examples Using ASP.NET Core 6, MassTransit, and Kubernetes

Sean Whitesell , Rob Richardson and Matthew D. Groves

Pro Microservices in .NET 6

With Examples Using ASP.NET Core 6, MassTransit, and Kubernetes

Foreword by Scott Hunter VP Director, Azure Developer Experience Microsoft

Logo of the publisher

This book is dedicated to you, the reader. Writing good software is hard enough. Learning and conquering the development of microservices is an even greater challenge. I hope this book serves you well in your journey to developing great solutions for your users.

The microservice architecture breaks software into smaller pieces that can be independently deployed, scaled, and replaced. There are many benefits to this modern architecture, but there are more moving pieces.

In the olden days, we compiled the entire software product into one piece and deployed it infrequently. Deployment was hard, so we opted not to do it very often. With the advent of containers, deployment has become much easier. We can now break our application into lots of little pieces microservices. When one microservice needs more horsepower, we can scale up only this portion of the web property. If a feature needs to work differently, we can deploy only this microservice, avoiding the churn with the entire system.

With this power come some additional layers of complexity. In the legacy monolithic software applications, we merely made a function call if we wanted to call into another part of the system. Our internal methods now have IP addresses, multiple instances, maybe load balancers distributing the load, and many more moving pieces.

How do we discover the address of the microservice? How do we scale to just the right level of availability without wasted cost? This is the magic of microservices, and this is the purpose of this book. Youll learn how to design, architect, scale, monitor, and containerize applications to build robust and scalable microservices.

In some respect, anyone involved with software projects related to distributed architecture should read this book. Even if a software project is not a distributed architecture but may become one, this book will shed some light on understanding existing business processes that may need to be handled by microservices.

From development managers to product owners to developers will find this book useful in understanding many complexities of a microservices architecture. Application architects and developers will gain quick insight with the hands-on code samples. The step-by-step coding approach covers examples with direct microservice calls as well as by messaging communication.

The microservices architecture is multifaceted and complex. Chapter , we use a fictional story to help convey the purpose of breaking apart a monolithic application to a microservices architecture. We cover using Event Storming and Domain-Driven Design tenants to help understand existing business processes to determine where and why to create a microservice.

In Chapter covers the messaging communication style. Also, you will create more microservices that communicate using MassTransit for messaging.

Chapter covers breaking apart data from a centralized data store to distributed data stores. We also cover Saga patterns for handling transactions across multiple systems.

In Chapter , we cover testing the microservices using direct communication. We also cover testing the microservices that communicate using messaging. You will create the test projects for both communication styles.

Chapter covers hosting microservices in Docker containers as well as using Kubernetes. By understanding containerization options, you understand how to handle the scaling of microservices.

In Chapter , we cover health concerns for microservices. The microservices developed in earlier chapters only have business logic. This chapter covers logging concerns, gathering metrics, tracing, and points for debugging.