Queue Providers
In ThingWorx, a Queue Provider enables connectivity to an external messaging system. This can be used for the following purposes:
• Externally Routing Data (off ramp) — This can be achieved by using IoT Stream, which allows you to extract data to an external system, for reasons such as archiving data and analytics.
ThingWorx 10.0 supports external routing for property values.
• Durable Queues — for improving scalability and reliability of ThingWorx internal messages — This can be achieved by enabling a system-provided durable queue (ThingworxQueueProvider).
ThingworxQueueProvider manges the queuing of events and data within the Platform. It ensures that events are processed in an orderly manner, handling tasks such as event subscriptions, data streams, and value streams.
Using the ThingworxQueueProvider system entity will reduce the buffer of internal in-memory queues used for events and persistence ThingWorx queues. This reduces memory pressure on the ThingWorx server and minimizes data loss in case of a server crash.
 |
You can configure one system-provided queue provider instance (ThingworxQueueProvider) to support both internal and external messages.
|
The initial implementation is based on the open-source Kafka client. The following configurations are tested:
• Opensource Kafka brokers
• Microsoft Azure Event Hubs
Since the implementation uses the Kafka protocol, other commercially available Kafka protocol-compliant brokers should work.
Related Topics