Mark Whitfield invested many years in the HPE NonStop field from 1990. The HPE NonStop architecture (originally Tandem Computers) is a legendary fault-tolerant system known for 100% continuous availability. The platform’s hardware and software execution evolved across six distinct eras and processor transitions:
Architecture: The foundational “shared-nothing” parallel architecture. Featured redundant components (processors, disks, power supplies) connected by a proprietary dual-bus (Dynabus). The operating system provided instant automated failover.
Architecture: Expanded into 32-bit computing. To keep pace with industry performance, Tandem transitioned from proprietary processors to off-the-shelf MIPS RISC processors while heavily emulating the original instruction set for compatibility.
3. The Himalaya/ServerNet Era (1997–2004)
Years: 1997–2004
Processors: MIPS R-series
Architecture: Replaced the legacy Dynabus with ServerNet, a high-speed system interconnect that served as an early precursor to modern networking fabrics. (Compaq acquired Tandem in 1997, which subsequently merged with HP in 2002).
4. The Integrity Itanium Era (2005–2013)
Years: 2005–2013
Processors: Intel Itanium (TNS/E)
Architecture: Branded as HP Integrity NonStop (NonStop i). The platform moved off proprietary silicon to standard Intel Itanium processors. This was driven by the “NonStop Advanced Architecture” (NSAA), lowering hardware costs while maintaining Availability Level 4 (AL4) standards.
5. The NonStop X (x86-64) Era (2014–Present)
Years: 2014–2026
Processors: Intel Xeon x86-64 (TNS/X)
Architecture: Fully decoupled the OS from proprietary hardware by shifting to standard Intel x86-64 processors and InfiniBand fabric. The latest compute nodes (such as the NS5 X5 and NS9 X5) utilize modern Intel Xeon Scalable processors to maintain maximum Availability Level 4 (AL4) workloads.
6. The Virtualized NonStop Era (Present)
Years: 2015–Present
Processors: Virtual Machines / Cloud / x86
Architecture: HPE extended the platform to support Virtualized NonStop Software, allowing fault-tolerant enterprise workloads to run entirely in private clouds via standard VMware or hybrid architectures, independent of specific physical servers.
The BASE24 electronic payment system developed by ACI Worldwide exists in two primary architectural generations:
BASE24 Classic (historically deployed on HPE NonStop / Tandem fault-tolerant hardware) and
BASE24-eps (Enterprise Payments System, built using an object-oriented C++ framework deployable across open systems, z/OS, and cloud infrastructure).
Despite structural differences, both share a highly optimized, component-based transaction routing engine.
BASE24 architecture overview
Core Structural Component Layers
The component architecture maps the complete end-to-end lifecycle of a financial message (such as ISO 8583) through five distinct functional sub-systems:
1. Network & Message Routing Component (XPNET)
Purpose: Coordinates all message traffic across internal processes and physical network nodes.
Function: Operates as a specialized middleware network manager that decouples low-level communication links from upper transaction routing layers.
Configuration: Relies on a Logical Network Configuration File (LCONF) to define active execution nodes, hardware lines, and physical stations.
2. Perimeter Access Layer (Device Handlers)
Purpose: Translates device-specific message protocol formats into the system’s unified internal format.
ATM Device Handlers (ATMDH): Manage direct connectivity to automated teller machines, unpack specific vendor dialects (such as Diebold or NCR states), and track terminal hardware statuses.
POS Device Handlers (POSDH): Interface with point-of-sale acquirer terminals and merchants.
Security Operations: Triggers immediate payload encryption/decryption and Hardware Security Module (HSM) PIN-block translation directly within this ingestion ring.
3. Core Transaction Logic (Authorization System)
Purpose: Determines whether a payment request should be accepted, rejected, or modified.
Full On-Us Authorization: Inspects internal databases for matching account records, positive balances, and velocity thresholds to issue real-time decisions.
Parametric/Negative Checks: Validates card status against offline negative files, usage restrictions, or custom risk parameters.
Scripting Engine: Modern BASE24-eps variants execute localized transaction routing scripts via customized operators without forcing a compile rewrite of the core engine core.
Interchange Interfaces (ICH): Package and transform the transaction payload into international network profiles (e.g., Visa, Mastercard, regional switches). It handles strict message mapping and regional network check requirements.
Host Interfaces (HIF): Create synchronous links back to an institution’s underlying Core Banking system to apply ledger adjustments, check balances, or execute real-time holds.
5. Offline & Administrative Subsystems
Extract Component: Gathers active transaction logs and streams filtered payloads out to analytical reporting databases.
Refresh Component: Updates terminal operational data, key packages, and card exclusion lists from parent systems down to active execution nodes.
Settlement Initiator: Groups, cleanses, and batches net-clearing totals to finalize payment entries into regional clearinghouses.
Architectural Divergence: Classic vs. EPS
The structural design varies significantly depending on the generation of the software deployment:
BASE24 and BASE24-eps architecture overview
End-to-End Component Transaction Flow
An ATM transaction arrives at the network interface layer managed by XPNET.
The message is routed to the Device Handler, which strips hardware packaging and requests translation from the HSM.
The clean internal message passes to the Authorization Engine.
If it is a “Not-On-Us” card, the engine identifies the destination BIN and transfers routing control to the Interchange Interface.
The Interchange Interface maps the payload to the external scheme standard (such as Visa) and transmits it to the external network.
The outbound network response is unwrapped by the Interchange component and tracked through the core engine to log final response codes.
The transaction safely records inside the active log file, allowing the Extract / Settlement components to pick it up later during batch processing.
The official HPE Nonstop Technology Architecture is a specialized, 100% fault-tolerant infrastructure built with a tightly integrated hardware and software stack designed to eliminate any single point of failure. Formal instruction and architectural frameworks have been modernized under the newly relaunched HPE Nonstop Compute Training Portfolio curriculum.
Originally developed by Tandem Computers in 1976, the platform eventually became part of Hewlett Packard Enterprise (HPE). Unlike standard servers that can crash due to a single component failure, NonStop uses a tightly integrated, “shared-nothing” architecture to ensure that if a hardware or software component fails, another instantly takes over with zero downtime or data loss.
Core Architectural Features
To understand how HPE NonStop works, you need to understand its unique design principles:
Shared-Nothing Architecture: Every processor has its own dedicated memory, I/O channels, and copy of the operating system. No single component is shared, eliminating any single point of failure.
Process Pairs: Applications run using a primary process and a backup process on a different processor. The primary process constantly copies its state to the backup. If the primary fails, the backup immediately takes over.
Massive Scalability: Systems can scale up seamlessly from small distributed environments to massive clusters containing up to 24,000 processor cores without interrupting running operations.
Hardware Platform: The modern software environment runs on industry-standard x86 architectures, available as physical server racks (like the HPE NonStop NS9 X5) or as virtualized instances in hybrid cloud environments.
Dual Operating Environments
HPE NonStop runs a specialized operating system called NonStop OS. Inside this OS, developers and administrators interact with two distinct environments:
Guardian Environment: The native, proprietary environment optimized for high-volume Online Transaction Processing (OLTP). It handles tasks sequentially through process-oriented manually-started jobs rather than traditional automated queues.
Open System Services (OSS): A UNIX-like, POSIX-compliant environment built on top of the NonStop kernel. This allows organizations to run standard open-source applications, tools, and scripts natively alongside Guardian.
Ecosystem and Use Cases
HPE NonStop is rarely used for standard office automation or basic web hosting. Instead, it serves as the backbone for global industries where an hour of downtime could cost millions of dollars:
Financial Transactions: Powers global stock exchanges, automated teller machines (ATMs), and retail point-of-sale credit card processing, eg. BASE24.
Travel and Logistics: Runs critical airline reservation systems and real-time cargo routing infrastructure.
Database Management: Features its own highly secure, distributed database engine called NonStop SQL, which guarantees absolute data integrity across all transactions.
Modern Development: Supports traditional languages like COBOL85 and ANSI C, alongside modern DevOps integrations like Git, Ansible, and Eclipse-based IDE environments.
An architectural blueprint of an HPE NonStop environment typically separates the layout into three core interdependent layers:
Hardware & Fabric Layer: Consists of independent, loosely-coupled Processor Nodes (handling up to 24,000 cores globally) connected via an ultra-fast InfiniBand or ServerNet system fabric backbone.
I/O & Subsystem Layer: Utilizes Cluster I/O Protocols (CLIMs), splitting tasks between Storage CLIMs (SCLIMs) and Network CLIMs (NCLIMs) to isolate external communication from main processing.
Operating System & DB Layer: Runs the NonStop OS, which simultaneously manages the traditional Guardian environment, Open System Services (OSS) for UNIX/Linux paradigms, and the NonStop SQL distributed database engine.
Recommended Architecture Training Curriculum
HPE organizes its technical blueprints into structured educational paths for engineers.
1. Foundational Blueprint Concepts
Course Code: U4147S (HPE Nonstop Compute System Fundamentals).
Focus: Delivers a top-down view of system goals, transaction processing, and fundamental architecture.
Key Modules: Explores Guardian vs OSS, Pathway application management, and basic database interaction.
2. System Operations & Administration
Course Code: H1SC3S (HPE Nonstop Compute System Administration I).
Focus: Maps physical and virtual components to real-world deployment.
PROject Templates 