DBMS > chDB vs. GeoSpock vs. Lovefield vs. Microsoft Azure Cosmos DB

System Properties Comparison chDB vs. GeoSpock vs. Lovefield vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

An embedded SQL OLAP Engine powered by ClickHouse

Spatial and temporal data processing engine for extreme data scale

Embeddable relational database for web apps written in pure JavaScript

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational 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	0.05
Rank	#358	Overall
	#152	Relational DBMS

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

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

Website

github.com/chdb-io/chdb

geospock.com

google.github.io/lovefield

azure.microsoft.com/services/cosmos-db

Technical documentation

doc.chdb.io

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

learn.microsoft.com/azure/cosmos-db

Developer

GeoSpock

Google

Microsoft

Initial release

2023

2014

Current release

2.0, September 2019

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

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

JavaScript

Server operating systems

server-less

hosted

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

tested with Chrome, Firefox, IE, Safari

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

temporal, categorical

yes

All properties auto-indexed by default

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

ANSI SQL for query only (using Presto)

SQL-like query language

via JavaScript builder pattern

SQL-like query language

APIs and other access methods

JDBC

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

Supported programming languages

Bun
C
C++
Go
JavaScript (Node.js)
Python
Rust

JavaScript

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

Server-side scripts

Stored procedures

JavaScript

Triggers

Using read-only observers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

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

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

ACID

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

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.

yes

using MemoryDB

User concepts

Access control

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.