DBMS > Apache Drill vs. Atos Standard Common Repository vs. Rockset vs. Snowflake vs. STSdb

System Properties Comparison Apache Drill vs. Atos Standard Common Repository vs. Rockset vs. Snowflake vs. STSdb

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Document store

Relational DBMS

Key-value store

Secondary database models

Relational DBMS
Search engine

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

drill.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

rockset.com

www.snowflake.com

github.com/STSSoft/STSdb4

Technical documentation

drill.apache.org/docs

docs.rockset.com

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Atos Convergence Creators

Rockset

Snowflake Computing Inc.

STS Soft SC

Initial release

2012

2016

2019

2014

2011

Current release

1.20.3, January 2023

1703

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GPLv2, commercial license available

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

Server operating systems

Linux
OS X
Windows

Linux

hosted

Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

optional

dynamic typing

yes

primitive types and user defined types (classes)

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

ingestion from XML files supported

yes

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

Read-only SQL queries, including JOINs

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

LDAP

HTTP REST

CLI Client
JDBC
ODBC

.NET Client API

Supported programming languages

C++

All languages with LDAP bindings

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

C#
Java

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Automatic sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

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

yes

User concepts

Access control

Depending on the underlying data source

LDAP bind authentication

Access rights for users and organizations can be defined via Rockset console

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.