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)

The Anti-Corruption Layer pattern

In this pattern, two different subsystems do not share the same semantics, but they can talk to each other with the implementation of a layer (mostly with the help of the Facade or Adapter patterns). The layer works in such a way that a request made by one subsystem reaches out and talks to another subsystem. In this section, we will discuss the Anti-Corruption Layer, from the perspective of our FlixOne application.

Maintaining access to new and legacy systems requires that the new system adheres to at least some of the APIs or other semantics of the legacy system. If these legacy apps have problems with consistency, then they corrupt what could otherwise be a cleanly crafted modern application. These issues or problems can also arise in an existing system that you want to connect with an external/legacy system. To sort out these...