DBMS > AnzoGraph DB vs. Apache Drill vs. KairosDB vs. SQLite

System Properties Comparison AnzoGraph DB vs. Apache Drill vs. KairosDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

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

Distributed Time Series DBMS based on Cassandra or H2

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
RDF store

Document store
Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	0.29
Rank	#303	Overall
	#25	Graph DBMS
	#14	RDF stores

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

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

cambridgesemantics.com/anzograph

drill.apache.org

github.com/kairosdb/kairosdb

www.sqlite.org

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

drill.apache.org/docs

kairosdb.github.io

www.sqlite.org/docs.html

Developer

Cambridge Semantics

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2018

2012

2013

2000

Current release

2.3, January 2021

1.20.3, January 2023

1.2.2, November 2018

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache Version 2

Open Source

Apache 2.0

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

Server operating systems

Linux

Linux
OS X
Windows

server-less

Data scheme

Schema-free and OWL/RDFS-schema support

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

SPARQL and SPARQL* as primary query language. Cypher preview.

SQL SELECT statement is SQL:2003 compliant

yes

SQL-92 is not fully supported

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

JDBC
ODBC
RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++
Java
Python

C++

Java
JavaScript

Node.js
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 and aggregates

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

selectable replication factor

based on Cassandra

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

none

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

not needed in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

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

yes

Depending on the underlying data source

yes

User concepts

Access control

Access rights for users and roles

Depending on the underlying data source

simple password-based access control

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.