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
Enable Dapr sidecars for non-HTTP-bound services #1097
What should we add or change to make your life better?
Optionally (?) start Dapr sidecars for services that have no bound HTTP port. Currently only services with an HTTP endpoint will have Dapr sidecars started.
Why is this important to you?
While it's true that applications expecting incoming requests (method invocations or pub-sub messages) must have a HTTP (or GRPC) endpoint to be reachable to the Dapr sidecar, it's not required for applications that only send requests to services via a Dapr sidecar (e.g. a worker that wakes periodically to start workflows by sending Dapr requests to other services).
There are existing Dapr samples that use this pattern, which today cannot be used with Tye as the "worker" gets no Dapr sidecar to use.
What should we add or change to make your life better?
Optionally (?) start Dapr sidecars for services that have no bound HTTP port. Currently only services with an HTTP endpoint will have Dapr sidecars started.
Why is this important to you?
While it's true that applications expecting incoming requests (method invocations or pub-sub messages) must have a HTTP (or GRPC) endpoint to be reachable to the Dapr sidecar, it's not required for applications that only send requests to services via a Dapr sidecar (e.g. a worker that wakes periodically to start workflows by sending Dapr requests to other services).
There are existing Dapr samples that use this pattern, which today cannot be used with Tye as the "worker" gets no Dapr sidecar to use.