DBMS > Coveo vs. GeoSpock vs. IRONdb vs. JSqlDb vs. Microsoft Azure Cosmos DB

System Properties Comparison Coveo vs. GeoSpock vs. IRONdb vs. JSqlDb vs. Microsoft Azure Cosmos DB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

JavaScript Query Language Database, stores JavaScript objects and primitives

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Search engine

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Time Series DBMS

Spatial DBMS

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

www.coveo.com

geospock.com

www.circonus.com/solutions/time-series-database/

jsqldb.org (offline)

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.coveo.com

docs.circonus.com/irondb/category/getting-started

learn.microsoft.com/azure/cosmos-db

Developer

Coveo

GeoSpock

Circonus LLC.

Konrad von Backstrom

Microsoft

Initial release

2012

2017

2018

2014

Current release

2.0, September 2019

V0.10.20, January 2018

0.8, December 2018

License

Commercial or Open Source

commercial

Open Source

commercial

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, Javascript

C and C++

Server operating systems

hosted

Linux

Linux
macOS
Windows

hosted

Data scheme

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

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

JSON 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.

Secondary indexes

yes

temporal, categorical

yes

All properties auto-indexed by default

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

APIs and other access methods

RESTful HTTP API

JDBC

HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

C#
Java
JavaScript
Python

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

JavaScript

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes, in Lua

functions in JavaScript

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

Automatic sharding

Automatic, metric affinity per node

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

none

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using RocksDB

yes

In-memory capabilities

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

User concepts

Access control

granular access controls, API key management, content filters

Access rights for users can be defined per table

Access rights can be defined down to the item level

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.