DBMS > Google Cloud Datastore vs. JSqlDb vs. QuestDB vs. Yanza

System Properties Comparison Google Cloud Datastore vs. JSqlDb vs. QuestDB vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

JavaScript Query Language Database, stores JavaScript objects and primitives

A high performance open source SQL database for time series data

Time Series DBMS for IoT Applications

Primary database model

Document store

Document store
Object oriented DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	2.81
Rank	#98	Overall
	#7	Time Series DBMS

Website

cloud.google.com/datastore

jsqldb.org (offline)

questdb.io

yanza.com

Technical documentation

cloud.google.com/datastore/docs

questdb.io/docs

Developer

Google

Konrad von Backstrom

QuestDB Technology Inc

Yanza

Initial release

2008

2018

2014

2015

Current release

0.8, December 2018

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java (Zero-GC), C++, Rust

Server operating systems

hosted

Linux
macOS
Windows

Windows

Data scheme

schema-free

yes

schema-free via InfluxDB Line Protocol

schema-free

Typing

predefined data types such as float or date

yes, details here

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

SQL

Support of SQL

SQL-like query language (GQL)

SQL with time-series extensions

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

HTTP API

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

any language that supports HTTP calls

Server-side scripts

Stored procedures

using Google App Engine

functions in JavaScript

Triggers

Callbacks using the Google Apps Engine

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning (by timestamps)

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

none

Source-replica replication with eventual consistency

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID for single-table writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using RocksDB

yes

In-memory capabilities

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

yes

through memory mapped files

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

More information provided by the system vendor

News

Combine Java and Rust Code Coverage in a Polyglot Project
10 September 2024

Weather data visualization and forecasting with QuestDB, Kafka and Grafana
4 September 2024

Building a new vector based storage model
22 August 2024

Calibrating VWAP executions with QuestDB and Grafana
16 August 2024

Write Time: a call for community writers
13 August 2024

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
13 September 2024, TechRadar

What Is Google Cloud? Platform, Benefits & More Explained
11 September 2024, Cloudwards

Google App Engine
26 April 2024, TechTarget

provided by Google News

SQL Extensions for Time-Series Data in QuestDB
11 January 2021, Towards Data Science

QuestDB snares $12M Series A with hosted version coming soon
3 November 2021, TechCrunch

QuestDB gets $12M Series A funding amid growing interest in time-series databases
3 November 2021, SiliconANGLE News

Read the Pitch Deck Database Startup QuestDB Used to Raise $12 Million
11 November 2021, Business Insider

Comparing Different Time-Series Databases
10 February 2022, hackernoon.com

provided by Google News

Share this page