Upstream software project

redict

Persistent key-value database with network interface (client)

About redict

Persistent key-value database with network interface (client)

This project links 27 native package records across 7 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Alpine Linux 3.21: 5 package records; Alpine Linux 3.22: 5 package records; Alpine Linux 3.23: 5 package records; Debian 12 (Bookworm): 4 package records; Debian 13 (Trixie): 4 package records; Fedora 43: 2 package records; Fedora 44: 2 package records. Catalog coverage diagram, not an application screenshot.redict: recorded package coverageAlpine Linux 3.215 recordsAlpine Linux 3.225 recordsAlpine Linux 3.235 recordsDebian 12 (Bookworm)4 recordsDebian 13 (Trixie)4 recordsFedora 432 recordsFedora 442 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
redict
Publisher
Not authoritatively mapped
Native package records
27
Operating systems
alpine-linux-3-21, alpine-linux-3-22, alpine-linux-3-23, debian-12, debian-13, fedora-43, fedora-44
License expression
Not reported
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Redict is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Redict works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Redict also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Redict behave like a cache. You can use Redict from most programming languages also.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Alpine Linux 3.21

  1. Package redict

    v3.21 (Alpine Linux 3.21): A distributed key/value database

    7.3.3-r1: aarch64 x86_64

    Source: redict

  2. Package redict-benchmark

    v3.21 (Alpine Linux 3.21): Redict benchmarking tool

    7.3.3-r1: aarch64 x86_64

    Source: redict

  3. Package redict-cli

    v3.21 (Alpine Linux 3.21): Redict CLI client

    7.3.3-r1: aarch64 x86_64

    Source: redict

  4. Package redict-compat

    v3.21 (Alpine Linux 3.21): Redict command symlinks and system group for compatibility with redis

    7.3.3-r1: aarch64 x86_64

    Source: redict

  5. Package redict-openrc

    v3.21 (Alpine Linux 3.21): A distributed key/value database (OpenRC init scripts)

    7.3.3-r1: aarch64 x86_64

    Source: redict

Alpine Linux 3.22

  1. Package redict

    v3.22 (Alpine Linux 3.22): A distributed key/value database

    7.3.6-r0: aarch64 x86_64

    Source: redict

  2. Package redict-benchmark

    v3.22 (Alpine Linux 3.22): Redict benchmarking tool

    7.3.6-r0: aarch64 x86_64

    Source: redict

  3. Package redict-cli

    v3.22 (Alpine Linux 3.22): Redict CLI client

    7.3.6-r0: aarch64 x86_64

    Source: redict

  4. Package redict-compat

    v3.22 (Alpine Linux 3.22): Redict command symlinks and system group for compatibility with redis

    7.3.6-r0: aarch64 x86_64

    Source: redict

  5. Package redict-openrc

    v3.22 (Alpine Linux 3.22): A distributed key/value database (OpenRC init scripts)

    7.3.6-r0: aarch64 x86_64

    Source: redict

Alpine Linux 3.23

  1. Package redict

    v3.23 (Alpine Linux 3.23): A distributed key/value database

    7.3.6-r0: aarch64 x86_64

    Source: redict

  2. Package redict-benchmark

    v3.23 (Alpine Linux 3.23): Redict benchmarking tool

    7.3.6-r0: aarch64 x86_64

    Source: redict

  3. Package redict-cli

    v3.23 (Alpine Linux 3.23): Redict CLI client

    7.3.6-r0: aarch64 x86_64

    Source: redict

  4. Package redict-compat

    v3.23 (Alpine Linux 3.23): Redict command symlinks and system group for compatibility with redis

    7.3.6-r0: aarch64 x86_64

    Source: redict

  5. Package redict-openrc

    v3.23 (Alpine Linux 3.23): A distributed key/value database (OpenRC init scripts)

    7.3.6-r0: aarch64 x86_64

    Source: redict

Debian 12 (Bookworm)

  1. Package redict

    bookworm-backports (Debian 12 (Bookworm)) (database): Persistent key-value database with network interface (metapackage)

    7.3.6+ds-2~bpo12+1: all

  2. Package redict-sentinel

    bookworm-backports (Debian 12 (Bookworm)) (database): Persistent key-value database with network interface (monitoring)

    7.3.6+ds-2~bpo12+1: amd64 arm64

    Source: redict

  3. Package redict-server

    bookworm-backports (Debian 12 (Bookworm)) (database): Persistent key-value database with network interface

    7.3.6+ds-2~bpo12+1: amd64 arm64

    Source: redict

  4. Package redict-tools

    bookworm-backports (Debian 12 (Bookworm)) (database): Persistent key-value database with network interface (client)

    7.3.6+ds-2~bpo12+1: amd64 arm64

    Source: redict

Debian 13 (Trixie)

  1. Package redict

    trixie-backports (Debian 13 (Trixie)) (database): Persistent key-value database with network interface (metapackage)

    7.3.6+ds-2~bpo13+1: all

  2. Package redict-sentinel

    trixie-backports (Debian 13 (Trixie)) (database): Persistent key-value database with network interface (monitoring)

    7.3.6+ds-2~bpo13+1: amd64 arm64

    Source: redict

  3. Package redict-server

    trixie-backports (Debian 13 (Trixie)) (database): Persistent key-value database with network interface

    7.3.6+ds-2~bpo13+1: amd64 arm64

    Source: redict

  4. Package redict-tools

    trixie-backports (Debian 13 (Trixie)) (database): Persistent key-value database with network interface (client)

    7.3.6+ds-2~bpo13+1: amd64 arm64

    Source: redict

Fedora 43

  1. Package redict

    43 (Fedora 43) (Unspecified): A persistent key-value database

    7.3.6-1.fc43: aarch64 x86_64

    Source: redict

  2. Package redict-devel

    43 (Fedora 43) (Unspecified): Development header for Redict module development

    7.3.6-1.fc43: aarch64 x86_64

    Source: redict

Fedora 44

  1. Package redict

    44 (Fedora 44) (Unspecified): A persistent key-value database

    7.3.6-1.fc44: aarch64 x86_64

    Source: redict

  2. Package redict-devel

    44 (Fedora 44) (Unspecified): Development header for Redict module development

    7.3.6-1.fc44: aarch64 x86_64

    Source: redict

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.