DBMS > 4D vs. AgensGraph vs. Google BigQuery vs. Riak KV vs. STSdb

System Properties Comparison 4D vs. AgensGraph vs. Google BigQuery vs. Riak KV vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Large scale data warehouse service with append-only tables

Distributed, fault tolerant key-value store

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Graph DBMS
Relational DBMS

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Key-value store

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

www.4d.com

bitnine.net/agensgraph

cloud.google.com/bigquery

github.com/STSSoft/STSdb4

Technical documentation

developer.4d.com

bitnine.net/documentation

cloud.google.com/bigquery/docs

www.tiot.jp/riak-docs/riak/kv/latest

Developer

4D, Inc

Bitnine Global Inc.

Google

OpenSource, formerly Basho Technologies

STS Soft SC

Initial release

1984

2016

2010

2009

2011

Current release

v20, April 2023

2.1, December 2018

3.2.0, December 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPLv2, commercial license available

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

Erlang

Server operating systems

OS X
Windows

Linux
OS X
Windows

hosted

Linux
OS X

Windows

Data scheme

yes

depending on used data model

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

restricted

SQL

Support of SQL

yes

close to SQL 92

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

Cypher Query Language
JDBC

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

.NET Client API

Supported programming languages

4D proprietary IDE
PHP

C
Java
JavaScript
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C#
Java

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

no, but can be realized using table inheritance

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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

Users and groups

fine grained access rights according to SQL-standard

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

yes, using Riak Security

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.