Hello, was wondering best practices for web dev module regarding a redundant backup server. Best way to handle if the master server is down. Currenltly, we do not handle it at all. First thought was the system calling the APIs we built would first try the master, if unresponsive, try the backup and they would have to do these everywhere they call our APIs. Was wondering if there is a better more global way to handle things. Some of our software devs and IT personnel have been discussing a load balancer but not sure if that is the right thing for what we are trying to achieve.
A load balancer/reverse proxy is the generally accepted solution to this, but be aware they have no concept of Ignition's specific redundancy concept. You'll have to use a product smart enough to distinguish between HTTP availability (whether the given redundant node is up at all) and Ignition's specific redundancy role (i.e. don't try to fail requests over to a backup that is not active). You can do this by checking the /system/gwinfo route.