DBMS > Kdb vs. SiteWhere vs. Snowflake vs. Solr

System Properties Comparison Kdb vs. SiteWhere vs. Snowflake vs. Solr

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performance Time Series DBMS

M2M integration platform for persisting/querying time series data

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

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Time Series DBMS
Vector DBMS

Time Series DBMS

Relational DBMS

Search engine

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	7.55
Rank	#53	Overall
	#3	Time Series DBMS
	#1	Vector DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

kx.com

github.com/sitewhere/sitewhere

www.snowflake.com

solr.apache.org

Technical documentation

code.kx.com

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

solr.apache.org/resources.html

Developer

Kx Systems, a division of First Derivatives plc

SiteWhere

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2000

kdb was released 2000, kdb+ in 2003

2010

2014

2006

Current release

3.6, May 2018

9.6.0, April 2024

License

Commercial or Open Source

commercial

free 32-bit version

Open Source

Common Public Attribution License Version 1.0

commercial

Open Source

Apache Version 2

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

Java

Server operating systems

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

predefined scheme

yes

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

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

table attribute 'grouped'

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language (q)

yes

Solr Parallel SQL Interface

APIs and other access methods

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

HTTP REST

CLI Client
JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
Scala

JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

Java plugins

Triggers

yes

with views

similar concept for controling cloud resources

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

based on HBase

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

similar paradigm used for internal processing

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

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

rights management via user accounts

Users with fine-grained authorization concept

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

yes

More information provided by the system vendor

Specific characteristics

Integrated columnar database & programming system for streaming, real time and historical...
» more

Competitive advantages

provides seamless scalability; runs on industry standard server platforms; is top-ranked...
» more

Typical application scenarios

tick database streaming sensor data massive intelligence applications oil and gas...
» more

Key customers

Goldman Sachs Morgan Stanley Merrill Lynch J.P. Morgan Deutsche Bank IEX Securities...
» more

Market metrics

kdb+ performance and reliability proven by our customers in critical infrastructure...
» more

Licensing and pricing models

upon request
» more

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.