DBMS > Google Cloud Datastore vs. LMDB vs. Sadas Engine vs. Trafodion

System Properties Comparison Google Cloud Datastore vs. LMDB vs. Sadas Engine vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A high performant, light-weight, embedded key-value database library

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store

Key-value store

Relational DBMS

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	1.94
Rank	#120	Overall
	#20	Key-value stores

Score	0.00
Rank	#385	Overall
	#159	Relational DBMS

Website

cloud.google.com/datastore

www.symas.com/symas-embedded-database-lmdb

www.sadasengine.com

trafodion.apache.org

Technical documentation

cloud.google.com/datastore/docs

www.lmdb.tech/doc

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

trafodion.apache.org/documentation.html

Developer

Google

Symas

SADAS s.r.l.

Apache Software Foundation, originally developed by HP

Initial release

2008

2011

2006

2014

Current release

0.9.32, January 2024

8.0

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

commercial

free trial version available

Open Source

Apache 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

C++

C++, Java

Server operating systems

hosted

Linux
Unix
Windows

AIX
Linux
Windows

Linux

Data scheme

schema-free

yes

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)

yes

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol

ADO.NET
JDBC
ODBC

Supported programming languages

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

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

.Net
C
C#
C++
Groovy
Java
PHP
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

using Google App Engine

Java Stored Procedures

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

via user defined functions and HBase

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

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

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

managed by 'Learn by Usage'

User concepts

Access control

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

Access rights for users, groups and roles according to SQL-standard

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.

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

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

Google App Engine
26 April 2024, TechTarget

17 Top Cloud Storage Companies to Know
9 April 2024, Built In

provided by Google News

Threat Actors Exploit Multiple Vulnerabilities in Ivanti Connect Secure and Policy Secure Gateways
29 February 2024, CISA

The Lightning Memory-mapped Database
2 March 2016, InfoQ.com

Akamai launches managed database service
25 April 2022, Blocks & Files

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

The Tom Brady Data Biography
8 September 2023, StatsBomb

provided by Google News

Share this page