DBMS > searchxml vs. Trafodion vs. Vertica

System Properties Comparison searchxml vs. Trafodion vs. Vertica

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

DBMS for structured and unstructured content wrapped with an application server

Transactional SQL-on-Hadoop DBMS

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Native XML DBMS
Search engine

Relational DBMS

Column oriented

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	0.00
Rank	#378	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	9.96
Rank	#42	Overall
	#26	Relational DBMS

Website

www.searchxml.net/category/products

trafodion.apache.org

www.vertica.com

Technical documentation

www.searchxml.net/support/handouts

trafodion.apache.org/documentation.html

vertica.com/documentation

Developer

informationpartners gmbh

Apache Software Foundation, originally developed by HP

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2015

2014

2005

Current release

1.0

2.3.0, February 2019

12.0.3, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C++, Java

C++

Server operating systems

Windows

Linux

Data scheme

schema-free

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

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

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

RESTful HTTP API
WebDAV
XQuery
XSLT

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

C++

most other programming languages supported via APIs

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

yes

on the application server

Java Stored Procedures

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

sychronisation to multiple collections

yes, via HBase

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

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

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

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Evaluating HTAP Databases for Machine Learning Applications
2 November 2016, KDnuggets

An Open Source Tour de Force at Apache: Big Data 2016
11 May 2016, Datanami

Low-latency, distributed database architectures are critical for emerging fog applications
7 April 2022, Embedded Computing Design

provided by Google News

Don’t Believe the Big Database Hype, Stonebraker Warns
8 July 2024, Datanami

Why HPE Vertica 8 is the best fit for businesses to create an analytics-driven enterprise
16 July 2024, AIM

What’s New in OpenText Vertica
25 July 2023, OpenText

Querying a Vertica data source in Amazon Athena using the Athena Federated Query SDK
11 February 2021, AWS Blog

Postgres pioneer Michael Stonebraker promises to upend the database once more
26 December 2023, The Register

provided by Google News

Share this page