DBMS > BigObject vs. Faircom DB vs. Snowflake vs. STSdb

System Properties Comparison BigObject vs. Faircom DB vs. Snowflake vs. STSdb

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

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Cloud-based data warehousing service for structured and semi-structured data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store
Relational DBMS

Relational DBMS

Key-value store

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

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

Website

bigobject.io

www.faircom.com/products/faircom-db

www.snowflake.com

github.com/STSSoft/STSdb4

Technical documentation

docs.bigobject.io

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

docs.snowflake.net/manuals/index.html

Developer

BigObject, Inc.

FairCom Corporation

Snowflake Computing Inc.

STS Soft SC

Initial release

2015

1979

2014

2011

Current release

V12, November 2020

4.0.8, September 2015

License

Commercial or Open Source

commercial

free community edition available

commercial

Restricted, free version available

commercial

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

ANSI C, 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)

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

hosted

Windows

Data scheme

yes

schema free, schema optional, schema required, partial schema,

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

CLI Client
JDBC
ODBC

.NET Client API

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

JavaScript (Node.js)
Python

C#
Java

Server-side scripts

Stored procedures

Lua

yes

.Net, JavaScript, C/C++

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

Users with fine-grained authorization concept, user roles and pluggable authentication

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.