Keypoints about High Availability and Fault Tolerance (HAFT) solution

The architecture of HAFT is as follows:

The keypoints about HAFT solution is as follows:

Software AG recommends this set up, if the RTO is highly demanding, which ranges from few a seconds to 15 minutes.

Each data center or the cloud region hosts an independent or isolated cluster of its own.

In the active-active setup, you can have N number of data centers and all the data centers serve the client request. Whereas in the hot standby setup, you cannot have more than two data centers. Out of which only the primary data center serves the client request.

API assets are synchronized across the data center through CI-CD deployments.

Cross-DC federation support is limited to API consumers and auth tokens.

API transactions are local to the cluster where the traffic is served and not aggregated.

For aggregated transactions, use a centralized API Data Store.

For more details, see Fault Tolerance.