DBMS > EXASOL vs. Linter vs. ReductStore vs. Snowflake

System Properties Comparison EXASOL vs. Linter vs. ReductStore vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

RDBMS for high security requirements

Designed to manage unstructured time-series data efficiently, providing unique features such as storing time-stamped blobs with labels, customizable data retention policies, and a straightforward FIFO quota system.

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	0.05
Rank	#384	Overall
	#44	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.exasol.com

linter.ru

github.com/reductstore
www.reduct.store

www.snowflake.com

Technical documentation

www.exasol.com/resources

www.reduct.store/docs

docs.snowflake.net/manuals/index.html

Developer

Exasol

relex.ru

ReductStore LLC

Snowflake Computing Inc.

Initial release

2000

1990

2023

2014

Current release

1.9, March 2024

License

Commercial or Open Source

commercial

Open Source

Business Source License 1.1

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

C++, Rust

Server operating systems

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Docker
Linux
macOS
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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C++
JavaScript (Node.js)
Python
Rust

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax with the possibility to convert from PL/SQL

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

Concurrency

Support for concurrent manipulation of data

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

Access rights for users, groups and roles according to SQL-standard

fine grained access rights according to SQL-standard

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.