DBMS > searchxml vs. Snowflake vs. Teradata Aster vs. Titan

System Properties Comparison searchxml vs. Snowflake vs. Teradata Aster vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

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

DBMS for structured and unstructured content wrapped with an application server

Cloud-based data warehousing service for structured and semi-structured data

Platform for big data analytics on multistructured data sources and types

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Native XML DBMS
Search engine

Relational DBMS

Graph DBMS

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

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.searchxml.net/category/products

www.snowflake.com

github.com/thinkaurelius/titan

Technical documentation

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

github.com/thinkaurelius/titan/wiki

Developer

informationpartners gmbh

Snowflake Computing Inc.

Teradata

Aurelius, owned by DataStax

Initial release

2015

2014

2005

2012

Current release

1.0

License

Commercial or Open Source

commercial

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

C++

Java

Server operating systems

Windows

hosted

Linux

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

on the application server

user defined functions

R packages

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

sychronisation to multiple collections

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

Transaction concepts

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

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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.

User concepts

Access control

Domain, group and role-based access control at the document level and for application services

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard

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.