DBMS > BigObject vs. SAP HANA vs. Sequoiadb vs. Vitess

System Properties Comparison BigObject vs. SAP HANA 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

In-memory, column based data store. Available as appliance or cloud service

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

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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	44.27
Rank	#23	Overall
	#16	Relational DBMS

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

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

bigobject.io

www.sap.com/products/hana.html

www.sequoiadb.com

vitess.io

Technical documentation

docs.bigobject.io

help.sap.com/hana

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

vitess.io/docs

Developer

BigObject, Inc.

SAP

Sequoiadb Ltd.

The Linux Foundation, PlanetScale

Initial release

2015

2010

2013

Current release

2.0 SPS07 (April 4, 2023), April 2023

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

also available as a cloud based 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

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Appliance or cloud-service

Linux

Docker
Linux
macOS

Data scheme

yes

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

yes

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

JDBC
ODBC

proprietary protocol using JSON

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.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

SQLScript, R

JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

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

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

yes

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.