DBMS > 4D vs. Coveo vs. Interbase vs. MySQL

System Properties Comparison 4D vs. Coveo vs. Interbase vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Light-weight proven RDBMS

originally from Borland

Widely used open source RDBMS

Primary database model

Relational DBMS

Search engine

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

www.4d.com

www.coveo.com

www.embarcadero.com/products/interbase

www.mysql.com

Technical documentation

developer.4d.com

docs.coveo.com

docs.embarcadero.com/products/interbase

dev.mysql.com/doc

Developer

4D, Inc

Coveo

Embarcadero

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

1984

2012

1984

1995

Current release

v20, April 2023

InterBase 2020, December 2019

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Server operating systems

OS X
Windows

hosted

Android
iOS
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

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.

yes

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes

with proprietary extensions

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

4D proprietary IDE
PHP

C#
Java
JavaScript
Python

.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

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

yes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Interbase Change Views

Multi-source replication
Source-replica replication

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

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

table locks or row locks depending on storage engine

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

Users and groups

granular access controls, API key management, content filters

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.