DBMS > MySQL vs. Pinecone vs. Realm vs. VoltDB vs. Yanza

System Properties Comparison MySQL vs. Pinecone vs. Realm vs. VoltDB vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

Widely used open source RDBMS

A managed, cloud-native vector database

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	3.16
Rank	#95	Overall
	#2	Vector DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

yanza.com

Technical documentation

dev.mysql.com/doc

docs.pinecone.io/docs/overview

realm.io/docs

docs.voltdb.com

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Pinecone Systems, Inc

Realm, acquired by MongoDB in May 2019

VoltDB Inc.

Yanza

Initial release

1995

2019

2014

2010

2015

Current release

8.4.0, April 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Java, C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Android
Backend: server-less
iOS
Windows

Linux
OS X

for development

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

String, Number, Boolean

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

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Java API
JDBC
RESTful HTTP/JSON API

HTTP API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Python

.Net
Java

with Android only
Objective-C
React Native
Swift

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

proprietary syntax

runs within the applications so server-side scripts are unnecessary

Java

Triggers

yes

Change Listeners

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

yes

In-memory capabilities

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

yes

In-Memory realm

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

yes

Users and roles with access to stored procedures

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.