DBMS > Interbase vs. MySQL vs. Pinecone vs. Sqrrl

System Properties Comparison Interbase vs. MySQL vs. Pinecone vs. Sqrrl

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

Light-weight proven RDBMS

originally from Borland

Widely used open source RDBMS

A managed, cloud-native vector database

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Relational DBMS

Key/Value like access via memcached API

Vector DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store
Spatial DBMS

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

Score	3.78
Rank	#77	Overall
	#41	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	3.02
Rank	#87	Overall
	#3	Vector DBMS

Website

www.embarcadero.com/products/interbase

www.mysql.com

www.pinecone.io

sqrrl.com

Technical documentation

docs.embarcadero.com/products/interbase

dev.mysql.com/doc

docs.pinecone.io/docs/overview

Developer

Embarcadero

Oracle

since 2010, originally MySQL AB, then Sun

Pinecone Systems, Inc

Amazon

originally Sqrrl Data, Inc.

Initial release

1984

1995

2019

2012

Current release

InterBase 2020, December 2019

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Java

Server operating systems

Android
iOS
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

String, Number, 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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Python

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

Multi-source replication
Source-replica replication

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.