Page History

...

• Network paths
  •  It may make sense to have edge nodes support multiple network paths to the MQTT servers.  For example, Ethernet, cellular, and satellite could all exist as supported network paths on a single Edge gateway.  This will help ensure additional reliability by supporting failover of networks.
• Primary Ignition and Primary Ignition backup placement
  • This tutorial was created by modeling this exact environment using Amazon AWS EC2 instances in the cloud.  Reliability could be improved by putting Ignition Primary and Ignition Primary Backup in different AWS availability zones or even different AWS regions.  This would allow the primary Ignition with MQTT Distributor and MQTT Engine to continue to operate even in the case of AWS failures.  In the case of on premises installations of Ignition these could be placed in different physical locations and/or on secondary networks.
• MQTT Servers
  • Additional MQTT Servers can be added so MQTT connections from remote edge nodes remain established.  Additional Chariot MQTT Servers can be used to make the system more robust (http://www.cirrus-link.com/mqtt-servers/).
• History enablement in MQTT Transmission
  • MQTT Transmission supports caching of data in the case that it can not establish a connection to any of the configured MQTT Servers.  Once a connection is reestablished, it will begin reporting and flush the stored historical values to prevent data loss in catastrophic failures.

...

(Note: For this test infrastructure, MQTT Distributor will be installed as an Ignition module on both the Primary Ignition Gateway as well as the Primary Ignition Gateway Backup.  Make sure to either turn off firewalls or at a minimum allow inbound connections to TCP/IP port #1883 and port #88831883, as remote MQTT Clients will need to be able to establish a TCP/IP socket connection to these ports).

...