DBMS > Kinetica vs. searchxml vs. Snowflake vs. Vitess

System Properties Comparison Kinetica vs. searchxml vs. Snowflake vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fully vectorized database across both GPUs and CPUs

DBMS for structured and unstructured content wrapped with an application server

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Native XML DBMS
Search engine

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.kinetica.com

www.searchxml.net/category/products

www.snowflake.com

vitess.io

Technical documentation

docs.kinetica.com

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

vitess.io/docs

Developer

Kinetica

informationpartners gmbh

Snowflake Computing Inc.

The Linux Foundation, PlanetScale

Initial release

2012

2015

2014

2013

Current release

7.1, August 2021

1.0

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0, commercial licenses available

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

C++

Server operating systems

Linux

Windows

hosted

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

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

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

on the application server

user defined functions

yes

proprietary syntax

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

sychronisation to multiple collections

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

multiple readers, single writer

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

GPU vRAM or System RAM

yes

User concepts

Access control

Access rights for users and roles on table level

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

Users with fine-grained authorization concept

no user groups or roles

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.