Home/Learn/Sql Nosql
Topic

Sql Nosql

Learn Sql Nosql as a connected topic across chapters, concepts, simulations, and interview reasoning.

10 Concepts10 Articles3h 52m

Overview

Learn Sql Nosql as a connected topic across chapters, concepts, simulations, and interview reasoning.

How this topic helps

Nosql
Databases
System Design
Distributed Systems

Learning Path in this Topic

Series that contain articles from Sql Nosql. Select a path to filter the article list.

Articles

10 matched articles

Article 1Choosing the Right Database: CAP Theorem and Practical Use CasesTLDR: Database selection is a trade-off between consistency, availability, and scalability. By using the CAP Theorem as a compass and matching your data access patterns to the right storage engine (Re7 minArticle 2NoSQL 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 minArticle 3CosmosDB Partition Internals: Logical vs Physical Partitions Explained🔥 When Your Database Bill Triples Overnight A retail engineering team ships a flash-sale feature. Traffic spikes 10×. Their Azure CosmosDB bill triples within 24 hours. Queries that ran in 5ms now ta16 minArticle 4Partitioning 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 minArticle 5Sharding 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 6Database 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 min

Page 1 of 2