DBMS > GridGain vs. SAP Advantage Database Server vs. Vitess vs. Yaacomo

System Properties Comparison GridGain vs. SAP Advantage Database Server vs. Vitess vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

Low-cost RDBMS with access to ISAM and FoxPro data structures

Scalable, distributed, cloud-native DBMS, extending MySQL

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

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

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.gridgain.com

www.sap.com/products/advantage-database-server.html

vitess.io

yaacomo.com

Technical documentation

www.gridgain.com/docs/index.html

vitess.io/docs

Developer

GridGain Systems, Inc.

Sybase, SAP

The Linux Foundation, PlanetScale

Q2WEB GmbH

Initial release

2007

1993

2013

2009

Current release

GridGain 8.5.1

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0, commercial licenses 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

Server operating systems

Linux
OS X
Solaris
Windows

Linux
Windows

Docker
Linux
macOS

Android
Linux
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

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

yes

with proprietary extensions

yes

APIs and other access methods

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

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Delphi
Perl
PHP

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

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

yes

proprietary syntax

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

Multi-source replication
Source-replica 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

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

caching of (temporary) tables can be configured

yes

User concepts

Access control

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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

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

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

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

GridGain Adds Andy Sacks as Chief Revenue Officer, Promotes Lalit Ahuja to Chief Customer and Product Officer ...
17 July 2023, Yahoo Finance

GridGain: Product Overview and Analysis
5 June 2019, eWeek

provided by Google News

SAP Announces Q3 2023 Results: Asia Pacific and Japan View
19 October 2023, SAP News

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

provided by Google News

Share this page