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)

Introducing the strangler pattern

We started our journey of learning in this book by transitioning from monolith applications to microservices-based applications. This transition follows the strangler pattern, which we will discuss in this section.

In simple words, we can define the strangler pattern as a pattern that helps us migrate a legacy application (in our case, a monolith application) continuously, by replacing specific functionality while introducing the new services/applications. Using this pattern, we replace the features of the legacy application that we identified previously, with the new system. To sum this up, a strangler pattern is all about decommissioning the old system after migrating all the required features/functionalities to the new system.

When should you use a strangler pattern?
This pattern should be used when you need to migrate your existing application...