A right-of-domain pattern organizes service capabilities and resources beneath a domain selected and controlled by the platform. The platform reserves the domain and standard traffic-entry patterns, while internal teams self-manage naming within those boundaries. section 7.1.3
A practical rollout separates ownership levels:
- Reserve a platform-managed domain such as epetech.io and provide standard DNS subdomains and ingress patterns. section 7.1.3
- Let teams self-manage names beneath the reserved domain without allowing them to create new top-level subdomains. section 7.1.3
- Expand incrementally to customer-managed subdomains or custom domains only when additional customization proves valuable. section 7.1.3
Epetech traffic entry
Epetech places APIs under api.epetech.io, with DNS pointing to an API gateway that redirects traffic to the actual API. Similar patterns support test, development, preview, and UI traffic. section 7.1.3
Figure 7.3 Our engineering platform must provide a self-serve experience for each internal customer (development team) to configure their service to receive traffic based on our company’s “product” decision for how the DNS domain and subdomain names reflect our digital products.
Use the platform’s self-service experience to configure how each service receives traffic and how product-oriented DNS names map to services. section 7.1.3
