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)

Summary

Testing microservices is a bit different from testing applications that have been built in the traditional architectural style. In a .NET monolithic application, testing is a bit easier, compared to microservices, and it provides implementation independence and short delivery cycles. Microservices face challenges while testing.

With the help of the testing pyramid concept, we can strategize our testing procedures. In terms of the testing pyramid, we can easily see that unit tests allow us to test a small function of a class, and they are less time-consuming. On the other hand, the top layer of the testing pyramid has a large scope, with system or end-to-end testing, and these tests are time-consuming and very expensive. Consumer-driven contracts are a very useful way to test microservices. Pact-net is an open source tool that's used for this purpose. Finally, we went...