DBMS > Brytlyt vs. Cassandra vs. Firebase Realtime Database vs. GridGain

System Properties Comparison Brytlyt vs. Cassandra vs. Firebase Realtime Database vs. GridGain

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

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

Primary database model

Relational DBMS

Wide column store

Document store

Key-value store
Relational DBMS

Secondary database models

Vector DBMS

starting with release V5

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	101.89
Rank	#12	Overall
	#1	Wide column stores

Score	14.29
Rank	#39	Overall
	#6	Document stores

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

Website

brytlyt.io

cassandra.apache.org

firebase.google.com/products/realtime-database

www.gridgain.com

Technical documentation

docs.brytlyt.io

cassandra.apache.org/doc/latest

firebase.google.com/docs/database

www.gridgain.com/docs/index.html

Developer

Brytlyt

Apache Software Foundation

Apache top level project, originally developped by Facebook

Google

acquired by Google 2014

GridGain Systems, Inc.

Initial release

2016

2008

2012

2007

Current release

5.0, August 2023

4.1.3, July 2023

GridGain 8.5.1

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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.

Astra DB: Multi-cloud DBaaS built on Apache Cassandra.

Implementation language

C, C++ and CUDA

Java

Java, C++, .Net

Server operating systems

Linux
OS X
Windows

BSD
Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

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

yes

Secondary indexes

yes

restricted

only equality queries, not always the best performing solution

yes

SQL

Support of SQL

yes

SQL-like SELECT, DML and DDL statements (CQL)

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

APIs and other access methods

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

Proprietary protocol

CQL (Cassandra Query Language, an SQL-like language)
Thrift

Android
iOS
JavaScript API
RESTful HTTP API

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

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

Java
JavaScript
Objective-C

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

limited functionality with using 'rules'

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

Triggers

yes

Callbacks are triggered when data changes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

Representation of geographical distribution of servers is possible

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomicity and isolation are supported for single operations

yes

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per object

yes, based on authentication and database rules

Security Hooks for custom implementations

More information provided by the system vendor

Specific characteristics

Apache Cassandra is the leading NoSQL, distributed database management system, well...
» more

Competitive advantages

No single point of failure ensures 100% availability . Operational simplicity for...
» more

Typical application scenarios

Internet of Things (IOT), fraud detection applications, recommendation engines, product...
» more

Key customers

Apple, Netflix, Uber, ING,, Intuit,Fidelity, NY Times, Outbrain, BazaarVoice, Best...
» more

Market metrics

Cassandra is used by 40% of the Fortune 100.
» more

Licensing and pricing models

Apache licenseÂ Pricing for commercial distributions provided by DataStax and available...
» more

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.