Low Level Design: MVCC Database Concurrency Control
Multi-Version Concurrency Control (MVCC) is the concurrency mechanism used by PostgreSQL, MySQL InnoDB, Oracle, and most modern databases to enable […]
Multi-Version Concurrency Control (MVCC) is the concurrency mechanism used by PostgreSQL, MySQL InnoDB, Oracle, and most modern databases to enable […]
OAuth2 is an authorization framework that allows users to grant third-party applications limited access to their accounts without sharing passwords.
GraphQL is a query language for APIs where clients specify exactly the data they need and receive nothing more. Unlike
Geo-spatial indexing enables efficient queries on geographic data: finding restaurants within 1km, matching drivers to riders within 500m, showing events
WebSocket provides full-duplex, low-latency communication between a browser and server over a single persistent TCP connection. Unlike HTTP polling (client
Full-text search finds documents matching natural language queries across large corpora. Unlike exact-match database queries (WHERE name = ‘foo’), full-text
gRPC is a high-performance RPC framework built on HTTP/2 and Protocol Buffers. It provides strongly-typed service contracts, efficient binary serialization,
An audit log records a tamper-evident, chronologically ordered history of all significant actions in a system: who did what, when,
A real-time leaderboard ranks users or entities by a score that updates continuously. The core challenge is serving low-latency rank
Zero-downtime deployment updates production services without dropping user requests. Modern techniques — rolling updates, blue-green deployments, and canary releases —
SLIs (Service Level Indicators), SLOs (Service Level Objectives), and error budgets are the quantitative framework for reliability engineering. An SLI
Feature flags (feature toggles) decouple code deployment from feature release. Code ships to production with a feature disabled; the flag
Apache Kafka is a distributed event streaming platform built around a partitioned, replicated, append-only log. Understanding Kafka internals — partitioning
Write-heavy systems must sustain high write throughput without overwhelming the storage layer. Techniques include write batching, asynchronous writes, write coalescing,
Read-heavy systems serve many more reads than writes — often 100:1 or higher ratios. Optimizing for reads requires layered caching,