Oracle vs YugabyteDB

Overview

Oracle

Stacks2.6K

Followers1.8K

Votes113

YugabyteDB

Stacks50

Followers114

Votes1

GitHub Stars9.9K

Forks1.2K

Oracle vs YugabyteDB: What are the differences?

Introduction

In this article, we will be discussing the key differences between Oracle and YugabyteDB, two popular database management systems.

Storage and Scale: Oracle is primarily a traditional relational database management system (RDBMS) designed for on-premises deployment, while YugabyteDB is a distributed SQL database designed for cloud-native and containerized environments. Oracle relies on a single-server architecture, while YugabyteDB can horizontally scale across multiple servers. This allows YugabyteDB to handle high traffic and large datasets more effectively.
ACID Compliance: Oracle has a strong focus on ACID (Atomicity, Consistency, Isolation, Durability) compliance, making it suitable for transactional workloads. YugabyteDB also offers full ACID compliance but with a different approach. It utilizes a distributed consensus protocol called Raft to ensure consistency across replicas, providing strong consistency guarantees even in a distributed environment.
Multi-Cloud Support: YugabyteDB is designed to support multi-cloud deployments, allowing users to leverage different cloud providers simultaneously. It provides built-in data replication across multiple availability zones and regions, ensuring high availability and reliability. Oracle, on the other hand, primarily supports on-premises or single-cloud deployments, although it offers options for cloud integration.
Data Model Support: Oracle follows a fixed-schema data model, meaning you need to define the schema upfront before storing data. In contrast, YugabyteDB supports both fixed-schema and flexible-schema approaches. It offers support for JSON and document-like data structures, making it more flexible for modern application development.
Open Source vs Proprietary: YugabyteDB is an open-source database and provides community and enterprise editions. The community edition is free to use and modify, while the enterprise edition offers additional features and support. Oracle, on the other hand, is a proprietary database system with commercial licensing options.
Datacenter and Availability: Oracle has a traditional, centralized design where all data is stored in one datacenter. While it offers replication across multiple servers for high availability, failure of the main datacenter can still cause severe downtime. YugabyteDB, being a distributed database, can replicate data across multiple datacenters and regions, ensuring better fault tolerance and disaster recovery capabilities.

In summary, Oracle is a traditional RDBMS focused on on-premises and single-cloud deployments, while YugabyteDB is a distributed SQL database designed for cloud-native, containerized environments, offering multi-cloud support, better scalability, ACID compliance, and schema flexibility.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Oracle, YugabyteDB

Daniel

Data Engineer at Dimensigon

Jul 18, 2020

Decided

We have chosen Tibero over Oracle because we want to offer a PL/SQL-as-a-Service that the users can deploy in any Cloud without concerns from our website at some standard cost. With Oracle Database, developers would have to worry about what they implement and the related costs of each feature but the licensing model from Tibero is just 1 price and we have all features included, so we don't have to worry and developers using our SQLaaS neither. PostgreSQL would be open source. We have chosen Tibero over Oracle because we want to offer a PL/SQL that you can deploy in any Cloud without concerns. PostgreSQL would be the open source option but we need to offer an SQLaaS with encryption and more enterprise features in the background and best value option we have found, it was Tibero Database for PL/SQL-based applications.

496k views496k

Comments

Abigail

Dec 6, 2019

Decided

In the field of bioinformatics, we regularly work with hierarchical and unstructured document data. Unstructured text data from PDFs, image data from radiographs, phylogenetic trees and cladograms, network graphs, streaming ECG data... none of it fits into a traditional SQL database particularly well. As such, we prefer to use document oriented databases.

MongoDB is probably the oldest component in our stack besides Javascript, having been in it for over 5 years. At the time, we were looking for a technology that could simply cache our data visualization state (stored in JSON) in a database as-is without any destructive normalization. MongoDB was the perfect tool; and has been exceeding expectations ever since.

Trivia fact: some of the earliest electronic medical records (EMRs) used a document oriented database called MUMPS as early as the 1960s, prior to the invention of SQL. MUMPS is still in use today in systems like Epic and VistA, and stores upwards of 40% of all medical records at hospitals. So, we saw MongoDB as something as a 21st century version of the MUMPS database.

