DBMS > GeoSpock vs. JaguarDB vs. Microsoft Azure AI Search vs. Microsoft Azure Cosmos DB

System Properties Comparison GeoSpock vs. JaguarDB vs. Microsoft Azure AI Search 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

Spatial and temporal data processing engine for extreme data scale

Performant, highly scalable DBMS for AI and IoT applications

Search-as-a-service for web and mobile app development

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Time Series DBMS

Vector DBMS

Spatial DBMS

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

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	5.52
Rank	#59	Overall
	#6	Search engines

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

Website

geospock.com

www.jaguardb.com

azure.microsoft.com/en-us/services/search

azure.microsoft.com/services/cosmos-db

Technical documentation

www.jaguardb.com/support.html

learn.microsoft.com/en-us/azure/search

learn.microsoft.com/azure/cosmos-db

Developer

GeoSpock

DataJaguar, Inc.

Microsoft

Initial release

2015

2014

Current release

2.0, September 2019

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.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

C++

the server part. Clients available in other languages

Server operating systems

hosted

Linux

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

ANSI SQL for query only (using Presto)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

APIs and other access methods

JDBC

JDBC
ODBC

RESTful HTTP API

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

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Python

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

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

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

Eventual Consistency

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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

In-memory capabilities

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

User concepts

Access control

Access rights for users can be defined per table

rights management via user accounts

yes

using Azure authentication

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.