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. Noms vs Scylla

Noms vs Scylla

OverviewDecisionsComparisonAlternatives

Overview

Noms
Noms
Stacks3
Followers24
Votes0
GitHub Stars7.4K
Forks267
ScyllaDB
ScyllaDB
Stacks143
Followers197
Votes8

Noms vs Scylla: What are the differences?

# Introduction

1. **Data Model**: Noms utilizes a content-addressable data model, where each piece of data is uniquely identified by its content hash. On the other hand, Scylla follows a more traditional key-value data model, where data is stored and retrieved based on a primary key.

2. **Consistency**: Noms supports write-once semantics, ensuring that data is immutable once it is written. In contrast, Scylla offers tunable consistency levels, providing flexibility in balancing consistency and availability based on the application's requirements.

3. **Query Language**: Noms utilizes a graph-based query language called NomsQL, which allows for expressive queries on the data graph. Scylla, on the other hand, supports CQL (Cassandra Query Language), a SQL-like language for querying the data stored in the database.

4. **Partitioning**: Noms uses a sharding mechanism to partition data across multiple storage nodes, enabling horizontal scalability. Scylla employs a similar partitioning strategy but leverages consistent hashing for distributing data evenly across nodes.

5. **Indexing**: Noms uses indexes for efficient data retrieval and management, supporting both primary and secondary indexes. Scylla also supports indexing for faster data access, with wide-column indexes available for querying specific data columns efficiently.

6. **Consensus Algorithm**: Noms employs a unique consensus algorithm called RON (Replicated Object Notation) for handling concurrent updates and ensuring data consistency across replicas. In contrast, Scylla relies on the Paxos or Raft consensus protocols for achieving distributed consensus and maintaining data integrity.

In Summary, Noms and Scylla differ in data model, consistency, query language, partitioning strategy, indexing mechanism, and consensus algorithm.

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 Noms, 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
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

Noms
Noms
ScyllaDB
ScyllaDB

Noms is a new database that makes it easy to store, move, and collaborate on large-scale structured data. Noms gives you the entire Git workflow, but for large-scale structured (or unstructured) data. Fork, merge, track history, efficiently synchronize changes, etc.

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
GitHub Stars
7.4K
GitHub Stars
-
GitHub Forks
267
GitHub Forks
-
Stacks
3
Stacks
143
Followers
24
Followers
197
Votes
0
Votes
8
Pros & Cons
No community feedback yet
Pros
  • 2
    Replication
  • 1
    Written in C++
  • 1
    High availability
  • 1
    High performance
  • 1
    Distributed
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 Noms, 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