DBMS > Ehcache vs. Percona Server for MongoDB vs. Snowflake vs. Sqrrl

System Properties Comparison Ehcache vs. Percona Server for MongoDB vs. Snowflake vs. Sqrrl

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

A widely adopted Java cache with tiered storage options

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Key-value store

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.ehcache.org

www.percona.com/mongodb/software/percona-server-for-mongodb

www.snowflake.com

sqrrl.com

Technical documentation

www.ehcache.org/documentation

docs.percona.com/percona-distribution-for-mongodb

docs.snowflake.net/manuals/index.html

Developer

Terracotta Inc, owned by Software AG

Percona

Snowflake Computing Inc.

Amazon

originally Sqrrl Data, Inc.

Initial release

2009

2015

2014

2012

Current release

3.10.0, March 2022

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL 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

Java

C++

Java

Server operating systems

All OS with a Java VM

Linux

hosted

Linux

Data scheme

schema-free

yes

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

schema-free

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

JCache

proprietary protocol using JSON

CLI Client
JDBC
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

Java

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

JavaScript (Node.js)
Python

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

JavaScript

user defined functions

Triggers

yes

Cache Event Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

yes

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Source-replica replication

yes

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

via In-Memory Engine

User concepts

Access control

Access rights for users and roles

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.