DBMS > BigObject vs. Galaxybase vs. Sequoiadb vs. Vitess

System Properties Comparison BigObject vs. Galaxybase vs. Sequoiadb vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Scalable, ACID-compliant native distributed parallel graph platform

NewSQL database with distributed OLTP and SQL

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Graph DBMS

Document store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	0.07
Rank	#377	Overall
	#40	Graph DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

Technical documentation

docs.bigobject.io

www.sequoiadb.com/en/index.php?m=Files&a=index

vitess.io/docs

Developer

BigObject, Inc.

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Sequoiadb Ltd.

The Linux Foundation, PlanetScale

Initial release

2015

2017

2013

Current release

Nov 20, November 2021

15.0.2, December 2022

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

Server: AGPL; Client: Apache V2

Open Source

Apache Version 2.0, commercial licenses available

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 and Java

C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux

Docker
Linux
macOS

Data scheme

yes

Strong typed schema

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

proprietary protocol using JSON

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Go
Java
Python

.Net
C++
Java
PHP
Python

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

Lua

user defined procedures and functions

JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Document is locked during a transaction

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

table locks or row locks depending on storage engine

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

Role-based access control

simple password-based access control

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.

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

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

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

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

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

provided by Google News

Share this page