Software Alternatives & Reviews

Tile38 VS KeyDB

Compare Tile38 VS KeyDB and see what are their differences

Tile38 logo Tile38

Geospatial database and real-time geofence server for managing fleets, mobile apps, and IoT devices.

KeyDB logo KeyDB

KeyDB is fast NoSQL database with full compatibility for Redis APIs, clients, and modules.
  • Tile38 Landing page
    Landing page //
    2021-08-26
  • KeyDB Landing page
    Landing page //
    2022-06-19

Tile38 videos

GopherCon 2018 Lightning Talk: Josh Baker - Roaming Geofences with Tile38

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 Tile38 and KeyDB)
Databases
25 25%
75% 75
NoSQL Databases
26 26%
74% 74
Key-Value Database
20 20%
80% 80
Search API
100 100%
0% 0

User comments

Share your experience with using Tile38 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 Tile38 and KeyDB

Tile38 Reviews

We have no reviews of Tile38 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 should be more popular than Tile38. It has been mentiond 9 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.

Tile38 mentions (1)

  • Your Data Fits in RAM
    I actually worked on a project that did this. We used a database called "Tile38" [1] which used an R-Tree to make geospatial queries speedy. It was pretty good. Our dataset was ~150 GiB, I think? All in RAM. Took a while to start the server, as it all came off disk. Could have been faster. (It borrowed Redis's query language, and its storage was just "store the commands the recreate the DB, literally", IIRC. Dead... - Source: Hacker News / almost 2 years ago

KeyDB mentions (9)

  • 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 / 5 days 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 1 year 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 2 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 2 years ago
  • Dragonflydb – A modern replacement for Redis and Memcached
    How does this compare to other multithreaded redis protocol compatibles? KeyDB is one key player https://docs.keydb.dev/. - Source: Hacker News / almost 2 years ago
View more

What are some alternatives?

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

VoltDB - In-memory relational DBMS capable of supporting millions of database operations per second

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

memcached - High-performance, distributed memory object caching system

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

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

Beringei - High performance, in-memory storage engine for time series data (by Facebook)