DBMS > Atos Standard Common Repository vs. Brytlyt vs. EJDB vs. GridGain

System Properties Comparison Atos Standard Common Repository vs. Brytlyt vs. EJDB vs. GridGain

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Primary database model

Document store
Key-value store

Relational DBMS

Document store

Key-value store
Relational DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

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

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

brytlyt.io

github.com/Softmotions/ejdb

www.gridgain.com

Technical documentation

docs.brytlyt.io

github.com/Softmotions/ejdb/blob/master/README.md

www.gridgain.com/docs/index.html

Developer

Atos Convergence Creators

Brytlyt

Softmotions

GridGain Systems, Inc.

Initial release

2016

2012

2007

Current release

1703

5.0, August 2023

GridGain 8.5.1

License

Commercial or Open Source

commercial

Open Source

GPLv2

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

Java, C++, .Net

Server operating systems

Linux

Linux
OS X
Windows

server-less

Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

yes

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

APIs and other access methods

LDAP

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

in-process shared library

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

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

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

Sharding

cell division

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

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 or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

User concepts

Access control

LDAP bind authentication

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

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Brytlyt releases version 5.0, introducing a more intuitive, intelligent and flexible analytics platform
1 August 2023, PR Newswire

London data analytics startup Brytlyt raises €4.43M from Amsterdam-based Finch Capital, others
22 December 2021, Silicon Canals

London’s Brytlyt raises €4.4 million for its data analytics and visualisation technology
22 December 2021, EU-Startups

Bringing GPUs To Bear On Bog Standard Relational Databases
26 February 2018, The Next Platform

Brytlyt raises £3.8m for '1000x faster analytics'
22 December 2021, BusinessCloud

provided by Google News

GridGain's 2023 Growth Positions Company for Strong 2024
25 January 2024, Datanami

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

Share this page