DBMS > Apache Impala vs. BigObject vs. Cachelot.io vs. EJDB vs. MySQL

System Properties Comparison Apache Impala vs. BigObject vs. Cachelot.io vs. EJDB vs. MySQL

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Analytic DBMS for real-time computations and queries

In-memory caching system

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Widely used open source RDBMS

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store

Document store

Relational DBMS

Key/Value like access via memcached API

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	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	0.04
Rank	#388	Overall
	#62	Key-value stores

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

impala.apache.org

bigobject.io

cachelot.io

github.com/Softmotions/ejdb

www.mysql.com

Technical documentation

impala.apache.org/impala-docs.html

docs.bigobject.io

github.com/Softmotions/ejdb/blob/master/README.md

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

BigObject, Inc.

Softmotions

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2015

2012

1995

Current release

4.1.0, June 2022

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

free community edition available

Open Source

Simplified BSD License

Open Source

GPLv2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

FreeBSD
Linux
OS X

server-less

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

Memcached protocol

in-process shared library

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

Lua

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Multi-source replication
Source-replica replication

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

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

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.