https://redislabs.com/redis-enterprise/advantages/
> Redis Enterprise is a robust in-memory database platform built by the people who develop open source Redis. It maintains the simplicity and high performance of Redis, while adding many enterprise-grade capabilities, such as linear scaling to hundreds of millions of operations per second, Active-Active geo-replication with local latency, Redis on Flash to tier data across dynamic and persistent memory and solid-state disk (SSD) to reduce total cost of ownership, and five-nines (99.999%) uptime based on built-in durability and single-digit-seconds failover. Redis Enterprise supports many data modeling methods with modules such as RediSearch, RedisJSON, RedisGraph, RedisTimeSeries, RedisBloom, and RedisAI, and allows operations to be executed across and between modules and core Redis functionality using RedisGears, a serverless engine that runs across shards and nodes of Redis Enterprise cluster. All this while keeping database latency under one millisecond, so your application can respond instantaneously. Learn how to implement the best in-memory database: Redis Enterprise.
That said, theres equal if not greater motivation for this hypothetical contributor to raise their own $100mm and compete with Redis Labs.
- professional support
- proprietary modules for Redis
- advice on integrating Redis into their legacy systems
When I, as a developer, have an issue with some open source code, I spend some amount of time fixing it (labor cost), and some amount of time with a broken system (downtime). But it's not a big deal for me, if I spend 30 minutes troubleshooting a problem. Scale that up to a company with thousands of employees, and those can be big costs.
I am saying that source code licenses are irrelevant to support and operations costs.
Both RedHat and Microsoft will sell you a support contract.
I've personally mostly used it as a message broker (celery in python, resque in ruby), but it can definitely be used as a database.
Bottom line, it's a very flexible tool, and can be more than "just a cache".
> I've personally mostly used it as a message broker
Did you geo replicate message broker?
Maybe, I actually have no idea, have you seen numbers?
> Their valuation reflects its use as a cache
How so?
> Did you geo replicate message broker?
No