Born in the Cloud, Built to Scale Loyalty to Infinity

ReactorCX is designed to run continuously without downtime, scheduled or unscheduled. The cloud-native architecture allows platform and program updates to roll out without interruptions over many years. Three architectural choices support this:

• Microservice architecture that scales with traffic and stays resilient through individual instance failures
• Fast NoSQL database with real-time replication and fault tolerance
• Distributed message brokers powered by Apache Kafka

ReactorCX has maintained zero downtime in production since October 2018 - across platform updates, program changes, and client migrations including some of the world's largest enterprise loyalty programs.

The ReactorCX microservice architecture scales up and down with traffic volume, stays resilient in the face of individual instance failures, and replaces failed instances transparently - without any interruption to the program or its members.

This architecture is one of the three foundations that support ReactorCX's continuous delivery with zero downtime, alongside the fast NoSQL database and the Apache Kafka event backbone.

ReactorCX uses a fast NoSQL database that delivers real-time transaction processing, real-time replication, and fault tolerance. The NoSQL choice supports the platform's horizontal scaling profile and the volume of activity processed in production.

In the largest single retail enterprise deployment: approximately 2.6 billion transactions per year and 25 million+ real-time API requests per day, all within the platform-wide <200ms API response SLA.

Apache Kafka is the distributed message broker powering the ReactorCX event backbone, handling hundreds of millions of events daily. Kafka handles the event publication layer that lets events flow from the ReactorCX processing model to downstream event handlers.

The Kafka layer supports both Replication Events (Level 1, CUD) for state synchronization and Business Events (Level 2) for action-specific triggers - giving downstream systems the right type of event for the right purpose.

ReactorCX supports Program Import/Export that enables fast changes with confidence - allowing promotions to be tested in lower environments and deployed to production without manual steps.

Program teams move quickly from idea to production without the manual hand-offs that traditionally slow enterprise loyalty programs and introduce risk. This is part of the broader change-velocity story that supports hundreds of active promotions per month at scale.

Folders and Rulesets enable efficient management of program complexity. They let program teams create mini-programs within a larger program and set up attribute-based access control for folders or even individual rules.

A single ReactorCX deployment can house multiple program domains with appropriate governance separation between teams, brands, or regions - without each domain requiring its own platform instance.

ReactorCX is built to safely and competently deliver program changes at any time. In the largest single retail enterprise deployment, 400+ active unique promotions run per month.

This velocity is supported by Program Import/Export between environments, Folders and Rulesets for organization and governance, and the underlying continuous-delivery architecture that lets teams ship changes without risk or downtime.

ReactorCX operates at enterprise scale in production:

• 2.6 billion transactions per year
• 25 million+ real-time API requests per day in the largest single retail enterprise deployment
• Peak event throughput of 56,000+ events per minute in a single hospitality program
• Hundreds of millions of events daily through the Apache Kafka event backbone

The platform-wide <200ms API response SLA holds across all of this volume. Loyalty Methods has integrated ReactorCX across 30,000+ locations.

ReactorCX supports two privacy modes: storing PII inside the platform with full data subject rights support (access, deletion, rectification, restriction of processing, portability), or operating with tokenized identifiers where PII is stored externally in a client-controlled system.

The scaling architecture operates consistently in either mode. MGM Resorts operates ReactorCX with membership numbers only - no PII stored in the loyalty platform.

ReactorCX is SOC 2 Type II certified with annual audit. Security controls include:

• Encryption in transit (TLS) and at rest (AES-256)
• Role-based and attribute-based access controls
• SSO integration via OIDC
• Audit logs across access, system activity, configuration changes, and member and transaction activity

Attribute-based access control extends to Folders and Rulesets at the program organization level, enabling per-team and per-role governance of program complexity - so the right people have access to the right parts of the program, at any scale.