DBMS > OceanBase vs. Vitess vs. Yaacomo

System Properties Comparison OceanBase vs. Vitess vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

A distributed, high available RDBMS compatible with Oracle and MySQL

Scalable, distributed, cloud-native DBMS, extending MySQL

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Secondary database models

Document store
Wide column store

Document store
Spatial DBMS

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

Score	1.66
Rank	#147	Overall
	#68	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

en.oceanbase.com

vitess.io

yaacomo.com

Technical documentation

en.oceanbase.com/docs/oceanbase-database

vitess.io/docs

Developer

OceanBase

previously Alibaba and Ant Group

The Linux Foundation, PlanetScale

Q2WEB GmbH

Initial release

2010

2013

2009

Current release

4.3.0, April 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Commercial license available

Open Source

Apache Version 2.0, commercial licenses available

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

Linux

Docker
Linux
macOS

Android
Linux
Windows

Data scheme

yes

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Proprietary native API
Table API

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

Supported programming languages

Ada

in MySQL-compatible model
C

in Oracle- and MySQL- compatible models
C++

in Oracle- and MySQL- compatible models
D

in MySQL-compatible model
Delphi

in MySQL-compatible model
Eiffel

in MySQL-compatible model
Erlang

in MySQL-compatible model
Haskell

in MySQL-compatible model
Java

in Oracle- and MySQL- compatible models
JavaScript (Node.js)

in MySQL-compatible model
Objective-C

in MySQL-compatible model
OCaml

in MySQL-compatible model
Perl

in MySQL-compatible model
PHP

in MySQL-compatible model
Python

in MySQL-compatible model
Ruby

in MySQL-compatible model
Scheme

in MySQL-compatible model
Tcl

in MySQL-compatible model

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

Server-side scripts

Stored procedures

PL/SQL in oracle-compatible mode, MySQL Stored Procedure in mysql-compatible mode

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by hash, key, range, range columns, list, and list columns)

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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

yes

Transaction concepts

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

ACID

ACID at shard level

ACID

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

Access rights for users, groups and roles according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

OceanBase Inks Agreement with NTU Singapore in Database Optimization and Green Computing Advancements
31 January 2024, PR Newswire

Ant Group Will Cut Foreign Investors Out of Fast-Growing Database Business
22 August 2023, The Information

How Southeast Asia's Leading e-Wallets Saved Up to 40% in Database Costs - Fintech Singapore
25 March 2024, Fintech News Singapore

Haidilao’s 6-step recipe for successful digital transformation with OceanBase
4 August 2023, Tech in Asia

Alibaba's OceanBase distributed database aims at markets outside China
16 August 2022, InfoWorld

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

provided by Google News

Share this page