A domain name is a human-readable hierarchical identifier that DNS translates into an IP address, making services discoverable and reachable through familiar names. section 7.1.3
Platform teams treat naming as a product decision, not merely infrastructure. Consistent domains and subdomains help internal and external users understand which digital product a service belongs to and how to access it. section 7.1.3
Service access through DNS
A customer profile service can be exposed at https://api.epetech.io/v1/profiles. The domain identifies the service family, while the path identifies a specific resource. A platform can provide self-service configuration for delegated zones such as api.epetech.io, dev.api.epetech.io, and preview.epetech.io. 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.
Shows how platform self-service connects domain and subdomain naming decisions with developers’ ability to configure traffic for their services. section 7.1.3

