DBMS > Apache Phoenix vs. Interbase vs. Newts vs. Snowflake

System Properties Comparison Apache Phoenix vs. Interbase vs. Newts vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

Light-weight proven RDBMS

originally from Borland

Time Series DBMS based on Cassandra

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

phoenix.apache.org

www.embarcadero.com/products/interbase

opennms.github.io/newts

www.snowflake.com

Technical documentation

phoenix.apache.org

docs.embarcadero.com/products/interbase

github.com/OpenNMS/newts/wiki

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Embarcadero

OpenNMS Group

Snowflake Computing Inc.

Initial release

2014

1984

2014

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

InterBase 2020, December 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

Linux
Unix
Windows

Android
iOS
Linux
OS X
Windows

Linux
OS X
Windows

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

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

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.

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

HTTP REST
Java API

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

Interbase procedure and trigger language

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on Cassandra

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Interbase Change Views

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

fine grained access rights according to SQL-standard

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.