DBMS > Amazon Redshift vs. Apache Druid vs. Google Cloud Datastore vs. jBASE

System Properties Comparison Amazon Redshift vs. Apache Druid vs. Google Cloud Datastore vs. jBASE

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

A robust multi-value DBMS comprising development tools and middleware

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Document store

Multivalue DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Website

aws.amazon.com/redshift

druid.apache.org

cloud.google.com/datastore

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

Technical documentation

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

cloud.google.com/datastore/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

Google

Rocket Software (formerly Zumasys)

Initial release

2012

2008

1991

Current release

29.0.1, April 2024

5.7

License

Commercial or Open Source

commercial

Open Source

Apache license v2

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

Server operating systems

hosted

Linux
OS X
Unix

hosted

AIX
Linux
Windows

Data scheme

yes

schema-less columns are supported

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

optional

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL for querying

SQL-like query language (GQL)

Embedded SQL for jBASE in BASIC

APIs and other access methods

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

.Net
Basic
Jabbascript
Java

Server-side scripts

Stored procedures

user defined functions

in Python

using Google App Engine

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

Multi-source replication using Paxos

yes

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.

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

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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

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.