SOFTWARE
RedGW
Redis GateWay
A gateway that provides data sharing between heterogeneous systems through standard Redis-based REST APIs, with synchronization to external databases set up by configuration.
One REST API for Data Sharing Between Systems
Business systems each use their own integration methods and authentication, so sharing data has meant building separate integrations and connecting directly to databases. RedGW places Redis in between as a shared hub and provides reads, writes, and real-time subscriptions through one REST API and one permission model. Systems that cannot call REST are connected through database synchronization.
Architecture
Core REST API Areas
- KV Key-value data storage and retrieval
- Map Object and structured data storage
- Queue Ordered queues and task management
- Group Unique data sets and set operations
- Rank Score-based ranking and sorted retrieval
- Event Event stream recording and subscription
- Pub/Sub Real-time notifications and WebSocket subscriptions
- Admin Service status and key management
Base Path: /api/v1/ns/{namespace}/{resource}/{key}
· Batch: …/{resource}/batch, …/{resource}/{key}/batch (up to 100 items)
Database Integration
- Poller DB → RedisPeriodic collection of changed data from external databases into Redis
- Reverse Poller Redis → DBChanged Redis data applied to external databases
- Table Replicator DB → DBOne-way direct replication between different database platforms
- Oracle
- Tibero
- MySQL
- MariaDB
- MSSQL
- PostgreSQL
- CUBRID
Redis is an in-memory hub for sharing, and the data of record stays in each system's database. All three synchronization modes provide connections to the seven database platforms. Tibero and CUBRID drivers are installed separately for each deployment, and integration with the target database is confirmed by testing before deployment.
Integration by Configuration, Protection at the Gateway
Integration targets are registered with connection details and synchronization settings. Access permissions, transport encryption, and audit records are applied at the gateway layer.
Connect system integration
- Batch processing — multiple reads and writes in a single call
- Accelerated processing — native acceleration for data validation and transformation
Protect access protection
- Access control — API keys, per-namespace read and write permissions, internal-network restriction for admin and metrics paths
- Transport and traffic protection — TLS encryption, rate limits, WebSocket support
- Audit logging — choice of standard logging for writes and access failures, or full logging including reads
Operate synchronization operation
- Duplicate-run prevention — concurrent runs of the same synchronization job blocked
- Health monitoring — database connections and synchronization jobs monitored, jobs resumed when the database recovers
- Integrated monitoring — service status and traffic dashboards based on Prometheus and Grafana
Use Cases
RedGW fits integrations where several business systems read and update the same data or need to receive it in real time.
- Data sharing between systems — Read and write data shared across business systems through a REST API
- REST access to database data — Changes collected from external databases and served without direct database access
- Real-time notifications — Subscription-based delivery of status changes and events
- Work request handoff — Ordered queues for work requests between systems
- Writing received data to databases — Data received over REST applied to business databases
Adoption Inquiry
We provide configuration and rollout guidance based on your requirements and operating environment. Demo and proposal requests are handled through the same contact.