DBMS > JaguarDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. OpenEdge vs. Snowflake

System Properties Comparison JaguarDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. OpenEdge vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Performant, highly scalable DBMS for AI and IoT applications

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

Application development environment with integrated database management system

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Key-value store
Vector DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.jaguardb.com

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

www.progress.com/openedge

www.snowflake.com

Technical documentation

www.jaguardb.com/support.html

learn.microsoft.com/azure/cosmos-db

documentation.progress.com/output/ua/OpenEdge_latest

docs.snowflake.net/manuals/index.html

Developer

DataJaguar, Inc.

Microsoft

Progress Software Corporation

Snowflake Computing Inc.

Initial release

2015

2014

2012

1984

2014

Current release

3.3 July 2023

OpenEdge 12.2, March 2020

License

Commercial or Open Source

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

C++

the server part. Clients available in other languages

Server operating systems

Linux

hosted

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

JSON types

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

yes

close to SQL 92

yes

APIs and other access methods

JDBC
ODBC

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

RESTful HTTP API

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

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

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Progress proprietary ABL (Advanced Business Language)

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

JavaScript

yes

user defined functions

Triggers

JavaScript

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

horizontal partitioning

since Version 11.4

yes

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. Replication either local, cross-facility or geo-redundant.

Source-replica replication

yes

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

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

ACID

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

rights management via user accounts

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

Users and groups

Users with fine-grained authorization concept, user roles and pluggable authentication

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.