After a 6-month beta program, the Standard Clustering model with PostgreSQL 16.4 is generally available in Update 5.5-20240926, and all SecureTransport 5.5 guides on the Axway Documentation Portal are updated to reflect the new functionality.

The documentation for the legacy Standard Cluster with embedded MariaDB, which is available with SecureTransport 5.5 releases up to 5.5-20240829, is attached to this article:

• SecureTransport_5.5-20240829_AdministratorGuide.pdf

• SecureTransport_5.5-20240829_InstallationGuide.pdf

Benefits

The primary benefits of the new Standard Clustering model over the legacy solution are:

• Embedded PostgreSQL database on Server and Edge: PostgreSQL performs better or similarly serving the database query patterns required by SecureTransport for file transfers, processing, and Advanced Routing.

• Data replication across cluster nodes using PostgreSQL- native logical replication: The databases on all cluster nodes are in sync, and the data is equal across all nodes except the Server Log, which is local for each node. The replication rules between the databases of the cluster nodes can be managed as needed, allowing better flexibility.

• Automatic application failover: The internal load balancer in the cluster detects the server outage and fails over incoming requests to another server.

• Automatic database failover: All servers in the cluster connect to the database of one server, and if it becomes inaccessible, all other servers switch to the database of another server with an accessible database. Once the original primary database is back online, all nodes in the cluster will switch back to it.

Main differences

The following table outlines the most important differences between the legacy solution and the new Standard Clustering model. It is advisable to check your network rules and OS packages list. For a complete list of requirements for the new Standard Cluster, refer to the Installation and Administrator Guides.