This is a draft document that was built and uploaded automatically. It may document beta software and be incomplete or even incorrect. Use this document at your own risk.

Jump to content
Introduction to Valkey
SUSE Linux Enterprise Server 16.0

Introduction to Valkey

Publication Date: 24 Oct 2025
WHAT?

Valkey is an open source in-memory data structure store that excels as a database, cache, message broker and streaming engine. Valkey provides a high-performance, scalable and versatile in-memory data store, crucial for accelerating applications and efficiently managing diverse data needs with enhanced multi-threading and reliability.

WHY?

Learn about how to install and configure Valkey.

EFFORT

40 minutes of reading time.

GOAL

Setting up Valkey on SUSE Linux Enterprise Server for SAP applications or migrating from Redis to Valkey.

1 About Valkey

 

Valkey is a fork of Redis version 7.2.4. It is an open source, in-memory data structure store, licensed under the BSD (Berkeley Software Distribution) license, that serves as a versatile platform for various applications. It excels as a database, providing fast and flexible data storage; as a cache, significantly improving application performance; as a message broker, enabling asynchronous communication; and even as a streaming engine for real-time data processing. Valkey builds upon the foundation of Redis OSS, incorporating multi-threading for enhanced performance and offering a robust solution for applications demanding speed, scalability, and diverse data handling capabilities.

Valkey has many benefits, which include the following:

  • Delivers fast, low-latency access to data stored in memory, ideal for caching, real-time analytics, and message brokering.

  • Supports powerful and versatile data structures like strings, hashes, lists, sets, sorted sets, streams, and geo-spatial indexes.

  • Offers RDB (Redis Database Backup) snapshot and AOF (append-only file) persistence for recovering data after restarts.

  • Enables horizontal scaling by partitioning data across multiple nodes.

  • Maintains compatibility with Redis 7.2, making it easy to migrate without changing existing client libraries or application logic.

  • Provides built-in publish/subscribe capabilities for building event-driven or messaging-based systems.

For more information on Valkey, refer to https://valkey.io/docs/.

2 Managing Valkey

 

Learn how to install Valkey, use the command-line tool and migrate from Redis to Valkey.

2.1 Setting up a Valkey service file

 

Valkey is an open-source and in-memory data store that functions as a database, cache, message broker and streaming engine.

Procedure 1: Creating a Valkey systemd service file
 

  1. Install Valkey:

    > sudo  zypper -n in valkey

  2. Create a Valkey systemd service file:

    > sudo  vi /etc/systemd/system/valkey.service

  3. Add the following to the file:

    [Unit]
        Description=Valkey In-Memory Data Store
        After=network.target

        [Service]
        User=valkey
        Group=valkey
        ExecStart=/usr/sbin/redis-server /etc/redis/valkey.conf
        LimitNOFILE=10240
        ExecStop=/usr/bin/valkey-cli shutdown
        Restart=always

        [Install]
        WantedBy=multi-user.target

  4. Copy the sample file to the specified config file: 

    > sudo  cp /etc/valkey/default.conf.example /etc/valkey/valkey.conf

  5. Update file permissions: 

    > sudo  chown valkey:valkey /etc/valkey/valkey.conf

  6. Start and enable the Valkey service: 

    > sudo  systemctl start valkey
    > sudo  systemctl enable valkey

  7. Verify the Valkey setup: 

    valkey-cli ping

    Valkey is running on your system when you get the command print PONG.

2.2 The Valkey command-line interface

 

The Valkey command-line interface is used for managing, debugging and testing Valkey. By default, the valkey-cli command connects to the server at the address 127.0.0.1 with port 6379.

Some of the valkey-cli command options include:

-h

Server host name with default ip of 127.0.0.1.

-p

Server port with a default vale of 6379.

-t

Server connection timeout in seconds (decimals allowed). Default timeout is 0, which means no limit and depends on the operating system.

-s

Server socket overrides the host name and port.

-a

Password to use when connecting to the server. You can also use the VALKEYCLI_AUTH environment variable to pass this password more safely. This argument takes precedence when both options are used.

--user

User name that is used to send ACL (Access Control List) style, which is AUTH username pass. Needs the -a option.

--pass

Password that is an alias of the -a option to align with the new --user option.

--askpass

Forces password input via STDIN with masking. If this argument is used, then -a and the VALKEYCLI_AUTH environment variable are ignored.

-u

Server URI in format valkey://user:password@host:port/dbnum. User, password and dbnum are optional. For authentication without a user name, use user name default. For TLS, use the scheme valkeys.

--help

Output help and exit.

--version

Output version and exit.

--cluster help

List all available cluster manager commands.

