DBMS > Cubrid vs. Google Cloud Datastore vs. LMDB vs. Lovefield

System Properties Comparison Cubrid vs. Google Cloud Datastore vs. LMDB vs. Lovefield

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

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

A high performant, light-weight, embedded key-value database library

Embeddable relational database for web apps written in pure JavaScript

Primary database model

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Website

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

cloud.google.com/datastore

www.symas.com/symas-embedded-database-lmdb

google.github.io/lovefield

Technical documentation

cubrid.org/manuals

cloud.google.com/datastore/docs

www.lmdb.tech/doc

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

Developer

CUBRID Corporation, CUBRID Foundation

Google

Symas

Google

Initial release

2008

2011

2014

Current release

11.0, January 2021

0.9.32, January 2024

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

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

JavaScript

Server operating systems

Linux
Windows

hosted

Linux
Unix
Windows

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

tested with Chrome, Firefox, IE, Safari

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL

Support of SQL

yes

SQL-like query language (GQL)

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

gRPC (using protocol buffers) 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

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

JavaScript

Server-side scripts

Stored procedures

Java Stored Procedures

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

Using read-only observers

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

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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.

Immediate 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

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

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google Cloud Platform: Professional Data Engineer certification prep
11 June 2024, O'Reilly Media

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
4 June 2024, TechRadar

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

provided by Google News

The Tom Brady Data Biography
8 September 2023, StatsBomb

Automating SAP S/4HANA Migration with IT-Conductor, BGP Managed Services, and AWS | Amazon Web Services
22 August 2023, AWS Blog

Jaxon Repp on HarperDB Distributed Database Platform
23 March 2022, InfoQ.com

Akamai launches managed database service – Blocks and Files
25 April 2022, Blocks and Files

The Lightning Memory-mapped Database
2 March 2016, InfoQ.com

provided by Google News

Share this page