NATS JetStream support

[falkolab]

What about NATS JetStream support and nats-queue-worker rework to support new streaming functionality of NATS

My actions before raising this issue

I'v read the blog article and didn't found any related to faasd info

I don't want to start with possible abandoned project

Who is this for?

What company is this for? Are you listed in the ADOPTERS.md file?

No

Expected Behaviour

At least some info provided in README, at most some roadmap provided

Current Behaviour

docker-compose.yaml contains abandoned nats-streaming and queue-worker services

[nitishkumar71]

faasd is not an abandoned project. it's use is limited to use cases where you don't want a lot of processing power. Support for async in faasd is equal to what is being offered in OpenFaas Community Edition.

There is no difference in user experience if you go with faasd or OpenFaas. Depending on your use case possibly, you can do prototyping on faasd and then switch to OpenFaas. I would recommend to explain your use case in community call.

[alexellis]

What @nitishkumar71 said is correct - nothing's been "abandoned" on our side, however the team behind NATS Streaming won't receive critical security patches going forward. If you purchase the eBook you'll see how to use NATS Core in your applications instead. NATS Core is based upon pub/sub, rather than queuing.

faasd / Community Edition are best suited for testing, development, personal use and building a prototype to see if further investment makes sense for a team. We plan to continue to update / maintain the various CE projects as normal, but you use NATS Streaming in production at your own risk.

If you would like JetStream support, it's been available for faasd and Kubernetes in OpenFaaS Standard for over a year, and all our customers have switched over to it.

See also: JetStream OpenFaaS