DBMS > Cubrid vs. Google Cloud Datastore vs. mSQL vs. SAP HANA vs. Solr

System Properties Comparison Cubrid vs. Google Cloud Datastore vs. mSQL vs. SAP HANA 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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

mSQL (Mini SQL) is a simple and lightweight RDBMS

In-memory, column based data store. Available as appliance or cloud service

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

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

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

cloud.google.com/datastore

hughestech.com.au/products/msql

www.sap.com/products/hana.html

solr.apache.org

Technical documentation

cubrid.org/manuals

cloud.google.com/datastore/docs

help.sap.com/hana

solr.apache.org/resources.html

Developer

CUBRID Corporation, CUBRID Foundation

Google

Hughes Technologies

SAP

Apache Software Foundation

Initial release

2008

1994

2010

2006

Current release

11.0, January 2021

4.4, October 2021

2.0 SPS07 (April 4, 2023), April 2023

9.6.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free licenses can be provided

commercial

Open Source

Apache Version 2

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

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

hosted

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

Appliance or cloud-service

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

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

Typing

predefined data types such as float or date

yes

yes, details here

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-like query language (GQL)

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

Solr Parallel SQL Interface

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Delphi
Java
Perl
PHP
Tcl

.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

using Google App Engine

SQLScript, R

Java plugins

Triggers

yes

Callbacks using the Google Apps Engine

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication using Paxos

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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, groups and roles based on Google Cloud Identity and 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.