DBMS > GeoMesa vs. Graph Engine vs. Splunk vs. TimescaleDB

System Properties Comparison GeoMesa vs. Graph Engine vs. Splunk vs. TimescaleDB

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.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Analytics Platform for Big Data

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Spatial DBMS

Graph DBMS
Key-value store

Search engine

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

Technical documentation

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

www.graphengine.io/docs/manual

docs.splunk.com/Documentation/Splunk

docs.timescale.com

Developer

CCRi and others

Microsoft

Splunk Inc.

Timescale

Initial release

2014

2010

2003

2017

Current release

4.0.5, February 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

MIT License

commercial

Limited free edition and free developer edition available

Open Source

Apache 2.0

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

.NET and C

Server operating systems

.NET

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

yes

Secondary indexes

yes

SQL

Support of SQL

Splunk Search Processing Language for search commands

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP API

HTTP REST

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C#
C++
F#
Visual Basic

C#
Java
JavaScript
PHP
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

Source-replica replication with hot standby and reads on replicas

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and roles

fine grained access rights according to SQL-standard

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

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Recent citations in the news

Trinity
2 June 2023, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

The graph analytics landscape 2019 - DataScienceCentral.com
27 February 2019, Data Science Central

provided by Google News

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL
18 March 2019, Microsoft

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, businesswire.com

SQL and TimescaleDB. This article takes a closer look into… | by Alibaba Cloud
31 July 2019, DataDrivenInvestor

provided by Google News

Share this page