Topic
Postgres
Learn Postgres as a connected topic across chapters, concepts, simulations, and interview reasoning.
10 Concepts11 Articles4h 34m
Overview
Learn Postgres as a connected topic across chapters, concepts, simulations, and interview reasoning.
How this topic helps
System Design
Databases
Distributed Systems
Sql
Learning Path in this Topic
Series that contain articles from Postgres. Select a path to filter the article list.
Articles
11 matched articles
Article 1System Design HLD Example: Hotel Booking System (Airbnb)TLDR: A robust hotel booking system must guarantee atomicity in inventory subtraction. The core trade-off is Consistency vs. Availability: we prioritize strong consistency for the booking path (Postgr15 min
Article 2System Design HLD Example: URL Shortener (TinyURL and Bitly)TLDR: A URL shortener is a read-heavy system (100:1 ratio) that maps long URLs to short, unique aliases. The core scaling challenge is generating unique IDs without database contention—solved using a 19 minArticle 3Azure 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 4How CDC Works Across Databases: PostgreSQL, MySQL, MongoDB, and BeyondA data engineering team at a fintech company built what they believed was a robust Change Data Capture pipeline: three source databases (PostgreSQL, MongoDB, and Cassandra), Debezium connectors wired 37 minArticle 5SQL Partitioning: Range, Hash, List, and Composite Strategies ExplainedTLDR: SQL partitioning divides one logical table into smaller physical child tables, all accessed through the parent table name. The query optimizer skips irrelevant child tables entirely — a process 25 min
Article 6ACID Properties Explained: How SQL Databases Guarantee Atomicity, Consistency, Isolation, and DurabilityTLDR: ACID is four orthogonal guarantees that every SQL transaction must provide. Atomicity says all-or-nothing: PostgreSQL implements it via WAL rollback; MySQL InnoDB via undo logs. Consistency says38 minPage 1 of 2