Overview
A UK-based infrastructure technology company was migrating their messaging stack to OpenShift, running Redis as a high-throughput caching layer processing millions of messages daily alongside RabbitMQ. As they modernized, they needed to ensure commercial Redis licensing compliance and architectural validation before committing to enterprise licensing.
Challenge
The firm was operating Redis at scale on OpenShift without a formal enterprise licensing agreement and needed to understand their compliance obligations, cost structure, and whether their architecture was optimally configured for production workloads.
Environment
OpenShift on cloud; Redis caching layer processing millions of messages daily; RabbitMQ for message brokering; UK regulatory environment.
Approach
AceMQ conducted an architecture and licensing workshop to validate the Redis deployment configuration, assess licensing requirements against actual usage patterns, and provide guidance on Redis Enterprise features relevant to their OpenShift deployment.
Solution
- Redis Enterprise licensing assessment and compliance path for OpenShift deployment
- Architecture workshop validating Redis cluster configuration for production workloads
- Sizing and capacity recommendations for millions of messages per day throughput
- Redis and RabbitMQ integration architecture review
- OpenShift-specific deployment and operational guidance
Outcome
The firm received a clear licensing compliance roadmap and architectural validation for their Redis deployment on OpenShift, enabling them to proceed with enterprise licensing with confidence in their configuration.
Technologies
Redis
RabbitMQ
OpenShift
Kubernetes
PostgreSQL
Kafka
