Topic
Nosql
Learn Nosql as a connected topic across chapters, concepts, simulations, and interview reasoning.
10 Concepts11 Articles4h 7m
Overview
Learn Nosql as a connected topic across chapters, concepts, simulations, and interview reasoning.
How this topic helps
System Design
Databases
Distributed Systems
Cassandra
Learning Path in this Topic
Series that contain articles from Nosql. Select a path to filter the article list.
Articles
11 matched articles
Article 1NoSQL Partitioning: How Cassandra, DynamoDB, and MongoDB Split DataTLDR: Every NoSQL database hides a partitioning engine behind a deceptively simple API. Cassandra uses a consistent hashing ring where a Murmur3 hash of your partition key selects a node — virtual nod24 min
Article 2Partitioning Approaches in SQL and NoSQL: Horizontal, Vertical, Range, Hash, and List PartitioningTLDR: Partitioning splits one logical table into smaller physical pieces. The database skips irrelevant pieces entirely — turning a 30-second full-table scan into a sub-second single-partition read. S12 min
Article 3Sharding Approaches in SQL and NoSQL: Range, Hash, and Directory-Based Strategies ComparedTLDR: Sharding splits your database across multiple physical nodes so no single machine carries all the data or absorbs all the writes. The strategy you choose — range, hash, consistent hashing, or di29 minArticle 4Database Anomalies: How SQL and NoSQL Handle Dirty Reads, Phantom Reads, and Write SkewTLDR: Database anomalies are the predictable side-effects of concurrent transactions — dirty reads, phantom reads, write skew, and lost updates. SQL databases use MVCC and isolation levels to prevent 31 minArticle 5Azure Cosmos DB API Modes Explained: NoSQL, MongoDB, Cassandra, PostgreSQL, Gremlin, and TableTLDR: Cosmos DB's six API modes are wire-protocol compatibility layers over one shared ARS storage engine — except PostgreSQL (Citus), which is genuinely different. Every API emulates its native datab24 minArticle 6The Dual Write Problem in NoSQL: MongoDB, DynamoDB, and CassandraTLDR: NoSQL databases trade cross-entity atomicity for scale — and every database draws that atomicity boundary in a different place. MongoDB's boundary is the document (pre-4.0) or the replica set (436 minPage 1 of 2