Tye is a tool that makes developing, testing, and deploying microservices and distributed applications easier. Project Tye includes a local orchestrator to make developing microservices easier and the ability to deploy microservices to Kubernetes with minimal configuration.
MIT License
5.28k
stars
520
forks
source link
Implement Consul like functions in control plane #487
What should we add or change to make your life better?
The control plane already has an api returning detailed information for services by name and for all services. It would be helpful to have an endpoint like:
/api/v1/services/discover/{name}/url
returning the public binding endpoint. i.e. http://localhost:56781 for service backend. This is helpful in an instance where you have a frontend SPA application like Blazor wasm, Vue etc., where we cannot use the Service Discovery capabilities of tye on the server. But where when using the --port option on ty run could assume that the discovery service address for the applications endpoints are at http:localhost:8001/api/v1/discover/backend/url for the backend service.
The only problem would be that this wouldn't currently work when you deploy. That would break the model right? What would your application do in production?
What should we add or change to make your life better?
The control plane already has an api returning detailed information for services by name and for all services. It would be helpful to have an endpoint like:
/api/v1/services/discover/{name}/url
returning the public binding endpoint. i.e.
http://localhost:56781
for servicebackend
. This is helpful in an instance where you have a frontend SPA application like Blazor wasm, Vue etc., where we cannot use the Service Discovery capabilities of tye on the server. But where when using the--port
option onty run
could assume that the discovery service address for the applications endpoints are athttp:localhost:8001/api/v1/discover/backend/url
for the backend service.i.e.
tye run --port 8001
@jkotalik