DBMS > Apache Drill vs. Google Cloud Datastore vs. H2 vs. JSqlDb

System Properties Comparison Apache Drill vs. Google Cloud Datastore vs. H2 vs. JSqlDb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

JavaScript Query Language Database, stores JavaScript objects and primitives

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

Document store
Object oriented DBMS

Secondary database models

Spatial 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	8.13
Rank	#49	Overall
	#31	Relational DBMS

Website

drill.apache.org

cloud.google.com/datastore

www.h2database.com

jsqldb.org (offline)

Technical documentation

drill.apache.org/docs

cloud.google.com/datastore/docs

www.h2database.com/html/main.html

Developer

Apache Software Foundation

Google

Thomas Mueller

Konrad von Backstrom

Initial release

2012

2008

2005

2018

Current release

1.20.3, January 2023

2.2.220, July 2023

0.8, December 2018

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

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

Linux
OS X
Windows

hosted

All OS with a Java VM

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

JDBC
ODBC

Supported programming languages

C++

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

Java

JavaScript

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

Java Stored Procedures and User-Defined Functions

functions in JavaScript

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

With clustering: 2 database servers on different computers operate on identical copies of a database

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

yes

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

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

Depending on the underlying data source

yes

using RocksDB

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)

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

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

Analyse Kafka messages with SQL queries using Apache Drill
23 September 2019, Towards Data Science

Apache Drill improves big data SQL query engine
31 August 2021, TechTarget

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

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

provided by Google News

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

Best cloud storage of 2024
29 April 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

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

Share this page