DBMS > TypeDB vs. Vertica

System Properties Comparison TypeDB vs. Vertica

Please select another system to include it in the comparison.

Our visitors often compare TypeDB and Vertica with PostgreSQL, Databricks and Trino.

Editorial information provided by DB-Engines

Name

Description

TypeDB provides developers with an expressive, customizable type system to manage their data using an award-winning query language, TypeQL, while building on a high-performance, distributed architecture.

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

Graph DBMS

The type-theoretic data model of TypeDB subsumes the graph database model.
Object oriented DBMS

The data model of TypeDB comprises object-oriented features such as class inheritance and interfaces.
Relational DBMS

The type-theoretic data model of TypeDB subsumes the relational database model.

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.58
Rank	#234	Overall
	#20	Graph DBMS
	#10	Object oriented DBMS
	#109	Relational DBMS

Score	9.85
Rank	#42	Overall
	#26	Relational DBMS

Website

typedb.com

www.vertica.com

Technical documentation

typedb.com/docs

vertica.com/documentation

Developer

Vaticle

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2016

2005

Current release

2.28.3, June 2024

12.0.3, January 2023

License

Commercial or Open Source

Open Source

GPL Version 3, commercial licenses available

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

Java

C++

Server operating systems

Linux
OS X
Windows

Linux

Data scheme

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.

Secondary indexes

yes

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

SQL

Support of SQL

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

APIs and other access methods

gRPC protocol
TypeDB Console (shell)
TypeDB Studio (IDE)

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

character-based, interactive, front-end utility

Supported programming languages

All JVM based languages
C
C++
Java
JavaScript (Node.js)
Python
Rust

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

Server-side scripts

Stored procedures

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via raft

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

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

substituted by the relationship feature

yes

Transaction concepts

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

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

yes

at REST API level; other APIs in progress

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

Spacecraft Engineering Models: How to Migrate UML to TypeQL
8 September 2021, HackerNoon

We’ve Released a COVID-19 Knowledge Graph
14 July 2020, Towards Data Science

Top 45+ startups in Knowledge Graph Platforms in Jan, 2025
16 January 2025, Tracxn

provided by Google News

Introducing the Future of Data Analysis: A Revolutionary Tool for Vertica Users
25 October 2024, OpenText Blogs

Leveraging Vertica Performance by Reducing CPU System Calls
23 January 2025, Taboola.com

New browser-based query editor for OpenText Core Analytics Database accelerates and simplifies querying your data
25 November 2024, OpenText Blogs

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

Vertica on Kubernetes
20 June 2024, OpenText Blogs

provided by Google News

Share this page