Back to Catalog
Microservices
Service Discovery
Cloud-Native Service Discovery
Let the cloud manage service discovery — no Eureka cluster to babysit.
Intent & Description
Real-world Use Case
ECS services register automatically via Service Connect. Order Service calls payment.internal — resolves via Cloud Map DNS to the Payment Service’s healthy instances. No Eureka. No Consul. No custom infra.
Source
📌 TL;DR
Cloud-native service discovery = managed Eureka. Let AWS do the ops work. Accept the vendor lock-in trade-off.
Advantages
- Zero infrastructure to manage — fully platform-owned
- Tight AWS integration — IAM, VPC, Route 53, CloudWatch
- Auto-scaling and health deregistration built in
- Reduces operational burden on platform/infra teams
Disadvantages
- AWS vendor lock-in — not portable to GCP, Azure, or on-prem
- Limited customization vs self-managed Consul
- Costs money (Cloud Map charges per registered instance + queries)
- Multi-cloud architectures need a different approach