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)

Understanding the deployment terminology

The microservice deployment terminology is where we code changes until the application's release. In this section, we will discuss all these steps of the deployment terminology, as follows:

  • Build: In the build stage, the service source is compiled without any errors and passes all the corresponding unit tests. This stage produces build artifacts.
  • Continuous integration (CI): CI forces the entire application to build again every time a developer commits any change. The application code is compiled, and a comprehensive set of automated tests are run against it. This practice emerged from the problems of the frequent integration of code in large teams. The basic idea is to keep the delta, or changes to the software, small. This provides confidence that the software is in a workable state. Even if a check-in that&apos...