DBMS > AnzoGraph DB vs. BoltDB vs. Microsoft Azure Cosmos DB vs. Typesense

System Properties Comparison AnzoGraph DB vs. BoltDB vs. Microsoft Azure Cosmos DB vs. Typesense

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 embedded key-value store for Go.

Globally distributed, horizontally scalable, multi-model database service

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

Graph DBMS
RDF store

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Search engine

Secondary database models

Spatial 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	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.79
Rank	#210	Overall
	#14	Search engines

Website

cambridgesemantics.com/anzograph

github.com/boltdb/bolt

azure.microsoft.com/services/cosmos-db

typesense.org

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

typesense.org/docs

Developer

Cambridge Semantics

Microsoft

Initial release

2018

2013

2014

2015

Current release

2.3, January 2021

License

Commercial or Open Source

commercial

free trial version available

Open Source

MIT License

commercial

Open Source

GPL V3

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

C++

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

Schema-free and OWL/RDFS-schema support

schema-free

pre-defined schema optional

Typing

predefined data types such as float or date

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

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

SQL-like query language

APIs and other access methods

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

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

Supported programming languages

C++
Java
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

user defined functions and aggregates

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

none

yes

Implicit feature of the cloud service

Multi-source replication using RAFT

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

not needed in graphs

Transaction concepts

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

ACID

yes

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

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 rights can be defined down to the item level

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.