DBMS > Apache Drill vs. IBM Cloudant vs. Memgraph vs. SQLite

System Properties Comparison Apache Drill vs. IBM Cloudant vs. Memgraph vs. SQLite

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

Database as a Service offering based on Apache CouchDB

An open source graph database built for real-time streaming and compatible with Neo4j

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Document store

Graph 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	2.85
Rank	#95	Overall
	#18	Document stores

Score	2.91
Rank	#94	Overall
	#7	Graph DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

drill.apache.org

www.ibm.com/products/cloudant

memgraph.com

www.sqlite.org

Technical documentation

drill.apache.org/docs

cloud.ibm.com/docs/Cloudant

memgraph.com/docs

www.sqlite.org/docs.html

Social network pages

Developer

Apache Software Foundation

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Memgraph Ltd

Dwayne Richard Hipp

Initial release

2012

2010

2017

2000

Current release

1.20.3, January 2023

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

BSL 1.1; commercial license for enterprise edition available

Open Source

Public Domain

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

Erlang

C and C++

Server operating systems

Linux
OS X
Windows

hosted

Linux

server-less

Data scheme

schema-free

schema-free and schema-optional

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

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

Bolt protocol
Cypher query language

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C++
Elixir
Go
Haskell
Java
JavaScript
PHP
Python
Ruby
Scala

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

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

dynamic graph partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication using RAFT

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

yes

Transaction concepts

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

atomic operations within a document possible

ACID

with snapshot isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

Durability

Support for making data persistent

Depending on the underlying data source

yes

with periodic snapshot and write-ahead logging (WAL) of changes

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

User concepts

Access control

Depending on the underlying data source

Access rights for users can be defined per database

Users, roles and permissions

More information provided by the system vendor

Specific characteristics

Memgraph directly connects to your streaming infrastructure so you and your team...
» more

Competitive advantages

Business Source License ensures a future for the Memgraph community MAGE algorithm...
» more

Typical application scenarios

Graph algorithms in bioinformatics Social network analysis Cryptocurrency network...
» more

Licensing and pricing models

You can check out our pricing model and licenses on the company website .
» more

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.