DBMS > Google Cloud Datastore vs. Oracle vs. Solr vs. Transbase

System Properties Comparison Google Cloud Datastore vs. Oracle vs. Solr vs. Transbase

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

Widely used RDBMS

A widely used distributed, scalable search engine based on Apache Lucene

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Spatial DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

cloud.google.com/datastore

www.oracle.com/database

solr.apache.org

www.transaction.de/en/products/transbase.html

Technical documentation

cloud.google.com/datastore/docs

docs.oracle.com/en/database

solr.apache.org/resources.html

www.transaction.de/en/products/transbase/features.html

Developer

Google

Oracle

Apache Software Foundation

Transaction Software GmbH

Initial release

2008

1980

2006

1987

Current release

23c, September 2023

9.5.0, February 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache Version 2

commercial

free development license

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

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes, details here

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

with proprietary extensions

Solr Parallel SQL Interface

yes

APIs and other access methods

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

using Google App Engine

PL/SQL

also stored procedures in Java possible

Java plugins

yes

Triggers

Callbacks using the Google Apps Engine

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

can be realized in PL/SQL

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

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

Eventual Consistency

Immediate Consistency

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

isolation level can be parameterized

optimistic locking

yes

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.

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

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

fine grained access rights according to SQL-standard

yes

fine grained access rights according to SQL-standard

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.