DBMS > Apache IoTDB vs. Coveo vs. GeoMesa vs. Graph Engine

System Properties Comparison Apache IoTDB vs. Coveo vs. GeoMesa vs. Graph Engine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

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

Primary database model

Time Series DBMS

Search engine

Spatial DBMS

Graph DBMS
Key-value store

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Website

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

docs.coveo.com

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

www.graphengine.io/docs/manual

Developer

Apache Software Foundation

Coveo

CCRi and others

Microsoft

Initial release

2018

2012

2014

2010

Current release

1.1.0, April 2023

5.0.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache License 2.0

Open Source

MIT License

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Scala

.NET and C

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

.NET

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

SQL-like query language

APIs and other access methods

JDBC
Native API

RESTful HTTP API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C#
Java
JavaScript
Python

C#
C++
F#
Visual Basic

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

yes

depending on storage layer

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

yes

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

depending on storage layer

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

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

User concepts

Access control

yes

granular access controls, API key management, content filters

yes

depending on the DBMS used for storage

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

AMD EPYC 4364P & 4564P @ DDR5-4800 / DDR5-5200 vs. Intel Xeon E-2488 Review
6 June 2024, Phoronix

TsFile: A Standard Format for IoT Time Series Data
27 February 2024, The New Stack

Linux 6.5 With AMD P-State EPP Default Brings Performance & Power Efficiency Benefits For Ryzen Servers
21 September 2023, Phoronix

Apache Promotes IoT Database Project
25 September 2020, Datanami

AMD EPYC 8324P / 8324PN Siena 32-Core Siena Linux Server Performance Review
10 October 2023, Phoronix

provided by Google News

Patrick Martin Sells 1531 Shares of Coveo Solutions Inc (TSE:CVO.TO) Stock
16 June 2024, Defense World

Is It Time To Consider Buying Coveo Solutions Inc. (TSE:CVO)?
6 June 2024, Yahoo Finance

Coveo Debuts GenAI Tools on Genesys Cloud and AppFoundry
17 May 2024, CX Today

Coveo Solutions Reports Strong Fiscal 2024 Results - TipRanks.com
3 June 2024, TipRanks

Coveo's 2024 Commerce Industry Report Finds More Than 70% of Consumers are Expecting Generative AI to ...
6 June 2024, PR Newswire

provided by Google News

Trinity
30 October 2010, Microsoft

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

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

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

provided by Google News

Share this page