DBMS > Amazon DynamoDB vs. Apache Jena - TDB vs. Atos Standard Common Repository vs. KeyDB

System Properties Comparison Amazon DynamoDB vs. Apache Jena - TDB vs. Atos Standard Common Repository vs. KeyDB

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, scalable database service by Amazon with the data stored in Amazons cloud

A RDF storage and query DBMS, shipped as an optional-use component of the Apache Jena framework

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Primary database model

Document store
Key-value store

RDF store

Document store
Key-value store

Key-value store

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

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	3.75
Rank	#84	Overall
	#3	RDF stores

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Website

aws.amazon.com/dynamodb

jena.apache.org/documentation/tdb/index.html

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

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

docs.aws.amazon.com/dynamodb

jena.apache.org/documentation/tdb/index.html

docs.keydb.dev

Developer

Amazon

Apache Software Foundation

originally developed by HP Labs

Atos Convergence Creators

EQ Alpha Technology Ltd.

Initial release

2012

2000

2016

2019

Current release

4.9.0, July 2023

1703

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache License, Version 2.0

commercial

Open Source

BSD-3

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

Server operating systems

hosted

All OS with a Java VM

Linux

Data scheme

schema-free

yes

RDF Schemas

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

yes

optional

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

LDAP

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

All languages with LDAP bindings

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

yes

Lua

Triggers

yes

by integration with AWS Lambda

yes

via event handler

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

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

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

TDB Transactions

Atomic execution of specific operations

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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)

Access control via Jena Security

LDAP bind authentication

simple password-based access control and ACL

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.