DBMS > 4D vs. BigObject vs. Google Cloud Datastore vs. Trafodion

System Properties Comparison 4D vs. BigObject vs. Google Cloud Datastore 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

Application development environment with integrated database management system

Analytic DBMS for real-time computations and queries

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store

Relational DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Website

www.4d.com

bigobject.io

cloud.google.com/datastore

trafodion.apache.org

Technical documentation

developer.4d.com

docs.bigobject.io

cloud.google.com/datastore/docs

trafodion.apache.org/documentation.html

Developer

4D, Inc

BigObject, Inc.

Google

Apache Software Foundation, originally developed by HP

Initial release

1984

2015

2008

2014

Current release

v20, April 2023

2.3.0, February 2019

License

Commercial or Open Source

commercial

free community edition available

commercial

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++, Java

Server operating systems

OS X
Windows

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

SQL-like DML and DDL statements

SQL-like query language (GQL)

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

fluentd
ODBC
RESTful HTTP API

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

ADO.NET
JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Lua

using Google App Engine

Java Stored Procedures

Triggers

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication using Paxos

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

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

automatically between fact table and dimension tables

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

Read/write lock on objects (tables, trees)

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

Users and groups

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

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

DB-Engines blog posts

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Recent citations in the news

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

Why Google will waive egress fees for customers ditching GCP
11 January 2024, The Register

provided by Google News

Evaluating HTAP Databases for Machine Learning Applications
2 November 2016, KDnuggets

Low-latency, distributed database architectures are critical for emerging fog applications
7 April 2022, Embedded Computing Design

provided by Google News

Share this page