DBMS > Snowflake vs. Typesense vs. VelocityDB vs. Vertica

System Properties Comparison Snowflake vs. Typesense vs. VelocityDB vs. Vertica

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

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

Relational DBMS

Search engine

Graph DBMS
Object oriented DBMS

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	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.80
Rank	#209	Overall
	#14	Search engines

Score	0.00
Rank	#385	Overall
	#40	Graph DBMS
	#21	Object oriented DBMS

Score	9.62
Rank	#42	Overall
	#26	Relational DBMS

Website

Technical documentation

docs.snowflake.net/manuals/index.html

typesense.org/docs

velocitydb.com/UserGuide

vertica.com/documentation

Developer

Snowflake Computing Inc.

VelocityDB Inc

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2014

2015

2011

2005

Current release

7.x

12.0.3, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

yes

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++

Server operating systems

hosted

Linux

Any that supports .NET

Linux

Data scheme

yes

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

schema-free

pre-defined schema optional

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

CLI Client
JDBC
ODBC

RESTful HTTP API

.Net

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

character-based, interactive, front-end utility

Supported programming languages

JavaScript (Node.js)
Python

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

.Net

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

Server-side scripts

Stored procedures

user defined functions

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

similar concept for controling cloud resources

Callbacks are triggered when data changes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using 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

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.

yes

User concepts

Access control

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

Based on Windows Authentication

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.