DBMS > 4D vs. Cubrid vs. Google BigQuery vs. Graph Engine vs. Ignite

System Properties Comparison 4D vs. Cubrid vs. Google BigQuery vs. Graph Engine vs. Ignite

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Key-value store
Relational DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

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

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Website

www.4d.com

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

cloud.google.com/bigquery

www.graphengine.io

ignite.apache.org

Technical documentation

developer.4d.com

cubrid.org/manuals

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

apacheignite.readme.io/docs

Developer

4D, Inc

CUBRID Corporation, CUBRID Foundation

Google

Microsoft

Apache Software Foundation

Initial release

1984

2008

2010

2015

Current release

v20, April 2023

11.0, January 2021

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

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

.NET and C

C++, Java, .Net

Server operating systems

OS X
Windows

Linux
Windows

hosted

.NET

Linux
OS X
Solaris
Windows

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

close to SQL 92

yes

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

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

RESTful HTTP API

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

Supported programming languages

4D proprietary IDE
PHP

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

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

Java Stored Procedures

user defined functions

in JavaScript

yes

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

Triggers

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes (replicated cache)

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

Since BigQuery is designed for querying 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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Users and groups

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)

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.