DBMS > Apache Drill vs. Google Cloud Datastore vs. RocksDB vs. SwayDB

System Properties Comparison Apache Drill vs. Google Cloud Datastore vs. RocksDB vs. SwayDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store
Relational DBMS

Document store

Key-value store

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

drill.apache.org

cloud.google.com/datastore

rocksdb.org

swaydb.simer.au

Technical documentation

drill.apache.org/docs

cloud.google.com/datastore/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Google

Facebook, Inc.

Simer Plaha

Initial release

2012

2008

2013

2018

Current release

1.20.3, January 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

BSD

Open Source

GNU Affero 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++

Scala

Server operating systems

Linux
OS X
Windows

hosted

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language (GQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

C++ API
Java API

Supported programming languages

C++

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

C
C++
Go
Java
Perl
Python
Ruby

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

none

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

none

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.

Immediate Consistency

Foreign keys

Referential integrity

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

yes

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

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

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.