DBMS > Graphite vs. Oracle vs. OrigoDB vs. Snowflake

System Properties Comparison Graphite vs. Oracle vs. OrigoDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Widely used RDBMS

A fully ACID in-memory object graph database

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Time Series DBMS

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

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	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/graphite-project/graphite-web

www.oracle.com/database

origodb.com

www.snowflake.com

Technical documentation

graphite.readthedocs.io

docs.oracle.com/en/database

origodb.com/docs

docs.snowflake.net/manuals/index.html

Developer

Chris Davis

Oracle

Robert Friberg et al

Snowflake Computing Inc.

Initial release

2006

1980

2009

under the name LiveDB

2014

Current release

23c, September 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

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

Python

C and C++

Server operating systems

Linux
Unix

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

Linux
Windows

hosted

Data scheme

yes

Schemaless in JSON and XML columns

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

Numeric data only

yes

User defined using .NET types and collections

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

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

HTTP API
Sockets

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

Supported programming languages

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

.Net

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

yes

user defined functions

Triggers

yes

Domain Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

horizontal partitioning

client side managed; servers are not synchronized

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

yes

Transaction concepts

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

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

Durability

Support for making data persistent

yes

Write ahead log

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'

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role based authorization

Users with fine-grained authorization concept, user roles and pluggable authentication

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.