DBMS > Cassandra vs. Firebird vs. Google Cloud Bigtable vs. Newts

System Properties Comparison Cassandra vs. Firebird vs. Google Cloud Bigtable vs. Newts

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

Firebird is an open source RDBMS forked from Borland's InterBase

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Time Series DBMS based on Cassandra

Primary database model

Wide column store

Relational DBMS

Key-value store
Wide column store

Time Series DBMS

Secondary database models

Vector DBMS

starting with release V5

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

Score	101.89
Rank	#12	Overall
	#1	Wide column stores

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

cassandra.apache.org

www.firebirdsql.org

cloud.google.com/bigtable

opennms.github.io/newts

Technical documentation

cassandra.apache.org/doc/latest

www.firebirdsql.org/en/reference-manuals

cloud.google.com/bigtable/docs

github.com/OpenNMS/newts/wiki

Developer

Apache Software Foundation

Apache top level project, originally developped by Facebook

Firebird Foundation

Google

OpenNMS Group

Initial release

2008

2000

As fork of Borland's InterBase

2015

2014

Current release

4.1.3, July 2023

5.0.0, January 2024

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Initial Developer's Public License

commercial

Open Source

Apache 2.0

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.

Astra DB: Multi-cloud DBaaS built on Apache Cassandra.

Implementation language

Java

C and C++

Java

Server operating systems

BSD
Linux
OS X
Windows

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

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

restricted

only equality queries, not always the best performing solution

yes

SQL

Support of SQL

SQL-like SELECT, DML and DDL statements (CQL)

yes

APIs and other access methods

Proprietary protocol

CQL (Cassandra Query Language, an SQL-like language)
Thrift

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

HTTP REST
Java API

Supported programming languages

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C#
C++
Go
Java
JavaScript (Node.js)
Python

Java

Server-side scripts

Stored procedures

PSQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Representation of geographical distribution of servers is possible

Source-replica replication

Internal replication in Colossus, and regional replication between two clusters in different zones

selectable replication factor

based on Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomicity and isolation are supported for single operations

ACID

Atomic single-row operations

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

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.

User concepts

Access control

Access rights for users can be defined per object

Users with fine-grained authorization concept

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

More information provided by the system vendor

Specific characteristics

Apache Cassandra is the leading NoSQL, distributed database management system, well...
» more

Competitive advantages

No single point of failure ensures 100% availability . Operational simplicity for...
» more

Typical application scenarios

Internet of Things (IOT), fraud detection applications, recommendation engines, product...
» more

Key customers

Apple, Netflix, Uber, ING,, Intuit,Fidelity, NY Times, Outbrain, BazaarVoice, Best...
» more

Market metrics

Cassandra is used by 40% of the Fortune 100.
» more

Licensing and pricing models

Apache licenseÂ Pricing for commercial distributions provided by DataStax and available...
» more

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.