DBMS > AgensGraph vs. Amazon Redshift vs. Google Cloud Datastore vs. JaguarDB

System Properties Comparison AgensGraph vs. Amazon Redshift vs. Google Cloud Datastore vs. JaguarDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Large scale data warehouse service for use with business intelligence tools

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Performant, highly scalable DBMS for AI and IoT applications

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Document store

Key-value store
Vector DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

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

Website

bitnine.net/agensgraph

aws.amazon.com/redshift

cloud.google.com/datastore

www.jaguardb.com

Technical documentation

bitnine.net/documentation

docs.aws.amazon.com/redshift

cloud.google.com/datastore/docs

www.jaguardb.com/support.html

Developer

Bitnine Global Inc.

Amazon (based on PostgreSQL)

Google

DataJaguar, Inc.

Initial release

2016

2012

2008

2015

Current release

2.1, December 2018

3.3 July 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

GPL V3.0

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
OS X
Windows

hosted

Linux

Data scheme

depending on used data model

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (GQL)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

Cypher Query Language
JDBC

JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

C
Java
JavaScript
Python

All languages supporting JDBC/ODBC

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

user defined functions

in Python

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication using Paxos

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

rights management via user accounts

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.