This type of architecture is ideal in smaller organizations since you don't have to worry about maintaining a server. Additionally, there is no on-site IT staff required to monitor the system.
If Ignition is hosted in the cloud, then it is very common to have your database also hosted in the cloud. However, many of our customers find that also having a controls database on-site to store temporary or in-progress data useful. This is great when you want to have data stored locally.
Cloud based servers are increasingly common, but it is important to educate your organization on the risks associated with them. If your organization is interested in a cloud based solution, we recommend following the guidelines in the Ignition Security Hardening Guide, as it addresses many potential security issues for both cloud and non-cloud based servers. Additionally, if offers recommendations on how to better protect your system.
If you are using redundancy or are concerned about uptime, you should be using Ignition redundancy regardless of whether your Ignition is in the cloud. While most cloud providers offer built-in redundancy, this is often much slower than Ignition's redundancy failover time. Typically Cloud Server redundancy has a new computer instance spun up (started) in the event the original fails. This will often take a couple minutes where Ignition's redundancy (with default settings) takes around 20 seconds to switch over. There are other options to make a Cloud Server start faster, but currently they all slow down the CPU substantially to make it possible.
If you are using Ignition's Redundancy with a Cloud Server, then typically we recommend that both of the servers are run side-by-side. This means either both in the cloud or both on site. One warning: If you have both instances of Ignition in the cloud but if your connection to the internet goes down, then you lose access to both instances of Ignition.
Many customers find the following cloud based service suggestions helpful: