DBMS > Bangdb vs. Interbase vs. Machbase Neo vs. Snowflake

System Properties Comparison Bangdb vs. Interbase vs. Machbase Neo vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

Light-weight proven RDBMS

originally from Borland

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Document store
Graph DBMS
Time Series DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.16
Rank	#338	Overall
	#47	Document stores
	#32	Graph DBMS
	#31	Time Series DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

bangdb.com

www.embarcadero.com/products/interbase

machbase.com

www.snowflake.com

Technical documentation

docs.bangdb.com

docs.embarcadero.com/products/interbase

machbase.com/dbms

docs.snowflake.net/manuals/index.html

Developer

Sachin Sinha, BangDB

Embarcadero

Machbase

Snowflake Computing Inc.

Initial release

2012

1984

2013

2014

Current release

BangDB 2.0, October 2021

InterBase 2020, December 2019

V8.0, August 2023

License

Commercial or Open Source

Open Source

BSD 3

commercial

free test version available

commercial

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

Server operating systems

Linux

Android
iOS
Linux
OS X
Windows

Linux
macOS
Windows

hosted

Data scheme

schema-free

yes

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

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

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.

export as XML data possible

yes

Secondary indexes

yes

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

yes

SQL-like query language

yes

APIs and other access methods

Proprietary protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Java
Python

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

user defined functions

Triggers

yes, Notifications (with Streaming only)

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

Interbase Change Views

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, run db with in-memory only mode

yes

volatile and lookup table

User concepts

Access control

yes (enterprise version only)

fine grained access rights according to SQL-standard

simple password-based access control

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.