Want to master Clean Architecture? Go here: https://bit.ly/3PupkOJ
Want to unlock Modular Monoliths? Go here: https://bit.ly/3SXlzSt
Join a community of 1000+ .NET developers: https://www.patreon.com/milanjovanovic
Microservices have revolutionized how we build and scale applications. However, microservices systems are also very dynamic. Services can come and go, scale up or down, and even move around within your infrastructure. This dynamic nature presents a significant challenge. How do your services find and communicate with each other reliably?
Hardcoding IP addresses and ports is a recipe for fragility. If a service instance changes location or a new instance spins up, your entire system could grind to a halt. Service discovery acts as a central directory for your microservices. It provides a mechanism for services to register themselves and discover the locations of other services.
In this video, we'll see how to implement service discovery in your .NET microservices with Consul.
Service Discovery in Microservices With .NET and Consul
https://www.milanjovanovic.tech/blog/service-discovery-in-microservices-with-net-and-consul
Consul Documentation: https://developer.hashicorp.com/consul/docs
Steeltoe Service Discovery: https://docs.steeltoe.io/api/v3/discovery/
Check out my courses:
https://www.milanjovanovic.tech/courses
Read my Blog here:
https://www.milanjovanovic.tech/blog
Join my weekly .NET newsletter:
https://www.milanjovanovic.tech
Chapters
0:00 Service Discovery Introduction
4:16 Hardcoding services communication
9:31 Introducing the Consul service registry
10:42 Configuring the Service Discovery library
16:58 Examining distributed traces with Jaeger