Greeting! In a monolithic architecture we have all our business logic in one place. We can directly use relevant service through the respective component. When it comes to microservices our business logic is in multiple places working independently. This introduces new problems. How does a service find another service? (hard code url hah?) How do we monitor health conditions? Maintaining address, port How to load balance for dynamic IPs. How about another microservice to handle all these problems? Get the complete source code. Service Registry And Discovery Pattern Service registry is like your address book. It has all the address' you need. When you need to find a place, you get the address book to locate it. Service registry is doing exactly the same thing. It maintains other microservices names, addresses, ports, health. Other microservices register themselves with the registry with necessary information. Discovery service relying on the heartbeat for serv
May all beings be happy, be well, be peaceful, and be free