DBMS > Apache Drill vs. Google BigQuery vs. Graph Engine vs. Newts vs. SAP SQL Anywhere

System Properties Comparison Apache Drill vs. Google BigQuery vs. Graph Engine vs. Newts vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

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

Large scale data warehouse service with append-only tables

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Time Series DBMS based on Cassandra

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Document store
Relational DBMS

Relational DBMS

Graph DBMS
Key-value store

Time Series 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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

drill.apache.org

cloud.google.com/bigquery

www.graphengine.io

opennms.github.io/newts

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

drill.apache.org/docs

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

github.com/OpenNMS/newts/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Apache Software Foundation

Google

Microsoft

OpenNMS Group

SAP

formerly Sybase

Initial release

2012

2010

2014

1992

Current release

1.20.3, January 2023

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

MIT License

Open Source

Apache 2.0

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

.NET and C

Java

Server operating systems

Linux
OS X
Windows

hosted

.NET

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

RESTful HTTP API

HTTP REST
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C++

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

Java

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.