DBMS > Amazon Redshift vs. atoti vs. Google Cloud Datastore vs. Rockset vs. searchxml

System Properties Comparison Amazon Redshift vs. atoti vs. Google Cloud Datastore vs. Rockset vs. searchxml

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS

Object oriented DBMS

Document store

Native XML DBMS
Search engine

Secondary database models

Relational DBMS
Search engine

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.61
Rank	#243	Overall
	#10	Object oriented DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

aws.amazon.com/redshift

atoti.io

cloud.google.com/datastore

rockset.com

www.searchxml.net/category/products

Technical documentation

docs.aws.amazon.com/redshift

docs.atoti.io

cloud.google.com/datastore/docs

docs.rockset.com

www.searchxml.net/support/handouts

Developer

Amazon (based on PostgreSQL)

ActiveViam

Google

Rockset

informationpartners gmbh

Initial release

2012

2008

2019

2015

Current release

1.0

License

Commercial or Open Source

commercial

free versions available

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

C++

Server operating systems

hosted

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

dynamic typing

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.

ingestion from XML files supported

yes

Secondary indexes

restricted

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

Multidimensional Expressions (MDX)

SQL-like query language (GQL)

Read-only SQL queries, including JOINs

APIs and other access methods

JDBC
ODBC

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

HTTP REST

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

All languages supporting JDBC/ODBC

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

Go
Java
JavaScript (Node.js)
Python

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

in Python

Python

using Google App Engine

yes

on the application server

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

Sharding

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

sychronisation to multiple collections

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

Immediate 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

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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)

Access rights for users and organizations can be defined via Rockset console

Domain, group and role-based access control at the document level and for application services

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.