LavikLAVIK 0.2.0 / FAQ
Getting started with Lavik: your questions answered
Performance, capacity cost, compatibility and migration—what you need to choose your first deployment.
What is Lavik?
Lavik is an Apache 2.0 Redis-compatible key-value store. It keeps a compact key index in DRAM and stores values on NVMe SSD, combining familiar Redis commands with much lower value-capacity cost. The current release is 0.2.0.
About Lavik →Can SSD-backed Lavik outperform Redis in DRAM?
Yes, in the published 16-vCPU SPDK test. At 10 million keys with 1 KiB values, Lavik 0.2.0 reaches 1,157.0k peak GET QPS and 945.4k peak SET QPS, above the tested Redis 8.10.2 and Valkey 9.1.2 configurations. The report includes the connection sweep, p99.9 latency, settings and reproduction commands.
See the benchmark →What does 20× lower capacity cost mean?
If DRAM costs 20 times as much per GiB as NVMe SSD, the same value payload costs 95% less in storage media on SSD. Lavik still needs memory for its index and runtime. Add replicas, CPU, networking and operations to compare complete deployments; the calculator lets you enter your own prices.
Calculate your costs →Can I keep my Redis client and data structures?
Lavik supports RESP2 and RESP3 and Redis data structures including strings, hashes, sets, lists, sorted sets and streams. The 0.2.0 manual lists command behavior and tested client versions. Match the commands and connection mode your application uses before switching its endpoint.
Check compatibility →What is the quickest way to try Lavik?
Use the Docker guide for a first instance, or install the Linux package for a host deployment. Both Minimal and Standard release archives are available for AMD64 and ARM64; Standard includes SPDK support. The quick start takes you from download to your first Redis-compatible commands.
Start with Lavik 0.2.0 →How do I migrate from Redis or Redis Cluster?
Use RedisShake v4.6.2 with a fresh managed Lavik target. The guide provides source and target configurations, full copy, incremental catch-up, a final write pause, data checks and endpoint cutover. Source and target shard counts can differ.
Follow the migration guide →How do I operate and monitor Lavik?
The release includes lavik, lavik-meta, lavik-ctl and Lavik Admin. Use the managed-deployment guides for topology, replication and failover, and the monitoring guide for Prometheus and Grafana. Choose Single or Cluster mode to match your application’s routing requirements.
Read the operations guides →Is Lavik free to use in a commercial application?
Yes. Lavik is open source under Apache 2.0. The source, architecture documents and benchmark procedures are public. You can use it in your projects, contribute improvements and discuss your workload with the community.
Join the community →