DBMS > Cubrid vs. FeatureBase vs. Firebase Realtime Database vs. Snowflake vs. Solr

System Properties Comparison Cubrid vs. FeatureBase vs. Firebase Realtime Database vs. Snowflake vs. Solr

Editorial information provided by DB-Engines

Name

Description

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

Real-time database platform that powers real-time analytics and machine learning applications by simultaneously executing low-latency, high-throughput, and highly concurrent workloads.

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

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

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Secondary database models

Spatial DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.22
Rank	#309	Overall
	#139	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

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

www.featurebase.com

firebase.google.com/products/realtime-database

www.snowflake.com

solr.apache.org

Technical documentation

cubrid.org/manuals

docs.featurebase.com

firebase.google.com/docs/database

docs.snowflake.net/manuals/index.html

solr.apache.org/resources.html

Developer

CUBRID Corporation, CUBRID Foundation

Molecula and Pilosa Open Source Contributors

Google

acquired by Google 2014

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2008

2017

2012

2014

2006

Current release

11.0, January 2021

2022, May 2022

9.6.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2

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

Java

Server operating systems

Linux
Windows

Linux
macOS

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

schema-free

yes

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

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

yes

SQL queries

yes

Solr Parallel SQL Interface

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

gRPC
JDBC
Kafka Connector
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

CLI Client
JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

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

Java
Python

Java
JavaScript
Objective-C

JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

Java Stored Procedures

limited functionality with using 'rules'

user defined functions

Java plugins

Triggers

yes

Callbacks are triggered when data changes

similar concept for controling cloud resources

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using Linux fsync

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

yes, based on authentication and database rules

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

yes

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.