DBMS > Cubrid vs. DataFS vs. Lovefield vs. OrigoDB

System Properties Comparison Cubrid vs. DataFS vs. Lovefield vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

Embeddable relational database for web apps written in pure JavaScript

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Object oriented DBMS

Relational DBMS

Document store
Object oriented DBMS

Secondary database models

Graph DBMS

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	0.09
Rank	#360	Overall
	#17	Object oriented DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

cubrid.com (korean)
cubrid.org (english)

newdatabase.com

google.github.io/lovefield

origodb.com

Technical documentation

cubrid.org/manuals

dev.mobiland.com/Overview.xsp

github.com/google/lovefield/blob/master/docs/spec_index.md

origodb.com/docs

Developer

CUBRID Corporation, CUBRID Foundation

Mobiland AG

Google

Robert Friberg et al

Initial release

2008

2018

2014

2009

under the name LiveDB

Current release

11.0, January 2021

1.1.263, October 2022

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

Open Source

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, C++, Java

JavaScript

Server operating systems

Linux
Windows

Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
Windows

Data scheme

yes

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

.NET Client API
Proprietary client DLL
WinRT client

.NET Client API
HTTP API
LINQ

Supported programming languages

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.Net
C
C#
C++
VB.Net

JavaScript

.Net

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Triggers

yes

no, except callback-events from server when changes happened

Using read-only observers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Proprietary Sharding system

none

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

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

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

Write ahead log

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Windows-Profile

Role based authorization

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.

Share this page