derekcollison
commented
2 months ago Since there is usage of reply subjects for both stream ingest and consumer ack for a message flowing through jetstream, you would need to use a header to signify the service reply subject and the responding ack would need to look for that header and use that if present when replying.
There also may be a different approach to this problem that does not involve jetstream.
Proposed change
We can use Request Reply from NATS core but it would be awesome to have the same for JetStream. The reason being is that we can use the number of requests for autoscaling and scaling to zero similar to Knative.
The same idea holds for the services API.
Use case
Microservices autoscaling including scaling to zero. Combined with cluster autoscaling this would allow for reduced cloud costs. Particularly useful for running heavy batch jobs that run once in a blue moon.
Contribution
No response