DBMS > AnzoGraph DB vs. Coveo vs. Fujitsu Enterprise Postgres vs. RocksDB

System Properties Comparison AnzoGraph DB vs. Coveo vs. Fujitsu Enterprise Postgres vs. RocksDB

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Enterprise-grade PostgreSQL-based DBMS with security enhancements such as Transparent Data Encryption and Data Masking, plus high-availability and performance improvement features.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Secondary database models

Document store
Spatial 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.11
Rank	#118	Overall
	#11	Search engines

Score	0.37
Rank	#278	Overall
	#128	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

cambridgesemantics.com/anzograph

www.coveo.com

www.postgresql.fastware.com

rocksdb.org

Technical documentation

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

docs.coveo.com

www.postgresql.fastware.com/product-manuals

github.com/facebook/rocksdb/wiki

Developer

Cambridge Semantics

Coveo

PostgreSQL Global Development Group, Fujitsu Australia Software Technology

Facebook, Inc.

Initial release

2018

2012

2013

Current release

2.3, January 2021

Fujitsu Enterprise Postgres 14, January 2022

9.2.1, May 2024

License

Commercial or Open Source

commercial

free trial version available

commercial

Open Source

BSD

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

hosted

Linux
Windows

Linux

Data scheme

Schema-free and OWL/RDFS-schema support

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

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

yes

APIs and other access methods

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

RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

C++ API
Java API

Supported programming languages

C++
Java
Python

C#
Java
JavaScript
Python

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

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

yes

partitioning by range, list and by hash

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

yes

Transaction concepts

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

ACID

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

granular access controls, API key management, content filters

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

100% compatible with community PostgreSQL
» more

Competitive advantages

Built-in TDE and Data Masking security. In-Memory Columnar Index, and a high speed...
» more

Typical application scenarios

Transactional payments applications, reporting and mixed workloads.
» more

Market metrics

Over 30 years experience in database technology. Over 20 years in Postgres development...
» more

Licensing and pricing models

Core based licensing
» more

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.