--- title: Building for the Scale You Imagine, Not the Scale You Have description: A cautionary tale about over-engineering infrastructure before validating actual scale needs. With 400k rows, plain Postgres answered analytics queries in... canonical: https://daily.dev/posts/building-for-the-scale-you-imagine-not-the-scale-you-have-lld4ftn7x twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Building for the Scale You Imagine, Not the Scale You Have | daily.dev og:description: A cautionary tale about over-engineering infrastructure before validating actual scale needs. With 400k rows, plain Postgres answered analytics queries in... og:url: https://daily.dev/posts/building-for-the-scale-you-imagine-not-the-scale-you-have-lld4ftn7x og:image: https://api.daily.dev/og/posts/lld4ftn7X.png og:image:alt: Building for the Scale You Imagine, Not the Scale You Have og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Building for the Scale You Imagine, Not the Scale You Have **[kaypee](https://daily.dev/sources/mwp4epfm53lshghtnqv5h)** · [@gkpc2004](https://daily.dev/gkpc2004) · 2 min read · 1 upvotes · 0 comments ## Summary A cautionary tale about over-engineering infrastructure before validating actual scale needs. With 400k rows, plain Postgres answered analytics queries in milliseconds — no ClickHouse, Kafka, or Kubernetes required. The post argues that early-stage teams routinely pattern-match problem types to heavyweight tools (OLAP→ClickHouse, search→Elasticsearch, scale→Kubernetes) before measuring real bottlenecks. The hidden costs are financial, cognitive, and velocity-related. The full article covers what was built with Postgres instead, the three hidden costs of premature infra, and when reaching for heavy tooling early is actually justified. ## Content "This is an OLAP problem, so we need ClickHouse." That sentence almost cost me two databases I didn't need. 400k users. Analytics dashboards. I sketched the whole stack in minutes — Kafka streaming events into ClickHouse, dashboards reading from it. Clean. Scalable. The kind of diagram that looks like a company that's going to make it. Then I did the math I should've done first: 400k rows is tens of megabytes. Postgres answers those queries in single-digit milliseconds. I wasn't solving a bottleneck. I was building for one I had imagined and never measured. And this is the trap I see early-stage teams fall into again and again: Analytics? ClickHouse. Search? Elasticsearch. Scale? Kubernetes. Events? Kafka. We pattern-match a problem type to a fancy tool — and adopt it before we've confirmed we even have the problem. It never feels like a mistake. It feels responsible. You're "building for scale." But every box on that diagram is a bill you haven't read: → money spent before there's a workload to justify it → cognitive load every engineer now carries forever → velocity you quietly lose to complexity that was never load-bearing The future you're building for is a hypothesis. Your current bottlenecks are data. Most teams provision for the hypothesis and ignore the data. I wrote up the full story — what I built instead with plain Postgres, the three hidden costs, and (importantly) when reaching for the heavy tool early actually IS the right call. If you've ever added infra "for when we scale" — this one's for you. Link in comments 👇 👉[Read the Full Article](https://0toscale.hashnode.dev/building-for-the-scale-you-imagine-not-the-scale-you-have) #softwarearchitecture #systemdesign #postgresql #startups #engineering ## Similar posts on daily.dev - [You can outgrow vanilla Postgres without abandoning Postgres](https://daily.dev/posts/you-can-outgrow-vanilla-postgres-without-abandoning-postgres-inzvfgbdt) · The New Stack · 2 upvotes · 0 comments - [Just Use Postgres](https://daily.dev/posts/just-use-postgres-ueffslq3a) · Lobsters · 0 upvotes · 0 comments - [ClickHouse vs PostgreSQL: Choosing the Right Database for Analytics](https://daily.dev/posts/clickhouse-vs-postgresql-choosing-the-right-database-for-analytics-ckxz2ek9o) · BigData Boutique blog · 3 upvotes · 0 comments - [How Polymarket scaled their data stack with Postgres and ClickHouse](https://daily.dev/posts/how-polymarket-scaled-their-data-stack-with-postgres-and-clickhouse-nktowolld) · ClickHouse · 3 upvotes · 0 comments --- Tags: [#startup](https://daily.dev/tags/startup), [#career](https://daily.dev/tags/career), [#postgresql](https://daily.dev/tags/postgresql), [#clickhouse](https://daily.dev/tags/clickhouse) [View this post on daily.dev](https://daily.dev/posts/building-for-the-scale-you-imagine-not-the-scale-you-have-lld4ftn7x) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/building-for-the-scale-you-imagine-not-the-scale-you-have-lld4ftn7x","headline":"Building for the Scale You Imagine, Not the Scale You Have","text":"A cautionary tale about over-engineering infrastructure before validating actual scale needs. With 400k rows, plain Postgres answered analytics queries in milliseconds — no ClickHouse, Kafka, or Kubernetes required. The post argues that early-stage teams routinely pattern-match problem types to heavyweight tools (OLAP→ClickHouse, search→Elasticsearch, scale→Kubernetes) before measuring real bottlenecks. The hidden costs are financial, cognitive, and velocity-related. The full article covers what was built with Postgres instead, the three hidden costs of premature infra, and when reaching for heavy tooling early is actually justified.","url":"https://daily.dev/posts/building-for-the-scale-you-imagine-not-the-scale-you-have-lld4ftn7x","datePublished":"2026-07-16T19:07:43.209Z","dateModified":"2026-09-13T21:13:25.152Z","author":{"@type":"Person","name":"kaypee","url":"https://daily.dev/gkpc2004","image":"https://media.daily.dev/image/upload/s--YCs2nSOm--/f_auto/v1784200192/avatars/avatar_mWP4EPfM53lSHgHTNQv5h?_a=BAMAMicg0","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":20}},"image":"https://media.daily.dev/image/upload/s--08AGKbo_--/f_auto/v1784228864/posts/lld4ftn7X?_a=BAMAMicg0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/sources/mwp4epfm53lshghtnqv5h","name":"kaypee"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"kaypee","item":"https://daily.dev/sources/mwp4epfm53lshghtnqv5h"},{"@type":"ListItem","position":3,"name":"Building for the Scale You Imagine, Not the Scale You Have"}]} ```