DBMS > Brytlyt vs. HEAVY.AI vs. Microsoft Access vs. Realm vs. Snowflake

System Properties Comparison Brytlyt vs. HEAVY.AI vs. Microsoft Access vs. Realm vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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

Primary database model

Relational DBMS

Document 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	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

brytlyt.io

github.com/heavyai/heavydb
www.heavy.ai

www.microsoft.com/en-us/microsoft-365/access

realm.io

www.snowflake.com

Technical documentation

docs.brytlyt.io

docs.heavy.ai

developer.microsoft.com/en-us/access

realm.io/docs

docs.snowflake.net/manuals/index.html

Developer

Brytlyt

HEAVY.AI, Inc.

Microsoft

Realm, acquired by MongoDB in May 2019

Snowflake Computing Inc.

Initial release

2016

1992

2014

Current release

5.0, August 2023

5.10, January 2022

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

Bundled with Microsoft Office

Open Source

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

C++

Server operating systems

Linux
OS X
Windows

Linux

Windows

Not a real database server, but making use of DLLs

Android
Backend: server-less
iOS
Windows

hosted

Data scheme

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

yes

but not compliant to any SQL standard

yes

APIs and other access methods

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

JDBC
ODBC
Thrift
Vega

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

All languages supporting JDBC/ODBC/Thrift
Python

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.Net
Java

with Android only
Objective-C
React Native
Swift

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

since Access 2010 using the ACE-engine

runs within the applications so server-side scripts are unnecessary

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

yes

Change Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

In-Memory realm

User concepts

Access control

fine grained access rights according to SQL-standard

a simple user-level security was built in till version Access 2003

yes

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.