The Nu Blog
The latest news, releases, features and commentary
Nussknacker 1.5
This version focused mainly on unifying our kafka source and sink components and some filter and choice (former switch) component improvements.
See the details
Decision scenarios with ML made easy
You can use Nussknacker to design and deploy ML models in use cases where complex decisioning, data transformation, and enrichment logic are needed. The decision logic you can build with Nusskkncker can be pretty sophisticated - we moved the bar of how much you can achieve with low code to pretty high.
Stretching old solutions to fit new problems doesn’t work. A genealogy of Nussknacker.
Extending SQL for the streaming world is very promising, but its main drawback is that in order to use it, you need to have all of your data in a homogenous environment. We took another approach that allows us to integrate any existing technology with stream processing.
NU has many flavours - which one is for you?
Chances are that you are already using a container’s scheduler - that is, Kubernetes. Wouldn’t it be great if we could just use it to deploy our business logic? You want to handle events from Kafka, enrich them with data from external systems, and possibly score some ML models? Let's glance at what is possible in Nu 1.3.
Running low-code scenarios with GraalVM native image
We’ve been working on making Nussknacker more cloud-ready, and it turned out we need to make the runtime container as small as possible.
It looks like GraalVM can be the answer: the resulting image and memory usage are really small, which makes running each Nussknacker scenario
in a separate container viable.
Nussknacker compared with similar open-source tools
People quite often ask us, what are the differences between Nussknacker and other similar (at first glance) tools. There are usually some overlapping areas in which many of them can be used interchangeably. But when your system grows, tools used for other purposes than they were designed for can cost you a lot of pain and can introduce a lot of technical debt.
Apache Ignite in Nussknacker environment. Lessons learned
A data cache allowing fast access by key is a must-have when dealing with a stream of thousands of records per second
Event streams always need Flink, or ...not really?
We believe there are many use cases where Nussknacker can bring significant value without operational overhead caused by Flink or other sophisticated stream processing engine
Nussknacker 1.1.
We have released version 1.1 of Nussknacker 🍾
See how lowcode can help with business decisions on streaming data 💪
Nussknacker
Business users can create or change decisioninig algorithmss anytime, without any assistance from IT department.
Contact us
We can help you customise and extend Nussknacker to meet your specific needs and then deploy and maintain it on your infrastructure.