DBMS > Apache Doris vs. GeoSpock vs. Google BigQuery vs. GridDB vs. Sphinx

System Properties Comparison Apache Doris vs. GeoSpock vs. Google BigQuery vs. GridDB vs. Sphinx

Editorial information provided by DB-Engines

Name

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

Description

An MPP-based analytics DBMS embracing the MySQL protocol

Spatial and temporal data processing engine for extreme data scale

Large scale data warehouse service with append-only tables

Scalable in-memory time series database optimized for IoT and Big Data

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Relational DBMS

Time Series DBMS

Search engine

Secondary database models

Time Series DBMS

Key-value store
Relational DBMS

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

Score	0.60
Rank	#247	Overall
	#113	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

doris.apache.org
github.com/apache/doris

geospock.com

cloud.google.com/bigquery

griddb.net

sphinxsearch.com

Technical documentation

github.com/apache/doris/wiki

cloud.google.com/bigquery/docs

docs.griddb.net

sphinxsearch.com/docs

Developer

Apache Software Foundation, originally contributed from Baidu

GeoSpock

Google

Toshiba Corporation

Sphinx Technologies Inc.

Initial release

2017

2010

2013

2001

Current release

1.2.2, February 2023

2.0, September 2019

5.1, August 2022

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

GPL version 2, commercial licence 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

Java

Java, Javascript

C++

Server operating systems

Linux

hosted

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

yes

full-text index on all search fields

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

yes

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
MySQL client

JDBC

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Proprietary protocol

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Automatic sharding

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

ACID at container level

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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)

Access rights for users can be defined per database

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» 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.