DBMS > Apache Drill vs. Brytlyt vs. CouchDB vs. Snowflake vs. Teradata Aster

System Properties Comparison Apache Drill vs. Brytlyt vs. CouchDB vs. Snowflake vs. Teradata Aster

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

Platform for big data analytics on multistructured data sources and types

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

drill.apache.org/docs

docs.brytlyt.io

docs.couchdb.org/en/stable

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Brytlyt

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Snowflake Computing Inc.

Teradata

Initial release

2012

2016

2005

2014

2005

Current release

1.20.3, January 2023

5.0, August 2023

3.3.3, December 2023

License

Commercial or Open Source

Open Source

Apache Version 2

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.

Implementation language

C, C++ and CUDA

Erlang

Server operating systems

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

schema-free

yes

schema-free

yes

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

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C++

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

View functions in JavaScript

user defined functions

R packages

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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

fine grained access rights according to SQL-standard

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.