Architecture of the Quick Processor

The following diagram illustrates the data flow of a data set. The Quick Processor is executed after the decoding process for each individual data set. 

A Quick Processor can be used for data transformation, but can also act as a filter with complex logic or as a state store to create aggregates. Therefore, the result of a Quick Processor execution is not always a data set.

The attribute filters are executed in the last step following the Quick Processor.

 

The position of the Quick Processor within the data flow when retrieving data.

• Related Articles

• Quick Processor Rights Management

  To modify or create a Quick Processor, the user must have both the QuickProcessorModify right and the TopicAccessRead right. QuickProcessorModify can be assigned for individual connections/environments. In combination with the TopicAccessRead right, ...

• Introduction to the Quick Processor

  The Quick Processor allows you to create filters and modify records using JavaScript. In this article, we show how to create a Quick Processor and how to access, filter, and modify records. A Quick Processor is always linked to a view. This means ...

• Requirements

  Hardware requirements The requirements can vary to a large extent depending on the number of users, connections in Kadeck and usage (e.g., how many users use it in parallel). Minimum Single Core CPU 4GB Memory 2 GB disk space Recommended 2+ Core CPU ...

• Getting Started

  The Kadeck Team says: Thank you! Kadeck is the result of experienced developers, operations, architects and project managers from the IT field, who were looking for an easier and better way to implement, communicate and operate data streaming ...

• Horizontal Scaling

  Architecture of a single node To scale horizontally just add servers behind a load balancer (with sticky sessions active). Don't forget to update the cluster configuration Startup Parameters when starting Kadeck on each server.