Close
KeyDB on FLASH

KeyDB on FLASH
"Performance and Persistence in ONE Package...
If you value your data keep it on FLASH"
  • Increase database size and decrease costs. Operate large database size when keeping everything in memory is not feasible or affordable
  • RDB and AOF files are not required. KeyDB on FLASH is persistent. Stop allocating memory to expensive forking operations. Stop deleting data when maxmemory is exceeded - evict it to FLASH
  • Optimize for your use case. KeyDB keeps hottest data in memory while the rest is stored in FLASH. Select the balance ideal for your use case.
  • KeyDB on FLASH is affordable and unlimited. Each node is limitless in regards to # cores, memory GB or FLASH database size.
Moving to KeyDB on FLASH is simple, you can download and try it easily using our deb/rpm packages or through docker. No need to sign up, get licenses, or go through a sales process. Get started with a few command lines here
KeyDB is fully compatible with Redis so migration is as easy as swapping out the server and enabling FLASH. Because we are fully compatible there is no additional work to do on the client side to use KeyDB
Ready to purchase KeyDB on FLASH?, Each license key provides unlimited cores, RAM, and FLASH per node. Only one node is needed per machine as our multithreaded architecture maximizes use of the hardware available.
License Keys are far more affordable that the alternative
Ready to purchase KeyDB on FLASH?, Each license key provides unlimited cores, RAM, and FLASH per node. Only one node is needed per machine as our multithreaded architecture maximizes use of the hardware available.
License Keys are far more affordable that the alternative

KeyDB on FLASH FAQ's:

  • How does KeyDB on FLASH decide what goes to RAM and what goes to FLASH?
    KeyDB on FLASH can be considered an overflow for your cache/memory. Similar to eviction policies, when the maxmemory value specified is exceeded the data is sent to FLASH instead of being removed. This enables hot data to remain available in RAM but for your database size to far exceed the amount of RAM available on your machine.
  • Explain FLASH persistence. What happens to the data kept in RAM?
    All data is written to FLASH and persisted similar to an fsync everysec policy. The hot data is kept in RAM for quick access but also remains persisted on FLASH.
  • How much is KeyDB Pro?
    $99.99/month per license. This can be considered per server and has no limits regarding cores, memory or FLASH database size.
  • I need to develop my application and the 2 hour built in demo time is not enough?
    Contact us for a trial license. We are flexible to ensuring the success of your project
  • I am currently using Redis, but don’t want to move to Redis enterprise. How much work is it to move to KeyDB Pro?
    Its extremely simple. KeyDB can be inserted directly to your application as a swapout to redis-server. It is already compatible with Redis and Redis Clients so there is no additional integration on your end
  • I am concerned about product support and making the switch. What if I have issues getting KeyDB working?
    If you have any questions we are friendly and responsive, give us an email to discuss and we will respond as soon as we are available. We also have support contract options available for those with strict support requirements

You can find out more on FLASH setup details here

Ready to Get Started with KeyDB Pro?