DBMS > Cubrid vs. Graph Engine vs. GridGain vs. Lovefield

System Properties Comparison Cubrid vs. Graph Engine vs. GridGain 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

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

GridGain is an in-memory computing platform, built on Apache Ignite

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Key-value store
Relational DBMS

Relational DBMS

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Website

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

www.graphengine.io

www.gridgain.com

google.github.io/lovefield

Technical documentation

cubrid.org/manuals

www.graphengine.io/docs/manual

www.gridgain.com/docs/index.html

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

Developer

CUBRID Corporation, CUBRID Foundation

Microsoft

GridGain Systems, Inc.

Google

Initial release

2008

2010

2007

2014

Current release

11.0, January 2021

GridGain 8.5.1

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

MIT License

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

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, C++, .Net

JavaScript

Server operating systems

Linux
Windows

.NET

Linux
OS X
Solaris
Windows

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

tested with Chrome, Firefox, IE, Safari

Data scheme

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

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

C#
C++
F#
Visual Basic

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript

Server-side scripts

Stored procedures

Java Stored Procedures

yes

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

yes (cache interceptors and events)

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

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

Security Hooks for custom implementations

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

Trinity
30 October 2010, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

The graph analytics landscape 2019 - DataScienceCentral.com
27 February 2019, Data Science Central

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

provided by Google News

GridGain in-memory data and generative AI – Blocks and Files
10 May 2024, Blocks and Files

GridGain's 2023 Growth Positions Company for Strong 2024
24 January 2024, PR Newswire

GridGain Unified Real-Time Data Platform Version 8.9 Addresses Today's More Complex Real-Time Data Processing ...
12 October 2023, GlobeNewswire

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain: Product Overview and Analysis
5 June 2019, eWeek

provided by Google News

Share this page