DBMS > AnzoGraph DB vs. Apache Phoenix vs. Atos Standard Common Repository vs. SQLite

System Properties Comparison AnzoGraph DB vs. Apache Phoenix vs. Atos Standard Common Repository vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

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

A scale-out RDBMS with evolutionary schema built on Apache HBase

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
RDF store

Relational DBMS

Document store
Key-value store

Relational DBMS

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

Score	0.23
Rank	#307	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

cambridgesemantics.com/anzograph

phoenix.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.sqlite.org

Technical documentation

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

phoenix.apache.org

www.sqlite.org/docs.html

Developer

Cambridge Semantics

Apache Software Foundation

Atos Convergence Creators

Dwayne Richard Hipp

Initial release

2018

2014

2016

2000

Current release

2.3, January 2021

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

1703

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache Version 2.0

commercial

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
Unix
Windows

Linux

server-less

Data scheme

Schema-free and OWL/RDFS-schema support

yes

late-bound, schema-on-read capabilities

Schema and schema-less with LDAP views

yes

dynamic column types

Typing

predefined data types such as float or date

yes

optional

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.

yes

Secondary indexes

yes

SQL

Support of SQL

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

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

LDAP

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++
Java
Python

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

All languages with LDAP bindings

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

cell division

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate Consistency or Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

not needed in graphs

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

LDAP bind authentication

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.