Book Image

Hands-On Microservices with C# 8 and .NET Core 3 - Third Edition

By : Gaurav Aroraa, Ed Price
Book Image

Hands-On Microservices with C# 8 and .NET Core 3 - Third Edition

By: Gaurav Aroraa, Ed Price

Overview of this book

<p>The microservice architectural style promotes the development of complex applications as a suite of small services based on specific business capabilities. With this book, you'll take a hands-on approach to build microservices and deploy them using ASP .NET Core and Microsoft Azure. </p><p>You'll start by understanding the concept of microservices and their fundamental characteristics. This microservices book will then introduce a real-world app built as a monolith, currently struggling under increased demand and complexity, and guide you in its transition to microservices using the latest features of C# 8 and .NET Core 3. You'll identify service boundaries, split the application into multiple microservices, and define service contracts. You'll also explore how to configure, deploy, and monitor microservices using Docker and Kubernetes, and implement autoscaling in a microservices architecture for enhanced productivity. Once you've got to grips with reactive microservices, you'll discover how keeping your code base simple enables you to focus on what's important rather than on messy asynchronous calls. Finally, you'll delve into various design patterns and best practices for creating enterprise-ready microservice applications. </p><p>By the end of this book, you'll be able to deconstruct a monolith successfully to create well-defined microservices.</p>
Table of Contents (16 chapters)

Trying out the coding of reactive microservices

As discussed in the initial chapters, we need to get ready for big changes, when embracing microservices. The discussions we've presented on deployment, security, and testing, so far, would have had you thinking by now about accepting this fact. Unlike monoliths, the adoption of microservices requires you to prepare beforehand, so that you start building the infrastructure along with it, and not after it's done.

In a way, microservices thrive in a complete ecosystem where everything is worked out, from deployment to testing, security, and monitoring. The returns associated with embracing such a change are huge. There is definitely a cost involved in making all of these changes. However, instead of having a product that doesn't make it to the market, it is better to incur some costs, and then to design and...