DBMS > Apache Kylin vs. GeoSpock vs. Google BigQuery vs. SWC-DB

System Properties Comparison Apache Kylin vs. GeoSpock vs. Google BigQuery vs. SWC-DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

Large scale data warehouse service with append-only tables

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Wide column store

Secondary database models

Time Series DBMS

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

Score	1.14
Rank	#171	Overall
	#77	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.01
Rank	#378	Overall
	#13	Wide column stores

Website

kylin.apache.org

geospock.com

cloud.google.com/bigquery

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

kylin.apache.org/docs

cloud.google.com/bigquery/docs

Developer

Apache Software Foundation, originally contributed from eBay Inc

GeoSpock

Google

Alex Kashirin

Initial release

2015

2010

2020

Current release

3.1.0, July 2020

2.0, September 2019

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL V3

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

Java, Javascript

C++

Server operating systems

Linux

hosted

Linux

Data scheme

yes

schema-free

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.

Secondary indexes

yes

temporal, categorical

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

ANSI SQL for query only (using Presto)

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

RESTful HTTP/JSON API

Proprietary protocol
Thrift

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

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.

User concepts

Access control

Access rights for users can be defined per table

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.