3 Comments
User's avatar
тна Return to thread
Arvind Ramaswamy's avatar

Thanks Saurabh! I have used API Gateway (Ocelot) to map a standard URL API (of the gateway), which the calling systems will use, to the actual APIs residing on diff locations using a json mapping. How exactly is this different from Service Discovery? Are these 2 different or is there a real-world scenario where they can complement each other?

Expand full comment
Saurabh Dashora's avatar

Hi Arvind...service discovery is complementary to API Gateway.

Service discovery is used to locate and connect to instances of services dynamically without worrying about IP addresses or hostnames. This is useful in environments where service instances can go down (like pods in Kubernetes or containers) and new instances are automatically created.

Each instance registers with the service discovery system. The API Gateway can act as an entry point for clients with a standard URL and internally use service discovery to route the requests to specific instances.

Expand full comment
Arvind Ramaswamy's avatar

Thanks a lot Saurabh!

Expand full comment