DBMS > Apache Impala vs. Drizzle vs. Google Cloud Datastore vs. LeanXcale

System Properties Comparison Apache Impala vs. Drizzle vs. Google Cloud Datastore vs. LeanXcale

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Analytic DBMS for Hadoop

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Primary database model

Relational DBMS

Document store

Key-value store
Relational DBMS

Secondary database models

Document store

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Website

impala.apache.org

cloud.google.com/datastore

www.leanxcale.com

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/datastore/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Drizzle project, originally started by Brian Aker

Google

LeanXcale

Initial release

2013

2008

2015

Current release

4.1.0, June 2022

7.2.4, September 2012

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GNU GPL

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

C++

Server operating systems

Linux

FreeBSD
Linux
OS X

hosted

Data scheme

yes

schema-free

yes

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-like DML and DDL statements

yes

with proprietary extensions

SQL-like query language (GQL)

yes

through Apache Derby

APIs and other access methods

JDBC
ODBC

JDBC

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

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

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

C
Java
Scala

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

using Google App Engine

Triggers

hooks for callbacks inside the server can be used.

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.

Related products and services

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

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Apache Impala 4 Supports Operator Multi-Threading
29 July 2021, iProgrammer

Apache Impala becomes Top-Level Project
28 November 2017, SDTimes.com

StarRocks Brings Speedy OLAP Database to the Cloud
14 July 2022, Datanami

Apache Doris just 'graduated': Why care about this SQL data warehouse
24 June 2022, InfoWorld

Hudi: Uber Engineering’s Incremental Processing Framework on Apache Hadoop
12 March 2017, Uber

provided by Google News

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

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

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

Best cloud storage of 2024
29 April 2024, TechRadar

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

provided by Google News

Share this page