nioev-mqtt VS spec

The fourth version also has a gesture sensor at the top for controlling it. The gesture sensor is connected to the Zero which sends all detected gestures over mqtt to my animation script. I added a small video where I show all the scenes I created. The timer is my tea timer btw :). The frames are all rendered on my Ordroid XU4Q, which runs nioev-mqtt, which is my custom MQTT broker which has built-in JS scripting support. It also supports native libraries which you can dynamically load. This is how I created the cairo bindings to render the frames (and convert them to PNGs). To save power and reduce load, the frames in the video are only actually send at about 50FPS, but I managed way more in the past. At this point the Pi is the bottle neck, I should probably switch out the Python script on there for a bit of C++ at some point.

AsyncAPI: Interested in how to define your WebSocket APIs? One of the most advanced realtime specifications is the AsyncAPI specification, which comes with various generators for code and documentation, as well as renderers for the specifications.

Our journey with FastStream started when we needed to integrate our machine learning models into a customer's Apache Kafka environment. To streamline this process, we created FastKafka using AIOKafka, AsyncAPI, and asyncio. It was our first step in making message queue management easier.

Automatic Docs: Stay ahead with automatic AsyncAPI documentation

FastStream supports in-memory testing, AsyncAPI schema generation and more... If you are interested, please support our project by giving a GH start and joining our discord server.

However, in order for the system to work effectively, there must be a common understanding between the components regarding events and their data structures. This is where AsyncAPI comes in; it helps define a contract that describes how the components communicate and behave effectively.

You can also take a look at https://www.asyncapi.com/ (a spec for asynchronous APIs). It's useful for this use case, that is, building a well structured websocket interface with pub/sub.

Sure! Next step I am working on AsyncAPI scheme generation by your application code. It's also includes a project generation from scheme, scheme web view (lika the Swagger for OpanAPI), etc. It will a much difficult than just another broker implementation...

Onboarding - Enable developers to quickly learn how to consume the exposed APIs. For example, offer OpenAPI or AsyncAPI documentation and provide a portal and sandbox.