DBMS > Amazon SimpleDB vs. Atos Standard Common Repository vs. Oracle Berkeley DB vs. SQLite

System Properties Comparison Amazon SimpleDB vs. Atos Standard Common Repository vs. Oracle Berkeley DB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Hosted simple database service by Amazon, with the data stored in the Amazon Cloud.

There is an unrelated product called SimpleDB developed by Edward Sciore

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

Widely used in-process key-value store

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Document store
Key-value store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

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

Score	1.85
Rank	#138	Overall
	#24	Key-value stores

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

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/simpledb

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

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

www.sqlite.org

Technical documentation

docs.aws.amazon.com/simpledb

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

www.sqlite.org/docs.html

Developer

Amazon

Atos Convergence Creators

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Dwayne Richard Hipp

Initial release

2007

2016

1994

2000

Current release

1703

18.1.40, May 2020

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

Public Domain

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

Server operating systems

hosted

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

server-less

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

optional

yes

not rigid because of 'dynamic typing' concept.

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

yes

All columns are indexed automatically

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

LDAP

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Erlang
Java
PHP
Python
Ruby
Scala

All languages with LDAP bindings

.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
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding must be implemented in the application

Sharding

cell division

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

Concurrent data updates can be detected by the application

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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 and roles can be defined via the AWS Identity and Access Management (IAM)

LDAP bind 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.