DBMS > Amazon Redshift vs. Graph Engine vs. Microsoft Access vs. Titan

System Properties Comparison Amazon Redshift vs. Graph Engine vs. Microsoft Access vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

Large scale data warehouse service for use with business intelligence tools

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Graph DBMS

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

Score	14.07
Rank	#38	Overall
	#23	Relational DBMS

Score	0.59
Rank	#235	Overall
	#21	Graph DBMS
	#33	Key-value stores

Score	91.31
Rank	#12	Overall
	#8	Relational DBMS

Website

aws.amazon.com/redshift

www.graphengine.io

www.microsoft.com/en-us/microsoft-365/access

github.com/thinkaurelius/titan

Technical documentation

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

developer.microsoft.com/en-us/access

github.com/thinkaurelius/titan/wiki

Developer

Amazon (based on PostgreSQL)

Microsoft

Aurelius, owned by DataStax

Initial release

2012

2010

1992

2012

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Bundled with Microsoft Office

Open Source

Apache license, version 2.0

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

.NET and C

C++

Java

Server operating systems

hosted

.NET

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Unix
Windows

Data scheme

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in graph

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

but no files for transaction logging

yes

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

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

a simple user-level security was built in till version Access 2003

User authentification and security via Rexster Graph Server

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.