Exactly-once event processing
Nussknacker delivers messages exactly once end to end through the Kafka sink, using Flink. Side effects such as enrichments may still repeat after a failure.
With the new release Nussknacker allows End-to-End Exactly-Once event processing.
We guarantee that the message is delivered once and only once via kafka sink in the scenario. If a fault occurs between checkpoints and after an operation that performs some side effects, such as enrichment, it possible that this action could be repeated.
This feature is provided by Flink. To read more about it see: Flink blog post and Flink fault tolerance.
Go to the docs page to learn more: link
Other highlights
- Nussknacker Quickstart has been updated and is now based on an installation example. Using Nussknacker Quickstart is now even clearer and easier. To see the instruction go here
- Impersonate mechanism added. When an external system is calling the Nussknacker API with a technical user, the impersonated user can be passed and the performed action will be carried on behalf of the impersonated user.
The visual Flink interface for real-time decision logic.
Enrich, decide, and act on every event.
Related posts
Nussknacker 1.15 release highlights
Nussknacker 1.15 adds a batch processing mode built on Flink's Table API and Catalogs, support for Flink 1.18, node search in the editor and a new theme.
Next-Generation Real-Time Rating Systems
Synchronous architectures struggle when rating must keep up with live usage. This post shows how stateful stream processing in Nussknacker handles it.
Turn your Flink UDFs and PTFs into low-code components
Nussknacker discovers the UDFs and PTFs you already wrote for Apache Flink and offers them as typed components, so scenarios call them without SQL or glue code.