How do microservices find each other's IP addresses?
Service Discovery gives microservices ability to communicate with each other without knowing their IP addresses in advance. How exactly does it work? Let’s find out!
======⚡⚡⚡======
Consider becoming a member of the channel by joining me ❤️
https://www.youtube.com/channel/UCqAL_b-jUOTPjrTSNl2SNaQ/join
👉 Check out Eraser: https://eraser.io
☕ Buy me a coffee: https://www.buymeacoffee.com/softwaredeveloperdiaries
🙌 Become my Patreon and get exclusive perks: https://patreon.com/softdevdiaries
💼 Follow me on LinkedIn and drop me a message if you’d like: https://www.linkedin.com/in/gadirovgs/
💻 Also, let’s connect on GitHub: https://github.com/gusgad
📚 Resources:
More on Service Discovery: https://www.baeldung.com/cs/service-discovery-microservices
Consul: https://www.npmjs.com/package/consul
Netflix Eureka: https://cloud.spring.io/spring-cloud-netflix/reference/html/
AWS ELB: https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-deregister-register-instances.html
And don’t forget to subscribe for more videos like this 😊
#microservices
ip address
Do you wanna learn about microservices together with me? Then make sure you hit that "subscribe" button
I use bash, nginx, and built in Linux utils to accomplish this type of load balancing. And some cloudflare rules / dns config
Please more such content 🔥 also, hands on if possible
Brother can You make a whole paid course where you discuss
All backend and devops with cloud I want to learn these skillss I only know frontend. Plzz make a course like that I will buy It plzz plzz❤
Taking this idea a bit further, service meshes act a little bit like an intelligent sidecar for containers for things like service discovery by knowing all the instances of a database that are available and when your service tries to access the database, the sidecar selects the appropriate instance to send the request to so doing load balancing and service discovery in the same package, but totally disconnected from your service. So your service gets these features automatically by sitting in the middle of all the dns resolution. All of the configuration updates in real time, so if you scale up your database. The sidecars can use the new instances without having to restart anything.