How deeply does ScyllaDB in Action cover BASE?

Defines the acronym and explains its consistency trade-off, then connects it to request levels without detailing replica internals.

BASE

As explained in ScyllaDB in Action

BASE is a distributed-systems consistency model characterized by basic availability, soft state, and eventual consistency.

BASE is a distributed-systems consistency model built around basic availability, soft state, and eventual consistency. Instead of guaranteeing ACID-level correctness after every write, it favors availability and faster writes, allowing replicas to converge over time. section 1.2.2 section 1.4

In ScyllaDB, BASE supports a cluster that remains useful when nodes fail. Developers can tune request consistency: ONE needs one responding node, QUORUM needs a majority, and ALL needs every node, balancing availability against correctness. section 1.4 section 1.2.2

A node failure

When a node crashes, ScyllaDB can continue serving requests through other nodes and later stream data to recover the cluster. Reads and writes may therefore favor availability before all replicas agree. section 1.4

How ScyllaDB in Action covers it

liveBook manning.com

Read ScyllaDB in Action on liveBook Get the book at manning.com

Related concepts

ACIDcontrasts with · ACID is the set of database transaction properties—atomicity, consistency, isolation, and durability—that characterize reliable transactional behavior.
NoSQL databaseused by · A NoSQL database is a database system organized primarily around nonrelational data models or access patterns rather than relational tables.
eventual consistencyimplements · Eventual consistency is a distributed-data consistency model that allows replicas to differ temporarily but guarantees they converge to a consistent state after updates propagate, typically when no further updates occur.
ScyllaDBcontrasts with · ScyllaDB is a distributed wide-column database compatible with Cassandra’s data model and protocol, designed for high scalability and availability.

This explainer was generated by Manning's knowledge graph from the text of ScyllaDB in Action. The section links point to the parts of the book it draws on.