DBMS > Apache Kylin vs. GeoMesa vs. Lovefield vs. Microsoft Azure Synapse Analytics vs. Snowflake

System Properties Comparison Apache Kylin vs. GeoMesa vs. Lovefield vs. Microsoft Azure Synapse Analytics vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Embeddable relational database for web apps written in pure JavaScript

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

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

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

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

Score	1.18
Rank	#172	Overall
	#79	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

kylin.apache.org

www.geomesa.org

google.github.io/lovefield

azure.microsoft.com/services/synapse-analytics

www.snowflake.com

Technical documentation

kylin.apache.org/docs

www.geomesa.org/documentation/stable/user/index.html

github.com/google/lovefield/blob/master/docs/spec_index.md

docs.microsoft.com/azure/synapse-analytics

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation, originally contributed from eBay Inc

CCRi and others

Google

Microsoft

Snowflake Computing Inc.

Initial release

2015

2014

2016

2014

Current release

3.1.0, July 2020

4.0.5, February 2024

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

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

Scala

JavaScript

C++

Server operating systems

Linux

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

hosted

Data scheme

yes

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

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

ANSI SQL for queries (using Apache Calcite)

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

JavaScript

C#
Java
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Transact SQL

user defined functions

Triggers

Using read-only observers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding, horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

using MemoryDB

User concepts

Access control

yes

depending on the DBMS used for storage

yes

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

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.