Mainframe versus Linux Cluster
Some customers may be familiar with the Software AG product Adabas Cluster Services operating on z/OS.
Both, Adabas Cluster Services (z/OS) and Adabas Cluster for Linux provide cluster functionality for Adabas specific to their platforms.
How do these products differ?
Adabas Cluster Services (for z/OS)
Adabas Cluster Services, a z/OS mainframe-based product, is a selectable unit of Adabas that helps you make full use of IBM's parallel sysplex environment by allowing a single physical database to be accessed simultaneously by up to 32 nuclei installed across multiple operating system images. Thus, all nuclei in a "cluster" process any updates concurrently.
In addition to the increased throughput that results from parallel processing, Adabas Cluster Services increases database availability during planned or unplanned outages. The database can remain available when a particular operating system image or cluster nucleus requires maintenance or goes down unexpectedly.
Adabas Cluster (for Linux)
Adabas Cluster for Linux has a completely different implementation and is a cluster solution for Linux focussing on a shared-nothing architecture eliminating all possible single points of failure.
Adabas Cluster for Linux is based on a primary-secondary cluster architecture. Only the primary node will handle requests. Client calls to secondary nodes are transparently re-routed to the primary node. The cluster handles data replication to the secondary nodes implicitly. Adabas Cluster for Linux focuses on High Availability.
The cluster framework supports synchronous replication (changes on one node are guaranteed to be applied on the other nodes). The cluster allows for point-to-point connections between a client application and the Adabas Server using ADATCP(S).
Note:
Data-in-flight between client and primary node can be secured using ADATCP(S). The prerequisite for ADATCP(S) is, along with a licence for Entire Net-Work (WCP) for ADATCP, a valid license for Adabas Encryption for Linux (AEL).