Software Alternatives, Accelerators & Startups

KeyDB VS Google Cloud Datastore

Compare KeyDB VS Google Cloud Datastore and see what are their differences

KeyDB logo KeyDB

KeyDB is fast NoSQL database with full compatibility for Redis APIs, clients, and modules.

Google Cloud Datastore logo Google Cloud Datastore

Cloud Datastore is a NoSQL database for your web and mobile applications.
  • KeyDB Landing page
    Landing page //
    2022-06-19
  • Google Cloud Datastore Landing page
    Landing page //
    2023-09-12

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.

Google Cloud Datastore features and specs

  • Scalability
    Google Cloud Datastore can automatically scale to handle large amounts of data and high read/write loads, making it suitable for applications with growing data needs.
  • Fully Managed
    As a fully managed service, Google Cloud Datastore eliminates the need for managing servers, software patches, and replication, allowing developers to focus on building applications.
  • High Availability
    Datastore provides strong consistency for reads and writes and is designed to maintain availability even in case of entire data center outages.
  • Flexible Data Model
    The schemaless nature of Datastore allows for a flexible data model that can easily adapt to changes in application requirements.
  • Integration with Google Cloud Platform
    Datastore seamlessly integrates with other Google Cloud Platform services, which simplifies the process of building end-to-end solutions.

Possible disadvantages of Google Cloud Datastore

  • Complex Query Language
    Datastore Query Language (GQL) can be less intuitive compared to SQL, which may pose a learning curve for developers accustomed to traditional relational databases.
  • Eventual Consistency for Queries
    While Datastore offers strong consistency for entity lookups by key, queries must be specifically configured for strong consistency, otherwise they might return eventually consistent data.
  • Cost
    As usage scales, costs can increase, particularly for applications with high write loads or those requiring many transactional operations, which might be a consideration for budget-conscious projects.
  • Limited Relational Capabilities
    Datastore is a NoSQL database, which means it lacks some of the relational features like joins and complex transactions that developers might expect from a SQL database.
  • Index Management
    Managing indexes can become complex, as every query in Datastore requires a corresponding index, and poorly planned indexes can lead to increased storage costs and slower query performance.

KeyDB videos

KeyDB on FLASH (Redis Compatible)

More videos:

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

Google Cloud Datastore videos

No Google Cloud Datastore videos yet. You could help us improve this page by suggesting one.

Add video

Category Popularity

0-100% (relative to KeyDB and Google Cloud Datastore)
Databases
47 47%
53% 53
Key-Value Database
100 100%
0% 0
NoSQL Databases
41 41%
59% 59
Network & Admin
0 0%
100% 100

User comments

Share your experience with using KeyDB and Google Cloud Datastore. 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 KeyDB and Google Cloud Datastore

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....

Google Cloud Datastore Reviews

We have no reviews of Google Cloud Datastore yet.
Be the first one to post

Social recommendations and mentions

KeyDB might be a bit more popular than Google Cloud Datastore. We know about 10 links to it since March 2021 and only 7 links to Google Cloud Datastore. 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.

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 / over 1 year 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 / over 2 years 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 / over 3 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 / about 4 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 / about 4 years ago
View more

Google Cloud Datastore mentions (7)

  • Using Google Cloud Firestore with Django's ORM
    A long time ago, a fork of Django called โ€œDjango-nonrelโ€ experimented with the idea of using Djangoโ€™s ORM with a non-relational database; what was then called the App Engine Datastore, but is now known as Google Cloud Datastore (or technically, Google Cloud Firestore in Datastore Mode). Since then a more recent project called "django-gcloud-connectors" has been developed by Potato to allow seamless ORM integration... - Source: dev.to / about 2 years ago
  • How to deploy flask app with sqlite on google cloud ?
    In that case use Cloud Datastore (aka Firestore in Datastore Mode). It's a NoSQL db that was initially targeted just for GAE (you needed to have a GAE App even if empty to use it) but that requirement has been relaxed. Source: over 3 years ago
  • Is Cloud Run a good choice for a portfolio website?
    As u/SierraBravoLima said - If you don't really need containerization, you can go with Google App Engine (Standard). If you need to store data, GAE will work with cloud datastore which has a large enough free tier. Source: over 4 years ago
  • Help! Difference between native and datastore
    Datastore mode had its start in App Engine's early days (launched in 2008), where its Datastore was the original scalable NoSQL database provided for all App Engine apps. In 2013, Datastore was made available all developers outside of App Engine, and "re-launched" as Cloud Datastore. In 2014, Google acquired Firebase for its RTDB (real-time database). Both teams worked together for the next 4 years, and in 2017,... Source: over 4 years ago
  • I'm a dev ID 10 T please help me
    Database: datastore should be very cheap, or you could just output as csv text and copy into Google Sheets (free!). Source: over 4 years ago
View more

What are some alternatives?

When comparing KeyDB and Google Cloud Datastore, 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.

MarkLogic Server - MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities.

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

Datomic - The fully transactional, cloud-ready, distributed database

Skytable - Skytable is a free and open-source realtime NoSQL database that aims to provide flexible data modelling at scale.

Valentina Server - Valentina Server is 3 in 1: Valentina DB Server / SQLite Server / Report Server