DBMS > CouchDB vs. Dolt vs. Hyprcubd vs. Interbase vs. Microsoft SQL Server

System Properties Comparison CouchDB vs. Dolt vs. Hyprcubd vs. Interbase vs. Microsoft SQL Server

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A MySQL compatible DBMS with Git-like versioning of data and schema

Serverless Time Series DBMS

Light-weight proven RDBMS

originally from Borland

Microsofts flagship relational DBMS

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store

Document store
Graph DBMS
Spatial DBMS

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

couchdb.apache.org

github.com/dolthub/dolt
www.dolthub.com

hyprcubd.com (offline)

www.embarcadero.com/products/interbase

www.microsoft.com/en-us/sql-server

Technical documentation

docs.couchdb.org/en/stable

docs.dolthub.com

docs.embarcadero.com/products/interbase

learn.microsoft.com/en-US/sql/sql-server

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

DoltHub Inc

Hyprcubd, Inc.

Embarcadero

Microsoft

Initial release

2005

2018

1984

1989

Current release

3.3.3, December 2023

InterBase 2020, December 2019

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache Version 2.0

commercial

restricted free version is 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.

Implementation language

Erlang

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

hosted

Android
iOS
Linux
OS X
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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

via views

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

CLI Client
HTTP REST

gRPC (https)

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Server-side scripts

Stored procedures

View functions in JavaScript

yes

currently in alpha release

yes

Interbase procedure and trigger language

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Interbase Change Views

yes, but depending on the SQL-Server Edition

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Multiversion concurreny control

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

Access rights for users can be defined per database

Only one user is configurable, and must be specified in the config file at startup

token access

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.