DBMS > Cubrid vs. dBASE vs. LokiJS vs. Snowflake vs. Speedb

System Properties Comparison Cubrid vs. dBASE vs. LokiJS vs. Snowflake vs. Speedb

Editorial information provided by DB-Engines

Name

Description

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

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

In-memory JavaScript DBMS

Cloud-based data warehousing service for structured and semi-structured data

An embeddable, high performance key-value store optimized for write-intensive workloads, which can be used as a drop-in replacement for RocksDB

Primary database model

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

Score	0.97
Rank	#189	Overall
	#86	Relational DBMS

Score	9.16
Rank	#43	Overall
	#27	Relational DBMS

Score	0.44
Rank	#256	Overall
	#40	Document stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.20
Rank	#310	Overall
	#44	Key-value stores

Website

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

www.dbase.com

github.com/techfort/LokiJS

www.snowflake.com

www.speedb.io

Technical documentation

cubrid.org/manuals

www.dbase.com/support/knowledgebase

techfort.github.io/LokiJS

docs.snowflake.net/manuals/index.html

Developer

CUBRID Corporation, CUBRID Foundation

Asthon Tate

Snowflake Computing Inc.

Speedb

Initial release

2008

1979

2014

2020

Current release

11.0, January 2021

dBASE 2019, 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

commercial

Open Source

Apache Version 2.0; commercial license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C, C++, Java

JavaScript

C++

Server operating systems

Linux
Windows

DOS

dBase Classic
Windows

dBase Pro

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

hosted

Linux
Windows

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

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

via views

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

none

The IDE can access other DBMS or ODBC-sources.

JavaScript API

CLI Client
JDBC
ODBC

Supported programming languages

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

dBase proprietary IDE

JavaScript

JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

The IDE can access stored procedures in other database systems.

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

not for dBase internal data, but IDE does support transactions when accessing external DBMS

atomic operations within a single collection possible

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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

Access rights for users and roles

Users with fine-grained authorization concept, user roles and pluggable authentication

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.