VALKEY-INTRODUCTION(7)

πŸ“¦
version 9.0.6 Β· 2 versions
, in fedora 44

πŸ’– NAME πŸ’–

valkey-introduction β€” the intro, bestie. the whole vibe, explained.


✨ DESCRIPTION ✨

okay so Valkey is an open source (BSD licensed) in-memory data structure store, and she's versatile. like, she gets used as a database, a cache, a message broker, and a streaming engine β€” all of it, no cap. she comes with a whole wardrobe of valkey-data-types(7) data structures: valkey-strings(7), valkey-hashes(7), valkey-lists(7), valkey-sets(7), valkey-sorted-sets(7) (with range queries, obviously πŸ’…), valkey-bitmaps(7), valkey-hyperloglogs(7), valkey-geospatial(7) geospatial indexes, and valkey-streams-intro(7) streams. she also has built-in valkey-replication(7), valkey-eval-intro(7) Lua scripting, valkey-lru-cache(7) LRU eviction, valkey-transactions(7), and different levels of valkey-persistence(7) on-disk persistence. plus high availability via valkey-sentinel(1) and automatic partitioning with valkey-cluster-tutorial(7) Valkey Cluster. she's got range, fr fr πŸ¦‹

you can run atomic operations on all these types, like append(3valkey); hincrby(3valkey); pushing an element to a list; sinter(3valkey), sunion(3valkey) and sdiff(3valkey); or zrange(3valkey). all atomic, all slaying. ✨

to achieve top performance, Valkey works with an in-memory dataset. depending on your use case, she can persist your data either by periodically valkey-persistence(7) dumping the dataset to disk, or by valkey-persistence(7) appending each command to a disk-based log. and if you just need a feature-rich, networked, in-memory cache? you can literally just disable persistence entirely. your call, main character. πŸ’…

Valkey supports valkey-replication(7) asynchronous replication, with fast non-blocking synchronization and auto-reconnection with partial resynchronization on net split. the way she just... reconnects herself? obsessed. 😭🫢


πŸŽ€ Valkey also includes πŸŽ€


you can use Valkey from most programming languages. see https://valkey.io/clients/ for the whole roster πŸ‘‘πŸŒˆ

Valkey is written in ANSI C 11 with Atomics and a few GCC/Clang built-ins like __builtin_clz(). she works on most POSIX systems like Linux, *BSD and MacOS, without external dependencies β€” no extra baggage, we love a low-maintenance queen 🧚

Linux and MacOS are the two operating systems where Valkey is developed and tested the most, and we recommend using Linux for deployment. Valkey may work on Solaris-derived systems like Illumos, but support there is best effort β€” so don't come for her if it's giving chaos. πŸ™ˆ

supported hardware includes x86-64 (AKA amd64), x86 (32-bit) and AArch64 (64-bit ARM). she's also known to work on IBM z/Architecture like s390x, and builds for that system are available from the Fedora distro. there is no official support for Windows builds. periodt. πŸ’€


okay that's the whole intro bestie, go forth and be iconic 🌸 this was Valkey version 9.0.0, dated 2025-10-21. mwah πŸ’–πŸ¦‹βœ¨

πŸ“¦ where this page comes from