DBMS > atoti vs. Blueflood vs. Brytlyt vs. Firebase Realtime Database vs. Snowflake

System Properties Comparison atoti vs. Blueflood vs. Brytlyt vs. Firebase Realtime Database vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

Scalable TimeSeries DBMS based on Cassandra

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

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

Score	0.56
Rank	#245	Overall
	#10	Object oriented DBMS

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

atoti.io

blueflood.io

brytlyt.io

firebase.google.com/products/realtime-database

www.snowflake.com

Technical documentation

docs.atoti.io

github.com/rax-maas/blueflood/wiki

docs.brytlyt.io

firebase.google.com/docs/database

docs.snowflake.net/manuals/index.html

Developer

ActiveViam

Rackspace

Brytlyt

Google

acquired by Google 2014

Snowflake Computing Inc.

Initial release

2013

2016

2012

2014

Current release

5.0, August 2023

License

Commercial or Open Source

commercial

free versions available

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

Java

C, C++ and CUDA

Server operating systems

Linux
OS X

Linux
OS X
Windows

hosted

Data scheme

predefined scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

SQL

Support of SQL

Multidimensional Expressions (MDX)

yes

APIs and other access methods

HTTP REST

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

Android
iOS
JavaScript API
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

Java
JavaScript
Objective-C

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Python

user defined functions

in PL/pgSQL

limited functionality with using 'rules'

user defined functions

Triggers

yes

Callbacks are triggered when data changes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Sharding

based on Cassandra

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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

yes, based on authentication and database rules

Users with fine-grained authorization concept, user roles and pluggable authentication

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.