Microservices Observability, Resilience, Monitoring on .Net

When you are developing projects in microservices architecture, it is crucial to following Microservices Observability, Microservices Resilience and Monitoring principles.

So, we will separate our Microservices Cross–Cutting Concerns in 4 main pillars;

Microservices Observability with Distributed Logging using ElastichSearch

Microservices Resilience and Fault Tolerance with Appling Retry and Circuit–Breaker patterns using Polly

Microservices Monitoring with Health Checks using WatchDog

Microservices Tracing with OpenTelemetry using Zipkin

So we are going to follow this 4 main pillars and develop our microservices reference application with using latest implementation and best practices on cloud–native microservices architecture style.

We have already developed this microservices reference application in the microservices course, So with this course, we will extend this microservices reference application with Cross–Cutting Concerns for provide microservices resilience.

We are going to cover;

Cross–Cutting Concerns in 4 main parts;

Microservices Observability with Distributed Logging,

This applying Elastic Stack which includes Elasticsearh + Logstach + Kibana and SeriLog nuget package for .net microservices.

We will docker–compose Kibana image from docker hub and feed Kibana with elastic stack

Microservices Resilience and Fault Tolerance using Polly

This will apply Retry and Circuit–Breaker Design Patterns on microservices communication with creating Polly policies.

Microservices Health Monitoring with using WatchDog

This will be the Aspnet Health Check implementation with custom health check methods which includes database availabilities – for example in basket microservices, we will add sub–health check conditions for connecting Redis and RabbitMQ.