DBMS > Google Cloud Datastore vs. jBASE vs. SQLite vs. Warp 10

System Properties Comparison Google Cloud Datastore vs. jBASE vs. SQLite vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A robust multi-value DBMS comprising development tools and middleware

Widely used embeddable, in-process RDBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

cloud.google.com/datastore

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.sqlite.org

www.warp10.io

Technical documentation

cloud.google.com/datastore/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

www.sqlite.org/docs.html

www.warp10.io/content/02_Getting_started

Developer

Google

Rocket Software (formerly Zumasys)

Dwayne Richard Hipp

SenX

Initial release

2008

1991

2000

2015

Current release

5.7

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Public Domain

Open Source

Apache License 2.0

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

Server operating systems

hosted

AIX
Linux
Windows

server-less

Linux
OS X
Windows

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes, details here

optional

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language (GQL)

Embedded SQL for jBASE in BASIC

yes

SQL-92 is not fully supported

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API
Jupyter
WebSocket

Supported programming languages

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

.Net
Basic
Jabbascript
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

using Google App Engine

yes

WarpScript

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

none

selectable replication factor

based on HBase

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

based on HBase

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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.

yes

User concepts

Access control

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

Access rights can be defined down to the item level

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.