DBMS > Cubrid vs. Elasticsearch vs. SQLite vs. TimesTen vs. Yanza

System Properties Comparison Cubrid vs. Elasticsearch vs. SQLite vs. TimesTen vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Widely used embeddable, in-process RDBMS

In-Memory RDBMS compatible to Oracle

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

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

www.elastic.co/elasticsearch

www.sqlite.org

www.oracle.com/database/technologies/related/timesten.html

yanza.com

Technical documentation

cubrid.org/manuals

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

www.sqlite.org/docs.html

docs.oracle.com/database/timesten-18.1

Developer

CUBRID Corporation, CUBRID Foundation

Elastic

Dwayne Richard Hipp

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Yanza

Initial release

2008

2010

2000

1998

2015

Current release

11.0, January 2021

8.6, January 2023

3.46.0 (23 May 2024), May 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Elastic License

Open Source

Public Domain

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C, C++, Java

Java

Server operating systems

Linux
Windows

All OS with a Java VM

server-less

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Windows

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

dynamic column types

yes

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL-92 is not fully supported

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API

Supported programming languages

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

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C
C++
Java
PL/SQL

any language that supports HTTP calls

Server-side scripts

Stored procedures

Java Stored Procedures

yes

PL/SQL

Triggers

yes

by using the 'percolation' feature

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

yes

In-memory capabilities

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

Memcached and Redis integration

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.