Example 1: Basic valkey-cli command examples include:
 

  • SET: Sets a key-value pair. 

    >  valkey-cli SET KEY_NAME "Hello Valkey"

    For example:

    >  valkey-cli SET TESTKEY "Hello Valkey"

  • GET: Retrieves the value associated with a key. 

    >  valkey-cli GET TESTKEY
  "Hello Valkey"

  • DEL: Deletes a key. 

    >  valkey-cli DEL TESTKEY
  (integer) 1

    1 if deleted and 0 if not found.

  • INFO: Displays information and statistics about the Valkey server. 

    >  valkey-cli INFO
  Server
  redis_version:7.2.4
  server_name:valkey
  valkey_version:8.0.2
  redis_git_sha1:00000000
  redis_git_dirty:0
  redis_build_id:e0cc1d08b1f9571a
  server_mode:standalone
  os:Linux 6.12.0-160000.9-default x86_64
  arch_bits:64
  monotonic_clock:POSIX clock_gettime
  multiplexing_api:epoll
  gcc_version:13.3.1
  process_id:974
  process_supervised:no
  run_id:32864c141804bcb17cae98145beee86ca251afd7
  tcp_port:6379
  server_time_usec:1750760734442451
  uptime_in_seconds:2780
  uptime_in_days:0
  hz:10
  configured_hz:10
  lru_clock:5930270
  executable:/usr/sbin/redis-server
  config_file:/etc/valkey/valkey.conf
  io_threads_active:0
  availability_zone:

[...]

  • MONITOR: Streams all commands processed by the Valkey server in real time. 

    >  valkey-cli MONITOR
OK

  • KEYS: Finds all keys matching a pattern. 

    >  valkey-cli KEYS "*" # All keys
"TESTKEY"
"TESTKEY1"

2.3 Migrating from Redis to Valkey

 

Valkey is designed to be a seamless replacement, maintaining compatibility with the Redis API, protocol, persistence data, ports and configuration files. The transition from Redis to Valkey is easy for many basic setups. The following procedure assumes Redis is installed, running and loaded with data.

Procedure 2: How to migrate from Redis to Valkey
 

  1. Check the current Redis server version:

    >  redis-cli info server
        # Server
        redis_version:7.2.4
        redis_git_sha1:00000000
        redis_git_dirty:0
        redis_build_id:8c22b097984bd350
        redis_mode:standalone
        [...]

  2. Install valkey-compat-redis package with the --force-resolution option: 

    > sudo  # zypper in --force-resolution valkey-compat-redis
        Refreshing service 'NVIDIA'.
        Refreshing service 'openSUSE'.
        Loading repository data...
        Reading installed packages...
        Resolving package dependencies...

        The following 2 NEW packages are going to be installed:
          valkey valkey-compat-redis

        The following package is going to be REMOVED:
          redis

        2 new packages to install, 1 to remove.

        Package download size:     1.3 MiB

        Package install size change:
                      |       5.2 MiB  required by packages that will be installed
          -245.2 KiB  |  -    5.4 MiB  released by packages that will be removed

        Backend:  classic_rpmtrans
        Continue? [y/n/p/...? shows all options] (y):

    The package takes your existing configuration files and persistence data and moves them to Valkey with no additional steps required. This migration is possible because Valkey is fully compatible with the Redis API, protocol, persistence data, ports and configuration files.

  3. Start and enable Valkey:

    > sudo  systemctl start valkey
    > sudo  systemctl enable valkey

  4. Check the server information:

    >  redis-cli info server
            # Server
            redis_version:7.2.4
            server_name:valkey
            valkey_version:7.2.5
            redis_git_sha1:00000000
            redis_git_dirty:0
            redis_build_id:b0d9f188ef999bd3
            redis_mode:standalone
            [...]

    Valkey is responsive to both redis_version:7.2.4 and valkey_version:7.2.5. Retaining the redis_version ensures maximum compatibility while still identifying the server with valkey_version. Valkey has a binary named valkey-cli but symbolically links redis-cli. Both CLIs have the same functionality.

GNU Free Documentation License

Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or non-commercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

You may copy and distribute the Document in any medium, either commercially or non-commercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

  1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.

  2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.

  3. State on the Title page the name of the publisher of the Modified Version, as the publisher.

  4. Preserve all the copyright notices of the Document.

  5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.

  6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.

  7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.

  8. Include an unaltered copy of this License.

  9. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.

  10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.

  11. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.

  12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.

  13. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.

  14. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.

  15. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See https://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. 

Copyright (c) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled “GNU
Free Documentation License”.

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with...Texts.” line with this: 

with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.