Scalable Approaches to Query an Ignition Instance

Hello All,

I am looking for the best practices / most scalable approaches to querying an Ignition instance. I was thinking of using an Ignition Edge instance and acting as an opcua client, is there a better approach that I should be using instead. The tags I am querying from the Ignition instance is around ~25,000.

For further context I want to collect data from an Ignition instance, and process it and send it to an external api via designer scripting.

As you know, scalability is relative…especially when considering realtime vs ad hoc data processing. Details aside:

For realtime data processing, read up on comparisons of OPC UA (Ignition native) vs MQTT SparkplugB (MQTT Transmission bolt-on). If any Ignition data is remote, I would encourage you to publish MQTT from the remote gateway. If all external servers are with low latency (local to Ignition gateway), OPC UA might be viable (and easiest to implement), albeit less scalable.

For ad hoc live data retrieval OR historical data processing, I would use Web Dev module and implement an API endpoint for external applications to retrieve the data they need via bridge to native Ignition functions.

3 Likes