DBMS > Cubrid vs. Google BigQuery vs. Graph Engine vs. Solr

System Properties Comparison Cubrid vs. Google BigQuery vs. Graph Engine vs. Solr

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

Large scale data warehouse service with append-only tables

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Search engine

Secondary database models

Spatial DBMS

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

Score	1.31
Rank	#169	Overall
	#78	Relational DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	44.28
Rank	#24	Overall
	#3	Search engines

Website

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

cloud.google.com/bigquery

www.graphengine.io

solr.apache.org

Technical documentation

cubrid.org/manuals

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

solr.apache.org/resources.html

Developer

CUBRID Corporation, CUBRID Foundation

Google

Microsoft

Apache Software Foundation

Initial release

2008

2010

2006

Current release

11.0, January 2021

9.5.0, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

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

.NET and C

Java

Server operating systems

Linux
Windows

hosted

.NET

All OS with a Java VM

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

Data scheme

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

Solr Parallel SQL Interface

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

RESTful HTTP API

Java API
RESTful HTTP/JSON API

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

.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

user defined functions

in JavaScript

yes

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.