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.
- 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