DBMS > AlaSQL vs. EJDB vs. Google Cloud Datastore vs. Yanza

System Properties Comparison AlaSQL vs. EJDB vs. Google Cloud Datastore vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

JavaScript DBMS library

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Time Series DBMS for IoT Applications

Primary database model

Document store
Relational DBMS

Document store

Time Series DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Website

alasql.org

github.com/Softmotions/ejdb

cloud.google.com/datastore

yanza.com

Technical documentation

github.com/AlaSQL/alasql

github.com/Softmotions/ejdb/blob/master/README.md

cloud.google.com/datastore/docs

Developer

Andrey Gershun & Mathias R. Wulff

Softmotions

Google

Yanza

Initial release

2014

2012

2008

2015

License

Commercial or Open Source

Open Source

MIT-License

Open Source

GPLv2

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

JavaScript

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

server-less

hosted

Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes, details here

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

Close to SQL99, but no user access control, stored procedures and host language bindings.

SQL-like query language (GQL)

APIs and other access methods

JavaScript API

in-process shared library

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

HTTP API

Supported programming languages

JavaScript

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

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

none

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

typically not needed, however similar functionality with collection joins possible

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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)

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.

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

Create a Marvel Database with SQL and Javascript, the easy way
2 July 2019, Towards Data Science

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

Multi faceted data exploration in the browser using Leaflet and amCharts
3 May 2020, Towards Data Science

provided by Google News

Best cloud storage of 2024
29 April 2024, TechRadar

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

What Is Google Cloud Platform?
28 August 2023, Simplilearn

provided by Google News

Share this page