Software Alternatives, Accelerators & Startups

Tarantool VS KeyDB

Compare Tarantool VS KeyDB and see what are their differences

Tarantool logo Tarantool

A NoSQL database running in a Lua application server.

KeyDB logo KeyDB

KeyDB is fast NoSQL database with full compatibility for Redis APIs, clients, and modules.
  • Tarantool Landing page
    Landing page //
    2023-04-27
  • KeyDB Landing page
    Landing page //
    2022-06-19

Tarantool features and specs

  • High Performance
    Tarantool is renowned for its high-speed transactions and low-latency response times, making it suitable for applications that require fast data processing.
  • In-Memory Storage
    Utilizes an in-memory architecture, which enhances data retrieval speeds, beneficial for real-time applications and caching solutions.
  • Lua Integration
    Provides seamless integration with Lua scripting, allowing developers to easily write stored procedures and embed logic directly with the data layer.
  • Scalability
    Offers features like asynchronous replication and sharding, enabling horizontal scaling for large-scale applications.
  • Flexible Schema
    Supports schema-less design, giving developers the flexibility to handle data without strict schemas, making it versatile for evolving data models.

Possible disadvantages of Tarantool

  • Limited Community Support
    Being a less mainstream technology compared to other databases, it has a smaller community, which might mean less third-party resources and community-driven support.
  • Complexity
    Its powerful features can add complexity, making it potentially challenging for developers unfamiliar with in-memory databases and advanced configurations.
  • Fewer Integrations
    Compared to more popular databases, Tarantool may have fewer out-of-the-box integrations with third-party applications and services.
  • Learning Curve
    Requires understanding of Lua scripting and its architecture, which might pose a learning hurdle for developers accustomed to more conventional databases.
  • Limited Documented Use Cases
    There is a relative scarcity of documented use cases and real-world applications, which could be a drawback for companies looking for proven and documented success stories.

KeyDB features and specs

  • High Performance
    KeyDB offers superior performance over Redis by allowing multi-threading, which utilizes multiple CPU cores efficiently, leading to significant improvements in throughput and latency.
  • Redis Compatibility
    KeyDB is fully compatible with Redis, meaning users can easily switch between Redis and KeyDB without needing to change their existing code or data structures.
  • Active Replication
    It supports multi-primary (active-active) replication, enabling all replicas to accept writes without worrying about conflicts, which increases availability and resilience.
  • Built-in TLS
    KeyDB includes built-in TLS support which enhances security by allowing data encryption in transit, a feature that requires third-party solutions in some Redis setups.
  • Persistence Options
    KeyDB supports both RDB snapshotting and AOF logging, offering flexible persistence strategies to balance between performance and durability.

Possible disadvantages of KeyDB

  • Community Size
    KeyDB, while gaining popularity, has a smaller community compared to Redis, which can lead to less community support and fewer third-party tools or extensions.
  • Maturity
    As a relatively newer project compared to Redis, KeyDB may lack the same level of proven stability and maturity, making it a potentially riskier choice for critical applications.
  • Documentation and Resources
    While KeyDB has extensive documentation, it might not be as comprehensive or complete as Redis, potentially leading to longer project integration times.
  • Potential Compatibility Issues
    Although KeyDB is compatible with Redis, advanced Redis features or unusual configurations might face compatibility issues during migration.
  • Less Architectural Simplicity
    The added complexity of multi-threading and active-active replication modes can increase the operational overhead compared to Redis's simpler single-threaded, master-slave architecture.

Tarantool videos

5. СУБД в HighLoad. Tarantool | Технострим

More videos:

  • Review - Поговорим про Tarantool.io, что это такое и как живёт
  • Review - Принципы и приёмы обработки очередей / Константин Осипов (tarantool.org)

KeyDB videos

KeyDB on FLASH (Redis Compatible)

More videos:

  • Demo - Simple Demo of KeyDB on Flash in under 7 minutes (Drop in Redis Alternative)

Category Popularity

0-100% (relative to Tarantool and KeyDB)
NoSQL Databases
32 32%
68% 68
Databases
28 28%
72% 72
Key-Value Database
26 26%
74% 74
Relational Databases
50 50%
50% 50

User comments

