DBMS > Apache Impala vs. Infobright vs. PlanetScale vs. XTDB

System Properties Comparison Apache Impala vs. Infobright vs. PlanetScale vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Scalable, distributed, serverless MySQL database platform built on top of Vitess

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Document store

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

impala.apache.org

ignitetech.com/softwarelibrary/infobrightdb

planetscale.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

impala.apache.org/impala-docs.html

planetscale.com/docs

www.xtdb.com/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Ignite Technologies Inc.; formerly InfoBright Inc.

PlanetScale

Juxt Ltd.

Initial release

2013

2005

2020

2019

Current release

4.1.0, June 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Open Source

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

Clojure

Server operating systems

Linux

Linux
Windows

Docker
Linux
macOS

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Users with fine-grained authorization concept

no user groups or roles

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 Impala becomes Top-Level Project
28 November 2017, SDTimes.com

Cloudera Bringing Impala to AWS Cloud
28 November 2017, 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

Updates & Upserts in Hadoop Ecosystem with Apache Kudu
27 October 2017, KDnuggets

provided by Google News

PlanetScale ends free tier bid, sheds staff in profitability bid
11 March 2024, The Register

PlanetScale Ranked Number 188 Fastest-Growing Company in North America on the 2023 Deloitte Technology Fast ...
8 November 2023, businesswire.com

PlanetScale forks MySQL to add vector support
3 October 2023, TechCrunch

PlanetScale Named to Fortune 2023 Best Small Workplaces
31 August 2023, businesswire.com

How to Migrate to PlanetScale's Serverless Database
14 October 2021, The New Stack

provided by Google News

Share this page