DBMS > Google Cloud Datastore vs. IRONdb vs. Newts vs. searchxml

System Properties Comparison Google Cloud Datastore vs. IRONdb vs. Newts vs. searchxml

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb 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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Time Series DBMS based on Cassandra

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Document store

Time Series DBMS

Native XML DBMS
Search engine

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

cloud.google.com/datastore

www.circonus.com/solutions/time-series-database/

opennms.github.io/newts

www.searchxml.net/category/products

Technical documentation

cloud.google.com/datastore/docs

docs.circonus.com/irondb/category/getting-started

github.com/OpenNMS/newts/wiki

www.searchxml.net/support/handouts

Developer

Google

Circonus LLC.

OpenNMS Group

informationpartners gmbh

Initial release

2008

2017

2014

2015

Current release

V0.10.20, January 2018

1.0

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

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 and C++

Java

C++

Server operating systems

hosted

Linux

Linux
OS X
Windows

Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

text, numeric, histograms

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)

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

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

HTTP API

HTTP REST
Java API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Java

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

using Google App Engine

yes, in Lua

yes

on the application server

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

configurable replication factor, datacenter aware

selectable replication factor

based on Cassandra

yes

sychronisation to multiple collections

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 per node, eventual consistency across nodes

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

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

Domain, group and role-based access control at the document level and for application services

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

Best cloud storage of 2024
4 June 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

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

provided by Google News

Application observability firm Apica buys telemetry data startup Circonus and adds more funding
21 February 2024, SiliconANGLE News

Apica Acquires Telemetry Data Management Pioneer Circonus And Lands New Funding
22 February 2024, Datanami

Apica gets $6 million in funding and buys Circonus -
21 February 2024, Enterprise Times

provided by Google News

Share this page