In-memory Database Redis Wants To Dabble in Disk (theregister.com) 5
Redis, the go-to in-memory database used as a cache and system broker, is looking to include disk as part of a tiered storage architecture to reduce costs and broaden the system's appeal. From a report: Speaking to The Register, CEO Rowan Trollope said he hoped the move would help customers lower costs and simplify their architecture. Redis counts Twitter X, Snapchat, and Craigslist among its customers, and it's popular among developers of modern internet-scale applications owing to its ability to create a cache to prevent the main database from overloading. Trollope said the sub-millisecond distributed system gives devs the performance they need, but admitted other systems built for internet scale, such as MongoDB, might offer price advantages. To address this, the company has already created a tiered approach to memory by offering flash support behind its in-memory system.
"We have a half-step between disk and memory. For some specific use cases, in gaming for example, a company might use us for leaderboards and other in-game stats, which they need in real time," he said. However, after an initial flush of the game launch, a large chunk of users would finish the game and their accounts would go dormant until the release of a new episode or some new content, when they might return. Trollope said using flash allowed users to dynamically tier memory. "We can take the lesser-used data that hasn't been touched in a while and shuttle it off to flash where it can sit for a while. When the user comes back eventually, it's very easy for us to seamlessly move it from flash back into memory. And that allows the company to save costs," he said.
"We have a half-step between disk and memory. For some specific use cases, in gaming for example, a company might use us for leaderboards and other in-game stats, which they need in real time," he said. However, after an initial flush of the game launch, a large chunk of users would finish the game and their accounts would go dormant until the release of a new episode or some new content, when they might return. Trollope said using flash allowed users to dynamically tier memory. "We can take the lesser-used data that hasn't been touched in a while and shuttle it off to flash where it can sit for a while. When the user comes back eventually, it's very easy for us to seamlessly move it from flash back into memory. And that allows the company to save costs," he said.
Not a coincidence? (Score:2)
Maybe it's not a coincidence that DHH called out redis at RailsWorld.
In the keynote at the 47 minute mark he starts in.
https://www.youtube.com/watch?... [youtube.com]
TLDR: SDD is super fast. Maybe let's ditch redis and use disk.
For them it worked out to be better performing since you can cache for weeks instead of hours or days.
Until you mis-cache to disc (Score:2)
Not impressed (Score:2)
AWS Elasticache already does this with it Data Tiering feature. Keys are stored in memory but values up to 128MB can be stored on a local SSD with 1ms performance penalty. Pretty impressive setup and I can see how it could be useful in certain caching architectures.
Not to be confused with ... (Score:2)
... disk-based databases that cache frequently used data in memory ...