DBMS > Badger vs. Brytlyt vs. HarperDB vs. Snowflake

System Properties Comparison Badger vs. Brytlyt vs. HarperDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

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.14
Rank	#331	Overall
	#49	Key-value stores

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

github.com/dgraph-io/badger

brytlyt.io

www.harperdb.io

www.snowflake.com

Technical documentation

godoc.org/github.com/dgraph-io/badger

docs.brytlyt.io

docs.harperdb.io/docs

docs.snowflake.net/manuals/index.html

Developer

DGraph Labs

Brytlyt

HarperDB

Snowflake Computing Inc.

Initial release

2017

2016

2017

2014

Current release

5.0, August 2023

3.1, August 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free community edition available

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

Node.js

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux
OS X

hosted

Data scheme

schema-free

yes

dynamic schema

yes

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

Typing

predefined data types such as float or date

yes

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

SQL

Support of SQL

yes

SQL-like data manipulation statements

yes

APIs and other access methods

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

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

Custom Functions

since release 3.1

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

A table resides as a whole on one (or more) nodes in a cluster

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

the nodes on which a table resides can be defined

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

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.