DBMS > Brytlyt vs. GeoSpock vs. Google BigQuery vs. Newts vs. SQLite

System Properties Comparison Brytlyt vs. GeoSpock vs. Google BigQuery vs. Newts vs. SQLite

Editorial information provided by DB-Engines

Name

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

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

Spatial and temporal data processing engine for extreme data scale

Large scale data warehouse service with append-only tables

Time Series DBMS based on Cassandra

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.38
Rank	#279	Overall
	#126	Relational DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

brytlyt.io

geospock.com

cloud.google.com/bigquery

opennms.github.io/newts

www.sqlite.org

Technical documentation

docs.brytlyt.io

cloud.google.com/bigquery/docs

github.com/OpenNMS/newts/wiki

www.sqlite.org/docs.html

Developer

Brytlyt

GeoSpock

Google

OpenNMS Group

Dwayne Richard Hipp

Initial release

2016

2010

2014

2000

Current release

5.0, August 2023

2.0, September 2019

3.45.2 (12 March 2024), March 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Public Domain

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

C, C++ and CUDA

Java, Javascript

Java

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC

RESTful HTTP/JSON API

HTTP REST
Java API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on Cassandra

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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)

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.