DBMS > Geode vs. GeoMesa vs. InfluxDB vs. SQLite

System Properties Comparison Geode vs. GeoMesa vs. InfluxDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

DBMS for storing time series, events and metrics

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Spatial DBMS

with GEO package

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	24.39
Rank	#28	Overall
	#1	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

geode.apache.org

www.geomesa.org

www.influxdata.com/products/influxdb-overview

www.sqlite.org

Technical documentation

geode.apache.org/docs

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

docs.influxdata.com/influxdb

www.sqlite.org/docs.html

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

CCRi and others

Dwayne Richard Hipp

Initial release

2002

2014

2013

2000

Current release

1.1, February 2017

5.0.0, May 2024

2.7.6, April 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache License 2.0

Open Source

MIT-License; commercial enterprise version available

Open Source

Public Domain

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

Java

Scala

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X

through Homebrew

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numeric data and Strings

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HTTP API
JSON over UDP

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Perl
PHP
Python
R
Ruby
Rust
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

in enterprise version only

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

depending on storage layer

selectable replication factor

in enterprise version only

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

depending on storage layer

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

depending on storage layer

yes

Depending on used storage engine

yes

User concepts

Access control

Access rights per client and object definable

yes

depending on the DBMS used for storage

simple rights management via user accounts

More information provided by the system vendor

Specific characteristics

InfluxData is the creator of InfluxDB , the open source time series database. It...
» more

Competitive advantages

Time to Value InfluxDB is available in all the popular languages and frameworks,...
» more

Typical application scenarios

IoT & Sensor Monitoring Developers are witnessing the instrumentation of every available...
» more

Key customers

InfluxData has more than 1,900 paying customers, including customers include MuleSoft,...
» more

Market metrics

Fastest-growing database to drive 27,500 GitHub stars Over 750,000 daily active instances
» more

Licensing and pricing models

Open source core with closed source clustering available either on-premise or on...
» more

News

Apache Superset and InfluxDB Cloud 3.0
14 June 2024

Scaling Data Collection: Solving Renewable Energy Challenges with InfluxDB
6 June 2024

Deadman Alerts with Grafana and InfluxDB Cloud 3.0
5 June 2024

Chasing the Skies: Monitoring Flights with InfluxDB
4 June 2024

Monitoring Your Cloud Environments and Applications with InfluxDB
30 May 2024

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.