DBMS > AnzoGraph DB vs. Atos Standard Common Repository vs. GeoMesa vs. Lovefield

System Properties Comparison AnzoGraph DB vs. Atos Standard Common Repository vs. GeoMesa vs. Lovefield

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

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Graph DBMS
RDF store

Document store
Key-value store

Spatial 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	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Website

cambridgesemantics.com/anzograph

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

www.geomesa.org

google.github.io/lovefield

Technical documentation

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

www.geomesa.org/documentation/stable/user/index.html

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Cambridge Semantics

Atos Convergence Creators

CCRi and others

Google

Initial release

2018

2016

2014

Current release

2.3, January 2021

1703

5.0.0, May 2024

2.1.12, February 2017

License

Commercial or Open Source

commercial

free trial version available

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0

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

Scala

JavaScript

Server operating systems

Linux

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Data scheme

Schema-free and OWL/RDFS-schema support

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

optional

yes

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.

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

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

LDAP

Supported programming languages

C++
Java
Python

All languages with LDAP bindings

JavaScript

Server-side scripts

Stored procedures

user defined functions and aggregates

Triggers

yes

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

cell division

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

yes

depending on storage layer

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

Immediate Consistency or Eventual Consistency depending on configuration

depending on storage layer

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

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

In-memory capabilities

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

yes

depending on storage layer

yes

using MemoryDB

User concepts

Access control

Access rights for users and roles

LDAP bind authentication

yes

depending on the DBMS used for storage

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

AnzoGraph review: A graph database for deep analytics
15 April 2019, InfoWorld

AnzoGraph: A W3C Standards-Based Graph Database | by Jo Stichbury
8 February 2019, Towards Data Science

Cambridge Semantics Fits AnzoGraph DB with More Speed, Free Access
23 January 2020, Solutions Review

Back to the future: Does graph database success hang on query language?
5 March 2018, ZDNet

Comparing Graph Databases II. Part 2: ArangoDB, OrientDB, and… | by Sam Bell
20 September 2019, Towards Data Science

provided by Google News

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Kagiso interactive shares: all eyes on android at google I/O
11 May 2015, WhaTech

provided by Google News

Share this page