The upcoming Choria Server release will support publishing fleet data to JetStream a new Streaming Server from the folks who built NATS - the core technology of the Choria Broker.
This technology is currently in tech preview and so we’ve added early support for it so Choria users can test it for their needs.
Support for JetStream will be in the nightly build tonight and a release will be soon.
Read on for some background on the why and how.
Choria Adapters allow you to receive data from Choria nodes and - after security validation - republish it into other technologies like Streaming Servers. You would traditionally use this for fleet metadata but should you embed Choria into your IoT devices or use something like our Backplane you can emit any data you want onto the Choria network which would then be adapted to other systems.
Today we support NATS Streaming and JetStream but hopefully one day we’ll support things like Kafka, Kinesis and many other types of stream. I’d also like to support webhook based systems etc.
At present we support receiving node metadata from a fleet of nodes and placing it into a NATS Streaming Server. I’ve used this to great effect to move vast amounts of metadata around the world with the help of the Choria Stream Replicator.
Using these two tools I’ve built a system that will maintain a real time view of 100s of thousands of fleet nodes with 5 minute resolution including node down detection in a highly distributed and stable manner.
NATS Streaming is a separate product from the core NATS server and has it’s own client libraries and turns the model on the head a bit which have always made it a bit weird to explain to others.
The NATS team have for a long time now been working on a next generation server called JetStream which integrates with core NATS - and core client libraries - and have many new features that would make it suitable for work queues in addition to the more traditional use while being secure, multi tenant and soon clustered.
Yesterday it was announce that JetStream has entered Tech Preview Status so to assist with testing it I added an adapter that will let Choria place data in it using the same model as with NATS Streaming today.
We’ll test this and as things stabalize add support for it to our Stream Replicator and also streaming based Prometheus federation system.
With this being a core technology in NATS server it’s conceivable that we will add the ability to access it in the Choria Brokers to create a more tightly contained Choria system that expose these capabilities. I’m especially interested in the job queue behavior for some future plans I have for Choria.