by Rafał Golcz & Piotr Jagielski @pjagielski It’s a streaming world Do the terms “stream processing” or “event-stream” sound familiar to you? We guess so, it’s 2022 and we’ve already got used to these concepts. But it wasn’t always the case. …

by Jakub Dutkowski & Maciek Próchniak @mpproch As mentioned in our previous post, while working on Nussknacker we’ve come to understand that a lot of real-life use cases do not require complex stateful data stream computations. Fortunately, Nussknacker was designed to be able to run multiple execution engines. …

Why native image? For some time we’ve been working on making Nussknacker more cloud-ready. This means a few things, one of them is being able to run scenarios as containerized microservices. by Maciek Próchniak @mpproch The idea is to have a docker container that, given JSON with the scenario and basic configuration (e.g…

People quite often ask us, what are the differences between Nussknacker and other similar (at first glance) tools. A good tool can be used in many different ways. There are usually some overlapping areas in which many of them can be used interchangeably. …

In this article, we’ll show you what’s the case for using Apache Ignite in a Nussknacker environment, which open-source components you can use in that case, and what to pay attention to in Ignite cluster configuration and monitoring. This is based on experience from one of our latest Nussknacker deployments. …

We believe there are many use cases where Nussknacker can bring significant value without operational overhead caused by Flink or other sophisticated stream processing engines by Maciek Próchniak @mpproch Stream processing — what can it mean? The term is quite broad. There are complex, powerful stream processing engines, some of…