DBMS > Cachelot.io vs. Cubrid vs. Lovefield vs. RDF4J vs. Snowflake

System Properties Comparison Cachelot.io vs. Cubrid vs. Lovefield vs. RDF4J vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

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

Embeddable relational database for web apps written in pure JavaScript

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Primary database model

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

cachelot.io

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

google.github.io/lovefield

rdf4j.org

www.snowflake.com

Technical documentation

cubrid.org/manuals

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

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

Developer

CUBRID Corporation, CUBRID Foundation

Google

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

Initial release

2015

2008

2014

2004

2014

Current release

11.0, January 2021

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

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

JavaScript

Java

Server operating systems

FreeBSD
Linux
OS X

Linux
Windows

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

tested with Chrome, Firefox, IE, Safari

Linux
OS X
Unix
Windows

hosted

Data scheme

schema-free

yes

RDF Schemas

yes

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

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

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

Memcached protocol

ADO.NET
JDBC
ODBC
OLE DB

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

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

JavaScript

Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes

user defined functions

Triggers

yes

Using read-only observers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

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

in-memory storage is supported as well

yes

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

fine grained access rights according to SQL-standard

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.