#Scalability
Articles about Scalability — exploring patterns, best practices, and real-world implementations in production systems.
6 posts tagged with scalability. ← Blog home
The capstone — one problem, a home-timeline feed, designed the whole way through with the method from post one: clarify, estimate, contract, then high-level to deep-dive to bottleneck, naming the trade-off at every step and drawing on all seven earlier posts.
The capstone: one worked design end to end — requirements, estimation, API and data model, high-level architecture, and deep dives applying the whole series (scaling, caching, sharding, consistency, async, reliability) with explicit trade-offs.
How systems grow under load — vertical vs horizontal scaling, why statelessness is the real enabler, load balancing from L4 to L7, consistent hashing, read/write scaling, the scale cube, and when the honest answer is "don't scale yet."
How systems grow: vertical vs horizontal scaling, statelessness as the enabler of horizontal scale, load balancing (L4/L7, consistent hashing), read/write scaling with replicas — and knowing when not to scale.
A repeatable method for designing systems and acing the design interview — clarify requirements, estimate on the back of an envelope, pin down the API and data model, then work high-level to deep-dive to bottleneck, always naming the trade-off.
The opener to a system-design series: a repeatable method rather than a grab-bag of components — clarifying functional vs non-functional requirements, back-of-the-envelope estimation with the latency numbers every engineer should know, and the trade-off-driven design flow.
Graph neural networks look clean on paper and get messy in production, because training on graphs breaks assumptions that ordinary deep learning takes for granted. The data points aren't independent, the graph may not fit in memory, and the model fails in graph-specific ways. This post covers the practical realities of making GNNs actually work at scale — the problems you'll hit and the techniques that address them.
GNNs look clean on paper and get messy in production because the data points aren't independent. Why mini-batching and train/test splitting break on graphs (leakage through edges), how sampling scales GNNs to huge graphs, and the graph-specific failure modes (over-smoothing, over-squashing, homophily) that shape real systems.
The graph convolutional network has two problems that make it impractical for real systems: it can't handle new nodes, and it needs the whole graph in memory at once. GraphSAGE fixes both with one shift in perspective — learn a reusable function that builds a node's embedding from a sample of its neighbors, rather than learning a fixed embedding per node. This is the idea that made GNNs usable on billion-node industrial graphs, and it's why most production GNNs are GraphSAGE-style.
The GCN can't handle new nodes and needs the whole graph in memory. GraphSAGE fixes both: learn a reusable function that builds an embedding from a sample of neighbors, rather than a fixed per-node vector. Inductive learning and neighbor sampling — the ideas that made GNNs work on billion-node industrial graphs.
Simple stream operations — filter this event, transform that one — need no memory. But the interesting computations — counts, aggregations, joins, windows, pattern detection — require remembering things across events, and that memory is state. Managing state correctly over an unbounded stream, at scale, with fault tolerance, is the hardest engineering problem in stream processing. This post is about state: why it's needed, what makes it hard, and how stream processors manage it.
Interesting stream computations — counts, aggregations, joins, windows, patterns — need to remember across events, and that memory is state. Why state is hard on an unbounded stream (bounding, speed, partitioning, surviving failure), and how engines provide managed keyed state.
All posts on this site are written by Pratik Dhanave, an Agentic AI Architect with 7+ years building production distributed systems, multi-agent AI platforms, and cloud-native infrastructure. About the author → Each article includes working code, architecture diagrams, and references to the specific frameworks and standards discussed. Browse the blog or explore related topics using the tag cloud above.