# Cloud-Native Service Discovery

> Let the cloud manage service discovery — no Eureka cluster to babysit.

- **Category**: Microservices
- **Subcategory**: Service Discovery
- **Canonical URL**: https://designpattern.fyi/patterns/cloud_service_discovery/

---

## Description
Clean, reusable architecture pattern.


## Use Cases
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.





## Trade-offs


### 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




### Considerations & Drawbacks

- 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







---
**Reference**: [Original Source](https://www.factualminds.com/blog/microservices-design-patterns-aws-production-guide-2026)