Understand how to run the Crosser Node as an Azure Container Service (ACS)

You can trigger flows externally using HTTP or MQTT by sending messages to the Node’s internal HTTP server or MQTT broker.

For unstable connections, store data locally and upload or stream it later to services like Azure IoT Hub or Kafka.

Crosser Node supports encryption and authentication for its MQTT Broker and HTTP Server, configurable via local files or environment variables on both Windows and Docker.

The Parquet Writer module creates compressed files from arrays for storage in cloud services like AWS or Azure. It auto-detects schema and types but allows overrides for inconsistent data.

The Data Generator module can be used to generate some sample data to simulate input from external systems. This is helpful if you want to build a flow with a known message structure on the input side but without having access to that system right now.

Combine Interval and Delay modules to create one-off triggers at any time.

Learn how to get two timestamps from different messages into the same message, so that we can calculate the difference.

Use flow annotations to document and explain the Flow in the Flow Studio.

Secure your Crosser Node's HTTP and MQTT endpoints with TLS encryption and authentication.