DBMS > AnzoGraph DB vs. Apache IoTDB vs. Sphinx vs. SQLite

System Properties Comparison AnzoGraph DB vs. Apache IoTDB vs. Sphinx 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

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Open source search engine for searching in data from different sources, e.g. relational databases

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	0.22
Rank	#302	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	1.31
Rank	#159	Overall
	#14	Time Series DBMS

Score	5.97
Rank	#56	Overall
	#5	Search engines

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

cambridgesemantics.com/anzograph

iotdb.apache.org

sphinxsearch.com

www.sqlite.org

Technical documentation

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

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

sphinxsearch.com/docs

www.sqlite.org/docs.html

Developer

Cambridge Semantics

Apache Software Foundation

Sphinx Technologies Inc.

Dwayne Richard Hipp

Initial release

2018

2001

2000

Current release

2.3, January 2021

1.1.0, April 2023

3.5.1, February 2023

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache Version 2.0

Open Source

GPL version 2, commercial licence 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

All OS with a Java VM (>= 1.8)

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Data scheme

Schema-free and OWL/RDFS-schema support

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

full-text index on all search fields

yes

SQL

Support of SQL

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

SQL-like query language

SQL-like query language (SphinxQL)

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
Native API

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++
Java
Python

C
C#
C++
Go
Java
Python
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Eventual Consistency
Strong Consistency with Raft

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

The original contents of fields are not stored in the Sphinx index.

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 and roles

yes

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.