DBMS > Fujitsu Enterprise Postgres vs. Microsoft Azure Cosmos DB vs. NSDb vs. VictoriaMetrics vs. Yanza

System Properties Comparison Fujitsu Enterprise Postgres vs. Microsoft Azure Cosmos DB vs. NSDb vs. VictoriaMetrics vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Globally distributed, horizontally scalable, multi-model database service

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	0.31
Rank	#285	Overall
	#129	Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

www.postgresql.fastware.com

azure.microsoft.com/services/cosmos-db

nsdb.io

victoriametrics.com

yanza.com

Technical documentation

www.postgresql.fastware.com/product-manuals

learn.microsoft.com/azure/cosmos-db

nsdb.io/Architecture

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

PostgreSQL Global Development Group, Fujitsu Australia Software Technology

Microsoft

VictoriaMetrics

Yanza

Initial release

2014

2017

2018

2015

Current release

Fujitsu Enterprise Postgres 14, January 2022

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Scala

Server operating systems

Linux
Windows

hosted

Linux
macOS

FreeBSD
Linux
macOS
OpenBSD

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

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

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

gRPC
HTTP REST
WebSocket

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

HTTP API

Supported programming languages

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

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

Java
Scala

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

JavaScript

Triggers

yes

JavaScript

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

partitioning by range, list and by hash

Sharding

Implicit feature of the cloud service

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

Synchronous replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

In-memory capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.