DBMS > SAP HANA vs. ScyllaDB vs. Snowflake vs. SpatiaLite

System Properties Comparison SAP HANA vs. ScyllaDB vs. Snowflake vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

In-memory, column based data store. Available as appliance or cloud service

Cassandra and DynamoDB compatible wide column store

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

Spatial extension of SQLite

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Key-value store

Relational DBMS

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	4.75
Rank	#68	Overall
	#5	Wide column stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

www.sap.com/products/hana.html

www.scylladb.com

www.snowflake.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

help.sap.com/hana

docs.scylladb.com

docs.snowflake.net/manuals/index.html

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

SAP

ScyllaDB

Snowflake Computing Inc.

Alessandro Furieri

Initial release

2010

2015

2014

2008

Current release

2.0 SPS07 (April 4, 2023), April 2023

ScyllaDB Open Source 5.4.1, January 2024

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

Open Source (AGPL), commercial license available

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Cloud-based only

Only available as a cloud service

also available as a cloud based service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

C++

Server operating systems

Appliance or cloud-service

Linux

hosted

server-less

Data scheme

yes

schema-free

yes

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

yes

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

cluster global secondary indices

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements (CQL)

yes

APIs and other access methods

JDBC
ODBC

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

CLI Client
JDBC
ODBC

Supported programming languages

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

SQLScript, R

yes, Lua

user defined functions

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Representation of geographical distribution of servers is possible

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomicity and isolation are supported for single operations

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

in-memory tables

yes

User concepts

Access control

yes

Access rights for users can be defined per object

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

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.