DBMS > Amazon Redshift vs. Oracle Berkeley DB vs. Sqrrl vs. Transwarp Hippo

System Properties Comparison Amazon Redshift vs. Oracle Berkeley DB vs. Sqrrl vs. Transwarp Hippo

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

Large scale data warehouse service for use with business intelligence tools

Widely used in-process key-value store

Adaptable, secure NoSQL built on Apache Accumulo

Cloud-native distributed Vector DBMS that supports storage, retrieval, and management of massive vector-based datasets

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store
Graph DBMS
Key-value store
Wide column store

Vector DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.00
Rank	#383	Overall
	#13	Vector DBMS

Website

aws.amazon.com/redshift

www.oracle.com/database/technologies/related/berkeleydb.html

sqrrl.com

www.transwarp.cn/en/subproduct/hippo

Technical documentation

docs.aws.amazon.com/redshift

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Amazon (based on PostgreSQL)

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Amazon

originally Sqrrl Data, Inc.

Initial release

2012

1994

2012

2023

Current release

18.1.40, May 2020

1.0, May 2023

License

Commercial or Open Source

commercial

Open Source

commercial license available

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, Java, C++ (depending on the Berkeley DB edition)

Java

C++

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Linux
macOS

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

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

only with the Berkeley DB XML edition

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Actionscript
C

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

C++
Java
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

making use of Hadoop

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

Immediate Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Atomic updates per row, document, or graph entity

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

fine grained access rights according to SQL-standard

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

Role based access control and fine grained access rights

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.