DBMS > Dolt vs. FatDB vs. Graphite vs. Oracle

System Properties Comparison Dolt vs. FatDB vs. Graphite vs. Oracle

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Widely used RDBMS

Primary database model

Relational DBMS

Document store
Key-value store

Time Series DBMS

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	5.19
Rank	#62	Overall
	#4	Time Series DBMS

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Website

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

github.com/graphite-project/graphite-web

www.oracle.com/database

Technical documentation

docs.dolthub.com

graphite.readthedocs.io

docs.oracle.com/en/database

Developer

DoltHub Inc

FatCloud

Chris Davis

Oracle

Initial release

2018

2012

2006

1980

Current release

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

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

Python

C and C++

Server operating systems

Linux
macOS
Windows

Windows

Linux
Unix

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

yes

Numeric data only

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

Secondary indexes

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

with proprietary extensions

APIs and other access methods

CLI Client
HTTP REST

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HTTP API
Sockets

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

JavaScript (Node.js)
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

via applications

PL/SQL

also stored procedures in Java possible

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

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

selectable replication factor

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

locking

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

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

Can implement custom security layer via applications

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.