DBMS > DataFS vs. Interbase vs. Sequoiadb vs. Snowflake

System Properties Comparison DataFS vs. Interbase vs. Sequoiadb vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

Light-weight proven RDBMS

originally from Borland

NewSQL database with distributed OLTP and SQL

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

Primary database model

Object oriented DBMS

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Secondary database models

Graph DBMS

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

Score	0.09
Rank	#360	Overall
	#17	Object oriented DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

newdatabase.com

www.embarcadero.com/products/interbase

www.sequoiadb.com

www.snowflake.com

Technical documentation

dev.mobiland.com/Overview.xsp

docs.embarcadero.com/products/interbase

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.snowflake.net/manuals/index.html

Developer

Mobiland AG

Embarcadero

Sequoiadb Ltd.

Snowflake Computing Inc.

Initial release

2018

1984

2013

2014

Current release

1.1.263, October 2022

InterBase 2020, December 2019

License

Commercial or Open Source

commercial

Open Source

Server: AGPL; Client: Apache V2

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

Server operating systems

Windows

Android
iOS
Linux
OS X
Windows

Linux

hosted

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

ADO.NET
JDBC
ODBC

proprietary protocol using JSON

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
VB.Net

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

.Net
C++
Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

JavaScript

user defined functions

Triggers

no, except callback-events from server when changes happened

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Document is locked during a transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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

Windows-Profile

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.