Can domain experts be so happy with a tool that the experience can be likened to nirvana? This provocative question is intended to start a discussion about the features needed to make real-time data products accessible to ordinary (non-technical) people. Zbigniew Małachowski presents his own list of required features. But are they enough to trigger nirvana-like relief?
Webinar video: Real-time data processing for the people
Abstract:
Acting on data in real time, such as fraud detection, next best action, streaming ML, clickstream analysis, IoT sensor analysis, etc., requires algorithms that are rarely trivial enough to be created with no code: just drag and drop.
In the streaming world, the reason why domain experts find themselves forced to go into deep technical details of Kafka, Flink, Spark, REST, etc is that while many platforms are quite successful in abstracting Kafka, Flink, Spark, etc, they are just simple visual overlays on the (streaming) SQL and do not allow for much more.
There needs to be more to author a serious actions-on-data algorithm.
What features are needed for these tools to truly succeed?
Decision models in Nussknacker: typed AI decisions for Kafka and API workflows
What if every event came with an AI answer to your own question, picked from options you define, plus how sure the model is? Nussknacker can call such models and act on the answer.
What is new in Nu - September 2026
Change Data Capture for tables, nodes with named outputs, a WebSocket Server source and live data for Request-Response.
What is new in Nu - August 2026
Deployment targets, the World Map component, improved enum support, improved compare versions and more.
Feel free to ask any questions
Nussknacker can make your data processing use case more agile and easier to manage.
