DBMS > Apache Drill vs. atoti vs. Ehcache vs. Sadas Engine vs. SQLite

System Properties Comparison Apache Drill vs. atoti vs. Ehcache vs. Sadas Engine vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

A widely adopted Java cache with tiered storage options

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Object oriented DBMS

Key-value store

Relational DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.61
Rank	#243	Overall
	#10	Object oriented DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

drill.apache.org/docs

docs.atoti.io

www.ehcache.org/documentation

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

www.sqlite.org/docs.html

Developer

Apache Software Foundation

ActiveViam

Terracotta Inc, owned by Software AG

SADAS s.r.l.

Dwayne Richard Hipp

Initial release

2012

2009

2006

2000

Current release

1.20.3, January 2023

3.10.0, March 2022

8.0

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

free versions available

Open Source

Apache Version 2; commercial licenses available

commercial

free trial version available

Open Source

Public Domain

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.

Implementation language

Java

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

AIX
Linux
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Multidimensional Expressions (MDX)

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JCache

JDBC
ODBC
Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++

Java

.Net
C
C#
C++
Groovy
Java
PHP
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

Python

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

Sharding

by using Terracotta Server

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

Durability

Support for making data persistent

Depending on the underlying data source

yes

using a tiered cache-storage approach

yes

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

managed by 'Learn by Usage'

yes

User concepts

Access control

Depending on the underlying data source

Access rights for users, groups and roles 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.