Commercial Redis CDC for Ruby

CDC Pro for Redis

A paid Ruby CDC bundle for Redis-heavy systems: fast Redis source drivers from cdc-redis-pro, paired with cdc-orchestrator-pro for concurrent downstream processing, worker-local resource pools, and benchmark-backed runtime tuning.

The source code and package registry remain private. This public site exists for discovery, product evaluation, and customer onboarding.

Features

Redis source drivers built for real topologies

Use Redis as a high-speed CDC ingress path with honest durability tradeoffs, clear topology support, and downstream orchestration that is built for production use.

Redis Streams

Durable, ordered CDC for Redis Streams with fast parallel downstream processing built for production workloads.

Redis Pub/Sub

Ultra-low-latency CDC delivery for real-time fan-out, lightweight event propagation, and responsive systems.

Redis Cluster sharded Pub/Sub

Horizontal CDC distribution across Redis Cluster shards for higher throughput, broader fan-out, and scalable consumption.

Redis keyspace notifications

Reactive CDC from Redis key events for cache invalidation, live state tracking, and event-driven automation.

Cluster and Sentinel

Sentinel primary discovery, Redis Cluster routing, same-slot Streams, sharded Pub/Sub, and multi-primary keyspace subscription support.

TLS and ACLs

Certified local topologies cover TLS, ACL authentication, standalone Redis, Sentinel, and Cluster configurations.

CLI-first operations

Run sources, check health, print Prometheus metrics, process JSONL events, or pipe Redis source events directly into the orchestrator runtime.

Sample pipeline app

A standalone Ruby example shows worker-local Redis client pooling upstream, Redis source mode configs, downstream process_many, license env vars, and local API docs generation.

View example ↗

Streams, Pub/Sub, Sharded Pub/Sub, and Keyspace recordings are published on asciinema.org.

Sample Rails dashboard

A Rails front end for the same licensed bundle, with per-mode run buttons, run history, and a local docs page customers can open after installing the gems.

View example

Example applications

Public demos for discovery and onboarding

The landing page should put the two working samples in front of people who want to inspect the bundle, not hide them behind the benchmarks.

Sample Rails dashboard preview
Rails dashboard sample with mode pages, bounded demo runs, and local docs.

Downstream runtime

Fast upstream source, stronger downstream primitives

The bundle showcases Redis as a fast upstream source coupled to cdc-orchestrator-pro for downstream processing: outer Ractor workers, inner fiber concurrency, partitioning, failure policy, and worker-local resource ownership.

Nested runtime: cdc-parallel outside, cdc-concurrent inside.
LocalResourcePool: each worker owns its own live Redis/database clients.
Batch-aware CLI: JSONL batches and direct Redis source piping.
Metrics: runtime throughput, failures, and Prometheus text output.

Operational commands

cdc-redis-pro run --config redis.yml --metrics prometheus
cdc-redis-pro health --config redis.yml
cdc-redis-pro metrics --config redis.yml
cdc-redis-pro orchestrate --batch-size 25 --redis-url redis://...
cdc-redis-pro pipe --config redis.yml --ractors 3 --fibers 50

Performance evidence

Public benchmark, soak, and chaos reports

The published reports expose CSV-backed benchmark artifacts and a generated analytics dashboard for Redis source and downstream orchestration workloads.

Peak runtime 62.3k events/s
Benchmarked events 11.43M
Benchmark failures 0
Chaos recovery 31/31
Latency and throughput benchmark chart

What to inspect

  • Throughput and latency across synthetic, Streams, Pub/Sub, CPU+Redis, and pgoutput+Redis workloads.
  • Resource behavior: CPU, RSS, allocations, Redis operations, and worker mailbox depth.
  • Five-minute, one-hour, and overnight soak stability plus recovery behavior under Redis and source outages.

Commercial license

How to get access

CDC Pro for Redis is sold manually for the founding release. A paid license includes private GitHub Packages access, signed offline license tokens, local API documentation, and support for integration questions.

*Response typically within 24 hours.

What to send

GitHub username Used for private package access.
Use case Redis topology, expected event volume, and downstream sink.
License term Founding license duration and renewal date are agreed manually.
Support channel Email, GitHub issue access, or another agreed customer channel.

Customer setup

Private package install and offline token verification

Customers install from GitHub Packages with a token that can read private packages. Runtime license checks are offline: the app receives a signed token and a public verification key.

The private signing key never ships with customer applications. Customers receive only the signed token and public key.

Bundle shape

bundle config https://rubygems.pkg.github.com/kanutocd USERNAME:TOKEN

source "https://rubygems.pkg.github.com/kanutocd" do
  gem "cdc-redis-pro", "0.9.0"
  gem "cdc-orchestrator-pro", "0.9.0"
end

export CDC_REDIS_PRO_LICENSE_KEY="cdc-license-v1..."
export CDC_REDIS_PRO_LICENSE_PUBLIC_KEY="-----BEGIN PUBLIC KEY-----..."
export CDC_ORCHESTRATOR_PRO_LICENSE_KEY="$CDC_REDIS_PRO_LICENSE_KEY"
export CDC_ORCHESTRATOR_PRO_LICENSE_PUBLIC_KEY="$CDC_REDIS_PRO_LICENSE_PUBLIC_KEY"

Customer resources

What a license includes

The product value is private package access, commercial usage rights, updates, and direct support. License checks are a local entitlement guard, not a substitute for the commercial agreement.

Private gems

Access to cdc-redis-pro and cdc-orchestrator-pro through GitHub Packages.

Offline license

A signed token that can be verified locally without outbound license-server access.

Versioned docs

Local YARD API docs generated from the exact installed gem versions, plus this public discovery site.

Benchmark reports

Public CSV and dashboard evidence for throughput, latency, soak stability, and recovery behavior.

Support

Integration help for Redis topology, runtime sizing, CLI use, and production rollout questions.

Updates

Access to commercial fixes and customer-visible package releases during the license term.