DBMS > GeoMesa vs. KeyDB vs. Lovefield vs. TigerGraph

System Properties Comparison GeoMesa vs. KeyDB vs. Lovefield vs. TigerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Embeddable relational database for web apps written in pure JavaScript

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

www.geomesa.org

github.com/Snapchat/KeyDB
keydb.dev

google.github.io/lovefield

www.tigergraph.com

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

docs.keydb.dev

github.com/google/lovefield/blob/master/docs/spec_index.md

docs.tigergraph.com

Developer

CCRi and others

EQ Alpha Technology Ltd.

Google

Initial release

2014

2019

2014

2017

Current release

4.0.5, February 2024

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD-3

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

C++

JavaScript

C++

Server operating systems

Linux

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

by using the Redis Search module

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

SQL-like query language (GSQL)

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

JavaScript

C++
Java

Server-side scripts

Stored procedures

Lua

yes

Triggers

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

using MemoryDB

User concepts

Access control

yes

depending on the DBMS used for storage

simple password-based access control and ACL

Role-based access control

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Snap snaps up database developer KeyDB to make its infrastructure more snappy
12 May 2022, TechCrunch

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, microsoft.com

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

provided by Google News

TigerGraph: Graph Analytics Platform | Graph Database
30 April 2024, tigergraph.com

TigerGraph Unveils CoPilot, Version 4.0, and New CEO
30 April 2024, Datanami

How TigerGraph CoPilot enables graph-augmented AI
30 April 2024, InfoWorld

TigerGraph unveils GenAI assistant, introduces new CEO
30 April 2024, TechTarget

TigerGraph Bolsters DB for Enterprise Graph Workloads
1 November 2023, Datanami

provided by Google News

Share this page