DBMS > Amazon Redshift vs. EJDB vs. Oracle vs. SiteWhere

System Properties Comparison Amazon Redshift vs. EJDB vs. Oracle vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Widely used RDBMS

M2M integration platform for persisting/querying time series data

Primary database model

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	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

aws.amazon.com/redshift

github.com/Softmotions/ejdb

www.oracle.com/database

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/redshift

github.com/Softmotions/ejdb/blob/master/README.md

docs.oracle.com/en/database

sitewhere1.sitewhere.io/index.html

Developer

Amazon (based on PostgreSQL)

Softmotions

Oracle

SiteWhere

Initial release

2012

1980

2010

Current release

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

restricted free version is available

Open Source

Common Public Attribution License Version 1.0

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

C and C++

Java

Server operating systems

hosted

server-less

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

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

predefined scheme

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

in-process shared library

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

user defined functions

in Python

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

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

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

typically not needed, however similar functionality with collection joins possible

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

Read/Write 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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.