DBMS > Amazon CloudSearch vs. JanusGraph vs. Memgraph vs. Teradata

System Properties Comparison Amazon CloudSearch vs. JanusGraph vs. Memgraph vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

A hybrid, in-memory first, distributed graph DBMS delivering high-performance on analytical and transactional workloads at enterprise scale

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Search engine

Graph DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Time Series DBMS

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

Score	2.89
Rank	#104	Overall
	#9	Search engines

Score	2.58
Rank	#110	Overall
	#5	Graph DBMS

Score	0.08
Rank	#305	Overall
	#29	Graph DBMS

Score	72.59
Rank	#14	Overall
	#9	Relational DBMS

Website

aws.amazon.com/cloudsearch

janusgraph.org

memgraph.com

www.teradata.com

Technical documentation

docs.aws.amazon.com/cloudsearch

docs.janusgraph.org

docs.memgraph.com

docs.teradata.com

Developer

Amazon

Linux Foundation; originally developed as Titan by Aurelius

Memgraph Ltd

Teradata

Initial release

2012

2017

1984

Current release

0.5.2, May 2020

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Free 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

Java

C and C++

Server operating systems

hosted

Linux
OS X
Unix
Windows

Linux

hosted
Linux

Data scheme

yes

schema-free and schema-optional

yes

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

all search fields are automatically indexed

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL 2016 + extensions

APIs and other access methods

HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Bolt protocol
Cypher query language

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

Clojure
Java
Python

.Net
C
C++
Elixir
Go
Haskell
Java
JavaScript
PHP
Python
Ruby
Scala

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

dynamic graph partitioning

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

relationships in graphs

yes

Transaction concepts

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

ACID

with snapshot isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

with periodic snapshot and write-ahead logging (WAL) of changes

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

authentication via encrypted signatures

User authentification and security via Rexster Graph Server

Users, roles and permissions

fine grained access rights according to SQL-standard

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.