540k views540k

Comments

Abigail

Dec 10, 2019

Decided

We wanted a JSON datastore that could save the state of our bioinformatics visualizations without destructive normalization. As a leading NoSQL data storage technology, MongoDB has been a perfect fit for our needs. Plus it's open source, and has an enterprise SLA scale-out path, with support of hosted solutions like Atlas. Mongo has been an absolute champ. So much so that SQL and Oracle have begun shipping JSON column types as a new feature for their databases. And when Fast Healthcare Interoperability Resources (FHIR) announced support for JSON, we basically had our FHIR datalake technology.

558k views558k

Comments

Detailed Comparison

Oracle	YugabyteDB
Oracle Database is an RDBMS. An RDBMS that implements object-oriented features such as user-defined types, inheritance, and polymorphism is called an object-relational database management system (ORDBMS). Oracle Database has extended the relational model to an object-relational model, making it possible to store complex business models in a relational database.	An open-source, high-performance, distributed SQL database built for resilience and scale. Re-uses the upper half of PostgreSQL to offer advanced RDBMS features, architected to be fully distributed like Google Spanner.
-	Resilience; High Performance; Scalability; Enterprise Grade; Cloud-native; Kubernetes; PostgreSQL-compatible; Geo-Distributed; Hybrid Cloud
Statistics
GitHub Stars -	GitHub Stars 9.9K
GitHub Forks -	GitHub Forks 1.2K
Stacks 2.6K	Stacks 50
Followers 1.8K	Followers 114
Votes 113	Votes 1
Pros & Cons
Pros 44 Reliable 33 Enterprise 15 High Availability 5 Hard to maintain 5 Expensive Cons 14 Expensive	Pros 1 Compatible with the result of pg_dump
Integrations
No integrations available	Golang PHP Java Python Spring Boot Apache Spark Node.js C# Kubernetes Ruby

What are some alternatives to Oracle, YugabyteDB?

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

Related Comparisons

Oracle vs YugabyteDB: What are the differences?

Introduction

In this article, we will be discussing the key differences between Oracle and YugabyteDB, two popular database management systems.

Storage and Scale: Oracle is primarily a traditional relational database management system (RDBMS) designed for on-premises deployment, while YugabyteDB is a distributed SQL database designed for cloud-native and containerized environments. Oracle relies on a single-server architecture, while YugabyteDB can horizontally scale across multiple servers. This allows YugabyteDB to handle high traffic and large datasets more effectively.
ACID Compliance: Oracle has a strong focus on ACID (Atomicity, Consistency, Isolation, Durability) compliance, making it suitable for transactional workloads. YugabyteDB also offers full ACID compliance but with a different approach. It utilizes a distributed consensus protocol called Raft to ensure consistency across replicas, providing strong consistency guarantees even in a distributed environment.
Multi-Cloud Support: YugabyteDB is designed to support multi-cloud deployments, allowing users to leverage different cloud providers simultaneously. It provides built-in data replication across multiple availability zones and regions, ensuring high availability and reliability. Oracle, on the other hand, primarily supports on-premises or single-cloud deployments, although it offers options for cloud integration.
Data Model Support: Oracle follows a fixed-schema data model, meaning you need to define the schema upfront before storing data. In contrast, YugabyteDB supports both fixed-schema and flexible-schema approaches. It offers support for JSON and document-like data structures, making it more flexible for modern application development.
Open Source vs Proprietary: YugabyteDB is an open-source database and provides community and enterprise editions. The community edition is free to use and modify, while the enterprise edition offers additional features and support. Oracle, on the other hand, is a proprietary database system with commercial licensing options.
Datacenter and Availability: Oracle has a traditional, centralized design where all data is stored in one datacenter. While it offers replication across multiple servers for high availability, failure of the main datacenter can still cause severe downtime. YugabyteDB, being a distributed database, can replicate data across multiple datacenters and regions, ensuring better fault tolerance and disaster recovery capabilities.

Oracle vs YugabyteDB

Overview

Oracle vs YugabyteDB: What are the differences?