DBMS > Amazon DynamoDB vs. Citus vs. Datomic vs. OrientDB vs. Typesense

System Properties Comparison Amazon DynamoDB vs. Citus vs. Datomic vs. OrientDB vs. Typesense

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Multi-model DBMS (Document, Graph, Key/Value)

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store

Search engine

Secondary database models

Document 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	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	0.79
Rank	#210	Overall
	#14	Search engines

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

docs.citusdata.com

docs.datomic.com

www.orientdb.com/docs/last/index.html

typesense.org/docs

Developer

Amazon

Cognitect

OrientDB LTD; CallidusCloud; SAP

Initial release

2012

2010

2012

2010

2015

Current release

8.1, December 2018

1.0.6735, June 2023

3.2.29, March 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

AGPL, commercial license also available

commercial

limited edition free

Open Source

Apache version 2

Open Source

GPL V3

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, Clojure

Java

C++

Server operating systems

hosted

Linux

All OS with a Java VM

All OS with a Java JDK (>= JDK 6)

Linux

Data scheme

schema-free

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

pre-defined schema optional

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

specific XML type available, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

SQL-like query language, no joins

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Clojure
Java

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

Transaction Functions

Java, Javascript

Triggers

yes

by integration with AWS Lambda

yes

By using transaction functions

Hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

none

But extensive use of caching in the application peers

Multi-source replication

Multi-source replication using RAFT

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

Access rights for users and roles; record level security configurable

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.