DBMS > 4D vs. GridGain vs. Ignite vs. Microsoft SQL Server vs. Tibero

System Properties Comparison 4D vs. GridGain vs. Ignite vs. Microsoft SQL Server vs. Tibero

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

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.

Microsofts flagship relational DBMS

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

www.4d.com

www.gridgain.com

ignite.apache.org

www.microsoft.com/en-us/sql-server

us.tmaxsoft.com/products/tibero

Technical documentation

developer.4d.com

www.gridgain.com/docs/index.html

apacheignite.readme.io/docs

learn.microsoft.com/en-US/sql/sql-server

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

4D, Inc

GridGain Systems, Inc.

Apache Software Foundation

Microsoft

TmaxSoft

Initial release

1984

2007

2015

1989

2003

Current release

v20, April 2023

GridGain 8.5.1

Apache Ignite 2.6

SQL Server 2022, November 2022

6, April 2015

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

commercial

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

Java, C++, .Net

C++, Java, .Net

C++

C and Assembler

Server operating systems

OS X
Windows

Linux
OS X
Solaris
Windows

Linux
Windows

AIX
HP-UX
Linux
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

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

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

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

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

4D proprietary IDE
PHP

C#
C++
Java
PHP
Python
Ruby
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

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

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Persistent Stored Procedure (PSM)

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes (replicated cache)

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

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

In-memory capabilities

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

yes

planned for next version

User concepts

Access control

Users and groups

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.