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 monitoring strategies

To begin with monitoring, you could think of different commonly implemented strategies, as a solution to your problem. Some of the commonly implemented strategies are as follows:

  • Application/system monitoring
  • Real-user monitoring
  • Semantic monitoring and synthetic transactions
  • Profiling
  • Endpoint monitoring

Just bear in mind that each one of these strategies is focused on solving a specific purpose. While one could help to analyze transaction propagation, another could be suitable for testing purposes. So, you need to pick a combination of these, when designing the whole system, since just using a single strategy won't meet your needs.

Monitoring strategies ensure and focus on serving a specific purpose, as discussed in this section. For different purposes, we would require more strategies. So, let's move ahead to that next and discuss...