APAbhinav Prakashinblog.iamabhinav.dev·19h ago · 19 min readHow to design a scalable DB SchemaI used to think database design was mostly about knowing SQL. You know: CREATE TABLE users (...); CREATE TABLE posts (...); Then add a few foreign keys, write some joins, and you're done. But after d00
Sspipaliya8insudhirpipaliya.hashnode.dev·Jul 21 · 6 min readThe Hidden Danger of MAX()+1 Logic in Enterprise ApplicationsGenerating the next number using MAX() + 1 is one of the most common approaches developers use when creating custom identifiers. At first glance, the logic looks simple and perfectly valid: var maxZid00
PDPriyansh Dimriinpriyanshdimri.hashnode.dev·Jul 21 · 5 min readWhy GistDB Stops Optimizing EarlyMost query optimizers sit somewhere between two extremes. One extreme applies very few optimizations. Every scan reads every column, predicates stay where they were written, and joins are not reordere10
SUSamuel Umohinumohsg.hashnode.dev·Jul 21 · 18 min readHorizontally Scaling PostgreSQL: Database Sharding with CitusA practical guide to scaling your database infrastructure horizontally. Learn how to shard your data, optimize query routing, and build a distributed multi-tenant architecture using Postgres, Citus an00
SGSergio González Téllezinevankhandev.hashnode.dev·Jul 15 · 2 min readWhy can someone use SQL for years and still never truly understand databases?SEED-009 PROBLEM Why can someone use SQL for years and still never truly understand databases? INSIGHT SQL queries can be learned relatively quickly; the real value for Operations, Infrastructure, a00
SGSergio González Téllezinevankhandev.hashnode.dev·Jul 13 · 2 min readWhy does an apparently simple optimization often become a system’s first real architectural decision?SEED-008 PROBLEM Why does an apparently simple optimization often become a system’s first real architectural decision? INSIGHT In SQL, indexes are one of the first places where a real architectural 10
RMRavi Mistryinravimistry.hashnode.dev·Jul 8 · 14 min readTrade-Offs in Data Systems ArchitectureWhat are Trade-Offs? - Trade-offs are the choices where improving one thing often means giving up or reducing something else. In system design, there is rarely a perfect solution - every decision has 00
SKShubham Kumaringodleon.hashnode.dev·Jun 13 · 12 min readDesigning a Library Management System — LLD - Database Schema DesignOn the surface, it sounds easy — "books, members, borrow, return." But once you start digging in, you'll find it touches almost every core schema-design concept: many-to-many relationships, soft busin00
ASArian Seyediinadv-frontend.hashnode.dev·Jun 11 · 3 min readEmbedded vs Referenced in MongoDB: How to Choose the Right Relationship Every TimeEvery MongoDB developer eventually faces the same question: Should I embed this data or create a reference? At first, the answer seems simple. MongoDB is a document database, so embedding everything s00
EDEric Davidinericdaviddev.hashnode.dev·Jun 9 · 8 min readDesigning Idempotent Payment Ingestion WorkflowsIn the first BillingTracker post, I focused on the relational foundation: tenants, source systems, external identifiers, payments, ingestion runs, errors, and sync state. The next step was proving tha00
