Service Mesh and Discovery
Koyeb provides a built-in service discovery mechanism to easily connect to other internal services of your application. This is coupled with a service mesh to ensure all inter-service communication is encrypted.
Service mesh
Services deployed in a Koyeb App can communicate with each other using a private mesh network. You can use both IPv4 and IPv6 to interact with your resources inside the mesh. The mesh network is available within the regions used by your App.
No configuration is needed to benefit from the service mesh. Just use the provided private domain that looks use the <SERVICE_NAME>.<APP_NAME>
format.
Free instances are excluded from the mesh network. This means that free instances don't receive a private domain and can't communicate with your other resources inside the mesh .
Service discovery
Each service you deploy in a Koyeb App comes with a unique private domain name based on the service name. This allows you to easily communicate with other internal services using a predictable naming system.
The table below shows different ways you can reach a service within a Koyeb App:
name | status | details |
---|---|---|
<SERVICE_NAME> | available | Reach a Service Instance across all regions. |
<SERVICE_NAME>.<APP_NAME>.internal | available | Reach a Service Instance within the same region. |
<REGION_NAME>.<SERVICE_NAME>.<APP_NAME>.internal | coming soon | Reach an Instance of the Service in a specific region. |