DBMS > Geode vs. Kinetica vs. Microsoft SQL Server vs. MonetDB

System Properties Comparison Geode vs. Kinetica vs. Microsoft SQL Server vs. MonetDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Fully vectorized database across both GPUs and CPUs

Microsofts flagship relational DBMS

A relational database management system that stores data in columns

Primary database model

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.72
Rank	#141	Overall
	#64	Relational DBMS

Website

geode.apache.org

www.kinetica.com

www.microsoft.com/en-us/sql-server

www.monetdb.org

Technical documentation

geode.apache.org/docs

docs.kinetica.com

learn.microsoft.com/en-US/sql/sql-server

www.monetdb.org/Documentation

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Kinetica

Microsoft

MonetDB BV

Initial release

2002

2012

1989

2004

Current release

1.1, February 2017

7.1, August 2021

SQL Server 2022, November 2022

Dec2023 (11.49), December 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

restricted free version is available

Open Source

Mozilla Public License 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java

C, C++

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

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 query language (OQL)

SQL-like DML and DDL statements

yes

SQL 2003 with some extensions

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C++
Java
JavaScript (Node.js)
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

Server-side scripts

Stored procedures

user defined functions

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes, in SQL, C, R

Triggers

yes

Cache Event Listeners

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding via remote tables

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes, but depending on the SQL-Server Edition

none

Source-replica replication available in experimental status

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

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

GPU vRAM or System RAM

yes

User concepts

Access control

Access rights per client and object definable

Access rights for users and roles on table level

fine grained access rights according to SQL-standard

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.