DBMS > Google BigQuery vs. Interbase vs. Manticore Search vs. RDF4J

System Properties Comparison Google BigQuery vs. Interbase vs. Manticore Search vs. RDF4J

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Light-weight proven RDBMS

originally from Borland

Multi-storage database for search, including full-text search.

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Relational DBMS

Search engine

RDF store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

cloud.google.com/bigquery

www.embarcadero.com/products/interbase

manticoresearch.com

rdf4j.org

Technical documentation

cloud.google.com/bigquery/docs

docs.embarcadero.com/products/interbase

manual.manticoresearch.com

rdf4j.org/documentation

Developer

Google

Embarcadero

Manticore Software

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2010

1984

2017

2004

Current release

InterBase 2020, December 2019

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Eclipse Distribution License (EDL), v1.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.

Implementation language

C++

Java

Server operating systems

hosted

Android
iOS
Linux
OS X
Windows

FreeBSD
Linux
macOS
Windows

Linux
OS X
Unix
Windows

Data scheme

yes

Fixed schema

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Interbase procedure and trigger language

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

Synchronous replication based on Galera library

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

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

yes

in-memory storage is supported as well

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

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.