LavikCompatibility Overview
Choose the correct client mode and check the exact commands your application uses.
Protocol And Data Types
Lavik uses the Redis protocol, including RESP2 and RESP3 negotiation, and targets Redis 7.2 semantics for the exposed commands. Supported families include Strings, Hashes, Sets, Sorted Sets, Lists, Streams, Geo, bitmaps, transactions, Lua/Functions and Pub/Sub. Compatibility is command- and option-specific; it is not a claim to implement every Redis module or later extension.
Standalone, Managed Single And Cluster
A Data node with --meta-seed gets client_mode from Meta’s committed manifest. Single has one Group spanning all slots and DB0–15, without MOVED redirects. Cluster uses DB0, MOVED routing and CROSSSLOT checks; complete replicas require READONLY for cluster reads. Transactions, scripts and Stream operations are admitted through the same authority and storage rules as other commands in 0.2.0.
Cluster Function libraries and keyless FLUSH operations are scoped to the receiving Group. Do not assume one request updates every Group. Live slot migration and CLUSTER SHARDS are not supported; use CLUSTER SLOTS with compatible clients.
Known Boundaries
CLIENT TRACKING and COMMAND INFO are not supported. Disable client-side caching in valkey-go. The command reference records rejected examples for ACL, HyperLogLog, RedisJSON/search module commands, field-level expiry and sharded Pub/Sub. WAIT is a bounded replica-acknowledgement fence, not a synchronous commit or a lossless-failover guarantee.