DBMS > Oracle vs. PlanetScale vs. STSdb vs. Yanza

System Properties Comparison Oracle vs. PlanetScale vs. STSdb vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Widely used RDBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Key-value store

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Document store
Spatial DBMS

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

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

www.oracle.com/database

planetscale.com

github.com/STSSoft/STSdb4

yanza.com

Technical documentation

docs.oracle.com/en/database

planetscale.com/docs

Developer

Oracle

PlanetScale

STS Soft SC

Yanza

Initial release

1980

2020

2011

2015

Current release

23c, September 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

GPLv2, commercial license available

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

C and C++

Server operating systems

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Docker
Linux
macOS

Windows

Data scheme

yes

Schemaless in JSON and XML columns

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

with proprietary extensions

APIs and other access methods

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
MySQL protocol
ODBC

.NET Client API

HTTP API

Supported programming languages

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

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

C#
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

yes

proprietary syntax

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

isolation level can be parameterized

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.