DBMS > PlanetScale vs. searchxml vs. Snowflake vs. SwayDB vs. Yanza

System Properties Comparison PlanetScale vs. searchxml vs. Snowflake vs. SwayDB vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

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

DBMS for structured and unstructured content wrapped with an application server

Cloud-based data warehousing service for structured and semi-structured data

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Native XML DBMS
Search engine

Relational DBMS

Key-value store

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

planetscale.com

www.searchxml.net/category/products

www.snowflake.com

swaydb.simer.au

yanza.com

Technical documentation

planetscale.com/docs

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

Developer

PlanetScale

informationpartners gmbh

Snowflake Computing Inc.

Simer Plaha

Yanza

Initial release

2020

2015

2014

2018

2015

Current release

1.0

License

Commercial or Open Source

commercial

Open Source

GNU Affero GPL V3.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

C++

Scala

Server operating systems

Docker
Linux
macOS

Windows

hosted

Windows

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
MySQL protocol
ODBC

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

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

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

Java
Kotlin
Scala

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

on the application server

user defined functions

Triggers

yes

similar concept for controling cloud resources

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

sychronisation to multiple collections

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID at shard level

multiple readers, single writer

ACID

Atomic execution of operations

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

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Domain, group and role-based access control at the document level and for application services

Users with fine-grained authorization concept, user roles and pluggable authentication

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.