DBMS > Databend vs. Dgraph vs. Interbase vs. SQLite vs. Trafodion

System Properties Comparison Databend vs. Dgraph vs. Interbase vs. SQLite vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

Distributed and scalable native Graph DBMS

Light-weight proven RDBMS

originally from Borland

Widely used embeddable, in-process RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

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

Score	0.34
Rank	#283	Overall
	#130	Relational DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/datafuselabs/databend
www.databend.com

dgraph.io

www.embarcadero.com/products/interbase

www.sqlite.org

trafodion.apache.org

Technical documentation

docs.databend.com

dgraph.io/docs

docs.embarcadero.com/products/interbase

www.sqlite.org/docs.html

trafodion.apache.org/documentation.html

Developer

Databend Labs

Dgraph Labs, Inc.

Embarcadero

Dwayne Richard Hipp

Apache Software Foundation, originally developed by HP

Initial release

2021

2016

1984

2000

2014

Current release

1.0.59, April 2023

InterBase 2020, December 2019

3.46.0 (23 May 2024), May 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

Open Source

Public Domain

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Rust

C++, Java

Server operating systems

hosted
Linux
macOS

Linux
OS X
Windows

Android
iOS
Linux
OS X
Windows

server-less

Linux

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

APIs and other access methods

CLI Client
JDBC
RESTful HTTP API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication via Raft

Interbase Change Views

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

via file-system locks

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

Users with fine-grained authorization concept, user roles

Planned for future releases

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.