Share your experience with using Tarantool and KeyDB. For example, how are they different and which one is better?
Log in or Post with

Reviews

These are some of the external sources and on-site user reviews we've used to compare Tarantool and KeyDB

Tarantool Reviews

We have no reviews of Tarantool yet.
Be the first one to post

KeyDB Reviews

Redis vs. KeyDB vs. Dragonfly vs. Skytable | Hacker News
2. KeyDB: The second is KeyDB. IIRC, I saw it in a blog post which said that it is a "multithreaded fork of Redis that is 5X faster"[1]. I really liked the idea because I was previously running several instances of Redis on the same node and proxying them like a "single-node cluster." Why? To increase CPU utilization. A single KeyDB instance could replace the unwanted...
Comparing the new Redis6 multithreaded I/O to Elasticache & KeyDB
Because of KeyDB’s multithreading and performance gains, we typically need a much larger benchmark machine than the one KeyDB is running on. We have found that a 32 core m5.8xlarge is needed to produce enough throughput with memtier. This supports throughput for up to a 16 core KeyDB instance (medium to 4xlarge)
Source: docs.keydb.dev
KeyDB: A Multithreaded Redis Fork | Hacker News
"KeyDB works by running the normal Redis event loop on multiple threads. Network IO, and query parsing are done concurrently. Each connection is assigned a thread on accept(). Access to the core hash table is guarded by spinlock. Because the hashtable access is extremely fast this lock has low contention. Transactions hold the lock for the duration of the EXEC command....

Social recommendations and mentions

Based on our record, KeyDB seems to be more popular. It has been mentiond 10 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

Tarantool mentions (0)

We have not tracked any mentions of Tarantool yet. Tracking of Tarantool recommendations started around Mar 2021.

KeyDB mentions (10)

  • Redis
    These facts only hold when the size of your payload and the number of connections remain relatively small. This easily jumps out the window with ever-increasing load parameters. The threshold is, unfortunately, rather low at a high number of connections and increased payload sizes. Modern large-scale micro-services will easily have over 100 running instances at medium scale. And since most instances employ some... - Source: dev.to / 3 months ago
  • Introducing LMS Moodle Operator
    The LMS Moodle Operator serves as a meta-operator, orchestrating the deployment and management of Moodle instances in Kubernetes. It handles the entire stack required to run Moodle, including components like Postgres, Keydb, NFS-Ganesha, and Moodle itself. Each of these components has its own Kubernetes Operator, ensuring seamless integration and management. - Source: dev.to / about 1 year ago
  • Dragonfly Is Production Ready (and we raised $21M)
    Congrats on the funding and getting production ready, it's good that KeyDB (and Redis) get some competition. https://docs.keydb.dev/ Open question, how does Dragonfly differ from KeyDB? - Source: Hacker News / about 2 years ago
  • I deleted 78% of my Redis container and it still works
    See: Distroless images[0] This is one of the huge benefits of recent systems languages like go and rust -- they compile to single binaries so you can use things like scatch[1] containers. You may have to fiddle with gnu libc/musl libc (usually when getaddrinfo is involved/dns etc), but once you're done with it, packaging is so easy. Even languages like Node (IMO the most progressive of the scripting languages)... - Source: Hacker News / almost 3 years ago
  • Dragonflydb – A modern replacement for Redis and Memcached
    Interesting project. Very similar to KeyDB [1] which also developed a multi-threaded scale-up approach to Redis. It's since been acquired by Snapchat. There's also Aerospike [2] which has developed a lot around low-latency performance. 1. https://docs.keydb.dev/ 2. https://aerospike.com/. - Source: Hacker News / almost 3 years ago
View more

What are some alternatives?

When comparing Tarantool and KeyDB, you can also consider the following products

Redis - Redis is an open source in-memory data structure project implementing a distributed, in-memory key-value database with optional durability.

Apache Ignite - high-performance, integrated and distributed in-memory platform for computing and transacting on...

MongoDB - MongoDB (from "humongous") is a scalable, high-performance NoSQL database.

Hazelcast - Clustering and highly scalable data distribution platform for Java

memcached - High-performance, distributed memory object caching system

Aerospike - Aerospike is a high-performing NoSQL database supporting high transaction volumes with low latency.