DBMS > Brytlyt vs. Ignite vs. Microsoft Azure Cosmos DB vs. SAP Advantage Database Server

System Properties Comparison Brytlyt vs. Ignite vs. Microsoft Azure Cosmos DB vs. SAP Advantage Database Server

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.

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

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.

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

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

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

brytlyt.io

ignite.apache.org

azure.microsoft.com/services/cosmos-db

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

Technical documentation

docs.brytlyt.io

apacheignite.readme.io/docs

learn.microsoft.com/azure/cosmos-db

Developer

Brytlyt

Apache Software Foundation

Microsoft

Sybase, SAP

Initial release

2016

2015

2014

1993

Current release

5.0, August 2023

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

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++ and CUDA

C++, Java, .Net

Server operating systems

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

hosted

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

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

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Delphi
Perl
PHP

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

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

JavaScript

yes

Triggers

yes

yes (cache interceptors and events)

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes (replicated cache)

yes

Implicit feature of the cloud service

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

caching of (temporary) tables can be configured

User concepts

Access control

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

Access rights can be defined down to the item level

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.