DBMS > Firebird vs. Google Cloud Datastore vs. SAP HANA vs. Sphinx

System Properties Comparison Firebird vs. Google Cloud Datastore vs. SAP HANA vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

In-memory, column based data store. Available as appliance or cloud service

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.firebirdsql.org

cloud.google.com/datastore

www.sap.com/products/hana.html

sphinxsearch.com

Technical documentation

www.firebirdsql.org/en/reference-manuals

cloud.google.com/datastore/docs

help.sap.com/hana

sphinxsearch.com/docs

Developer

Firebird Foundation

Google

SAP

Sphinx Technologies Inc.

Initial release

2000

As fork of Borland's InterBase

2008

2010

2001

Current release

5.0.0, January 2024

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Initial Developer's Public License

commercial

Open Source

GPL version 2, commercial licence available

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (GQL)

yes

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

Proprietary protocol

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

PSQL

using Google App Engine

SQLScript, R

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication using Paxos

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

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

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

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

yes

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.