DBMS > Apache Drill vs. Google Cloud Datastore vs. Sequoiadb vs. Transbase

System Properties Comparison Apache Drill vs. Google Cloud Datastore vs. Sequoiadb vs. Transbase

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

NewSQL database with distributed OLTP and SQL

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Relational DBMS

Document store

Document store
Relational DBMS

Relational DBMS

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	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

drill.apache.org

cloud.google.com/datastore

www.sequoiadb.com

www.transaction.de/en/products/transbase.html

Technical documentation

drill.apache.org/docs

cloud.google.com/datastore/docs

www.sequoiadb.com/en/index.php?m=Files&a=index

www.transaction.de/en/products/transbase/features.html

Developer

Apache Software Foundation

Google

Sequoiadb Ltd.

Transaction Software GmbH

Initial release

2012

2008

2013

1987

Current release

1.20.3, January 2023

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Server: AGPL; Client: Apache V2

commercial

free development license

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

C and C++

Server operating systems

Linux
OS X
Windows

hosted

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

oid, date, timestamp, binary, regex

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language (GQL)

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

proprietary protocol using JSON

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C++

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

.Net
C++
Java
PHP
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

JavaScript

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica 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

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.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Document is locked during a transaction

yes

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

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)

simple password-based access control

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

MapR to Speak on Stream Processing Systems, Apache Spark and Drill at Industry Events in January
27 May 2024, Yahoo Movies UK

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Apache Drill vs. Apache Spark — Which SQL query engine is better for you?
23 September 2019, Towards Data Science

Apache Drill Poised to Crack Tough Data Challenges
19 May 2015, Datanami

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

provided by Google News

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
21 May 2024, TechRadar

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

provided by Google News

Share this page