DBMS > Apache Drill vs. Google Cloud Datastore vs. JaguarDB vs. Lovefield

System Properties Comparison Apache Drill vs. Google Cloud Datastore vs. JaguarDB vs. Lovefield

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

Performant, highly scalable DBMS for AI and IoT applications

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Document store
Relational DBMS

Document store

Key-value store
Vector DBMS

Relational DBMS

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

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores
	#16	Vector DBMS

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Website

drill.apache.org

cloud.google.com/datastore

www.jaguardb.com

google.github.io/lovefield

Technical documentation

drill.apache.org/docs

cloud.google.com/datastore/docs

www.jaguardb.com/support.html

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Apache Software Foundation

Google

DataJaguar, Inc.

Google

Initial release

2012

2008

2015

2014

Current release

1.20.3, January 2023

3.3 July 2023

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GPL V3.0

Open Source

Apache 2.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++

the server part. Clients available in other languages

JavaScript

Server operating systems

Linux
OS X
Windows

hosted

Linux

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Data scheme

schema-free

yes

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)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

via JavaScript builder pattern

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

Using read-only observers

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

Multi-source replication

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.

Eventual 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

Durability

Support for making data persistent

Depending on the underlying data source

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

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

using MemoryDB

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)

rights management via user accounts

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
27 September 2019, Towards Data Science

MapR Advances Support for Flexible and High Performance Analytics on JSON and S3 Data with Apache Drill
30 January 2019, Business Wire

Apache Drill Adds New Data Formats
28 March 2022, iProgrammer

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

provided by Google News

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
13 September 2024, TechRadar

Google App Engine
26 April 2024, TechTarget

17 Top Cloud Storage Companies to Know
9 April 2024, Built In

provided by Google News

Share this page