All Crosser modules can keep messages until successfully delivered. To enable this feature you need to set the ‘Max Number of Retries’ setting to a value larger than the default 0.

Maintain a stable, efficient, and secure production environment while enabling a dynamic and flexible space for development activities.

There is no automatic scaling but processing can be split over multiple nodes by for example selecting subsets of data using filter conditions or separate by data sources.

One of the great benefits with Crosser is the performance, tests show that we can process >100 000 messages per second on a pretty basic VM. A Raspberry Pi3 can process about 8000 messages per second.

In this article we describe what options you have and how to utilize provided interfaces for integration into your monitoring solution.

Split your use cases into smaller Flows and bind them together with the concept of Flow-to-Flow communication.

Explore how to maximize the efficiency of your data management with Node-to-Node communication.

There is no automated support for redundant nodes. However, the same flow can be installed on multiple nodes and started from the Cloud service on failure. You can also use container management tools, such as Kubernetes, to build high-availability setups with Crosser Nodes.

Crosser provides a library of FlowApps to show examples of how to solve common problems, but you can also create your own FlowApps, tailored to your organization.

Obtain complex operational KPIs, like OEE, by combining KPIs from these modules.