StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Databases
  5. Oracle vs Scylla

Oracle vs Scylla

OverviewDecisionsComparisonAlternatives

Overview

Oracle
Oracle
Stacks2.6K
Followers1.8K
Votes113
ScyllaDB
ScyllaDB
Stacks143
Followers197
Votes8

Oracle vs Scylla: What are the differences?

Introduction

In this article, we will explore the key differences between Oracle and Scylla databases. Oracle is a widely used relational database management system (RDBMS), while Scylla is a highly scalable NoSQL database. Let's dive into the differences between these two databases.

  1. Data Model: Oracle is a relational database that organizes data into tables with predefined schemas and enforces relationships between tables using foreign keys. On the other hand, Scylla is based on Apache Cassandra and follows a wide-column NoSQL data model. It uses a flexible schema allowing variable fields and denormalization to achieve high performance.

  2. Scalability: Oracle is designed to run on a single server and can vertically scale by adding more resources to the existing server. However, Scylla is designed to be massively scalable, allowing horizontal scaling by adding more commodity servers to the cluster. It leverages a distributed architecture and consistent hashing to distribute data across multiple nodes.

  3. Performance: Oracle is known for its robustness and feature richness, providing excellent performance for transactional workloads. It supports various indexing options, query optimization, and parallel processing. On the other hand, Scylla offers extreme performance for big data and high-velocity workloads. It is optimized for write-heavy operations and can handle millions of operations per second.

  4. Fault Tolerance: Oracle provides built-in fault tolerance mechanisms such as data replication, clustering, and failover options to ensure high availability. It supports various backup and recovery options to protect data in case of failures. In contrast, Scylla is designed with fault tolerance in mind from the ground up. It uses a distributed architecture with replication across multiple nodes, ensuring data durability and availability even in the face of node failures.

  5. Data Consistency: Oracle emphasizes strong data consistency by enforcing ACID (Atomicity, Consistency, Isolation, Durability) properties. It supports transactions with strict atomicity and isolation guarantees. Scylla, being a NoSQL database, offers tunable consistency levels. It provides eventual consistency by default, but allows users to choose stronger consistency levels when needed. This trade-off allows for higher availability and faster performance at the cost of relaxing strict consistency guarantees.

  6. Cost: Oracle is a commercially licensed database that requires substantial licensing and maintenance costs, especially for enterprise-level deployments. Scylla, on the other hand, offers a community edition that is free to use and an enterprise edition that offers advanced features and support at a fraction of the cost compared to Oracle.

In summary, Oracle is a mature and feature-rich RDBMS with a strong emphasis on data integrity, while Scylla is a highly scalable NoSQL database optimized for big data and high-velocity workloads. Their differences lie in data models, scalability, performance, fault tolerance, data consistency, and cost.

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)
or
Manual

Advice on Oracle, ScyllaDB

Tom
Tom

CEO at Gentlent

Jun 9, 2020

Decided

The Gentlent Tech Team made lots of updates within the past year. The biggest one being our database:

We decided to migrate our #PostgreSQL -based database systems to a custom implementation of #Cassandra . This allows us to integrate our product data perfectly in a system that just makes sense. High availability and scalability are supported out of the box.

387k views387k
Comments
Daniel
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.

495k views495k
Comments
Vinay
Vinay

Head of Engineering

Sep 19, 2019

Needs advice

The problem I have is - we need to process & change(update/insert) 55M Data every 2 min and this updated data to be available for Rest API for Filtering / Selection. Response time for Rest API should be less than 1 sec.

The most important factors for me are processing and storing time of 2 min. There need to be 2 views of Data One is for Selection & 2. Changed data.

174k views174k
Comments

Detailed Comparison

Oracle
Oracle
ScyllaDB
ScyllaDB

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.

ScyllaDB is the database for data-intensive apps that require high performance and low latency. It enables teams to harness the ever-increasing computing power of modern infrastructures – eliminating barriers to scale as data grows.

-
High availability; horizontal scalability; vertical scalability; Cassandra compatible; DynamoDB compatible; wide column; NoSQL; lightweight transactions; change data capture; workload prioritization; shard-per-core; IO scheduler; self-tuning
Statistics
Stacks
2.6K
Stacks
143
Followers
1.8K
Followers
197
Votes
113
Votes
8
Pros & Cons
Pros
  • 44
    Reliable
  • 33
    Enterprise
  • 15
    High Availability
  • 5
    Hard to maintain
  • 5
    Expensive
Cons
  • 14
    Expensive
Pros
  • 2
    Replication
  • 1
    Fewer nodes
  • 1
    High performance
  • 1
    Written in C++
  • 1
    High availability
Integrations
No integrations available
KairosDB
KairosDB
Wireshark
Wireshark
JanusGraph
JanusGraph
Grafana
Grafana
Hackolade
Hackolade
Prometheus
Prometheus
Kubernetes
Kubernetes
Datadog
Datadog
Kafka
Kafka
Apache Spark
Apache Spark

What are some alternatives to Oracle, ScyllaDB?

MongoDB

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

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

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

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

SQLite

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

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

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

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

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

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

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase