DBMS > etcd vs. Interbase vs. MySQL vs. Solr vs. Yanza

System Properties Comparison etcd vs. Interbase vs. MySQL vs. Solr vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

A distributed reliable key-value store

Light-weight proven RDBMS

originally from Borland

Widely used open source RDBMS

A widely used distributed, scalable search engine based on Apache Lucene

Time Series DBMS for IoT Applications

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Search engine

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	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

etcd.io
github.com/etcd-io/etcd

www.embarcadero.com/products/interbase

www.mysql.com

solr.apache.org

yanza.com

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.embarcadero.com/products/interbase

dev.mysql.com/doc

solr.apache.org/resources.html

Developer

Embarcadero

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Yanza

Initial release

1984

1995

2006

2015

Current release

3.4, August 2019

InterBase 2020, December 2019

8.4.0, April 2024

9.6.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2

commercial

free version available

Cloud-based only

Only available as a cloud service

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

Server operating systems

FreeBSD
Linux
Windows

experimental

Android
iOS
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Windows

Data scheme

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

schema-free

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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.

export as XML data possible

yes

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

Solr Parallel SQL Interface

APIs and other access methods

gRPC
JSON over HTTP

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
RESTful HTTP/JSON API

HTTP API

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

yes

proprietary syntax

Java plugins

Triggers

yes, watching key changes

yes

User configurable commands triggered on index changes

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Interbase Change Views

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

not for MyISAM storage engine

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

yes

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.