DBMS > BigObject vs. gStore

System Properties Comparison BigObject vs. gStore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

A native Graph DBMS to store and maintain very large RDF datasets.

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Graph DBMS
RDF store

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

Score	0.14
Rank	#333	Overall
	#145	Relational DBMS

Score	0.01
Rank	#376	Overall
	#39	Graph DBMS
	#20	RDF stores

Website

bigobject.io

en.gstore.cn

Technical documentation

docs.bigobject.io

en.gstore.cn/#/enDocs

Developer

BigObject, Inc.

Initial release

2015

2016

Current release

1.2, November 2023

License

Commercial or Open Source

commercial

free community edition available

Open Source

BSD

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux

Data scheme

yes

schema-free and OWL/RDFS-schema support

Typing

predefined data types such as float or date

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 DML and DDL statements

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

HTTP API
SPARQL 1.1

Supported programming languages

C++
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

Lua

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

Transaction concepts

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

yes

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, roles and permissions, Role-Based Access Control (RBAC) supported

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.

Share this page