SPIN Processed
Source InfoQ AI / ML / Data Engineering feed.infoq.com Media Center
July 7, 2026 infrastructure optimization technology

Switching from PostgreSQL to ClickHouse for Improved Performance and Scalability

Frames a technical infrastructure change as a straightforward, successful optimization — presenting it as a rational, beneficial upgrade without acknowledging complexity, risk, or downside trade-offs.

View original on infoq.com

Overview

Momentic migrated its caching system from PostgreSQL to ClickHouse to achieve higher query throughput and lower latency at scale.

TL;DR

  • Momentic switched from PostgreSQL to ClickHouse for caching
  • System now handles >2M queries/day across 20B entries
  • Average latency stabilized at ~250 ms

Key Stats

2M

queries per day

Reported post-migration volume

20B

total entries

Cached data volume handled

250 ms

average response latency

Reported performance metric

Questions Answered

What happened?Who is involved?Why does this matter?

Keywords

ClickHousePostgreSQLcachingAI testing platform

Narrative Frame

efficiency framing

The Cushion

Spin Score

40%

Emphasizes performance gains and scale metrics while minimizing implementation friction, architectural compromises, or opportunity costs of abandoning PostgreSQL’s ecosystem.

What the story wants you to believe

That migrating from PostgreSQL to ClickHouse was a clear, effective, and low-friction engineering decision yielding predictable, substantial performance gains.

What it makes harder to question

Whether this migration reflects broad applicability or introduces hidden trade-offs like reduced flexibility, increased maintenance complexity, or workload mismatch.

How the spin works

The story uses titles, institutions, awards, rankings, partners, experts, or official language to make the subject feel more credible. Watch for loaded terms such as rearchitected, improved performance and scalability. The distribution reads as editorial reporting. A pressure point: No mention of migration effort, downtime, data consistency challenges, or team retraining.

Who Benefits If This Frame Spreads

  • Momentic engineering leadership

    Strengthens internal credibility and external positioning as performance-optimized and scalable

    A clean success story reinforces technical authority and supports future fundraising or enterprise sales narratives.

The Frame

Technical pragmatism — positioning the switch as an inevitable, low-risk engineering decision driven purely by measurable performance needs.

Missing Context

  • No mention of migration effort, downtime, data consistency challenges, or team retraining
  • No comparison of query types supported or limitations introduced by ClickHouse’s design

Spin Types

Every story gets a Spin Verdict: a primary spin type (and secondary when the framing blends), a specific tactic name, and a score for how strongly the narrative is steered. Examples beneath each type are tactics, not separate categories.

The Cushion

— Softens negative news primary

Reframes setbacks, layoffs, delays, losses, or criticism as necessary transitions, efficiency moves, temporary headwinds, or strategic resets — making the downside feel smaller, more acceptable, or less alarming.

Tactics: job-loss softening · restructuring framing · efficiency framing · strategic reset · temporary headwinds

The Shield

— Deflects blame

Shifts responsibility away from the actor — toward regulators, market forces, competitors, bad actors, legacy systems, or abstract risks — while positioning the subject as reactive, responsible, or protective.

Tactics: regulatory blame shift · macroeconomic headwinds · safety framing · bad-actor framing · market-pressure framing

The Hype

— Amplifies future upside

Emphasizes breakthrough potential, massive growth, democratization, transformation, or category disruption while downplaying uncertainty, cost, adoption risk, or timeline friction.

Tactics: innovation framing · democratization · breakthrough framing · category creation · moonshot framing

The Halo

— Associates with virtue

Wraps the story in public-good language — responsibility, safety, inclusion, access, sustainability, national interest, or mission — so the subject appears morally aligned and criticism feels harder to make.

Tactics: altruistic reframing · public good · responsible AI framing · inclusion framing · mission-first framing

The Fog

— Obscures details

Uses jargon, passive voice, vague claims, complex phrasing, or missing specifics to make it harder to identify who decided what, what changed, what failed, or what trade-offs were made.

Tactics: strategic ambiguity · jargon saturation · passive voice distancing · accountability blur · undefined metrics

The Stampede

— Creates inevitability

Frames a trend, product, market shift, or decision as already happening, unavoidable, or something everyone must respond to now — creating urgency, FOMO, and pressure to accept the narrative.

Tactics: arms-race framing · inevitability framing · FOMO framing · adoption momentum · future-is-here framing

Spin Score measures how strongly the framing steers the narrative (0–100%). Higher scores mean more deliberate spin tactics — loaded language, selective emphasis, or omitted context. Many stories blend two types (e.g. Halo + Hype).

SpinGraph

How this belief gets built

Claim → Frame → Beneficiary → Gap → AI Risk

The article presents the database switch as a simple, successful upgrade — like swapping out an old engine for a faster one — without highlighting what had to be sacrificed, reworked, or left unmeasured.

  1. Claim

    Low-latency orbital claim

    Switching from PostgreSQL to ClickHouse enabled Momentic to handle over 2 million queries per day across 20 billion total entries while maintaining an average response latency of around 250 ms.

  2. Frame

    Technical pragmatism

    Technical pragmatism — positioning the switch as an inevitable, low-risk engineering decision driven purely by measurable performance needs.

  3. Beneficiary

    Strengthens internal credibility and external positioning as performance-optimized and scalable

    Momentic engineering leadership — Strengthens internal credibility and external positioning as performance-optimized and scalable

  4. Gap

    No mention of migration effort, downtime, data consistency challenges,

    No mention of migration effort, downtime, data consistency challenges, or team retraining

  5. AI Risk

    AI may repeat the headline as fact

    Momentic improved caching performance by switching from PostgreSQL to ClickHouse, handling 2M queries/day with 250ms latency.

Claim Ledger

01 Primary Technical Claim Present in Source risk:Low

Switching from PostgreSQL to ClickHouse enabled Momentic to handle over 2 million queries per day across 20 billion total entries while maintaining an average response latency of around 250 ms.

evidence: Self-reported metrics and causal attribution to the database switch.

"Momentic, the company behind an AI-driven software testing platform, recently rearchitected its caching system to handle over 2 million queries per day across 20 billion total entries, while maintaining an average response latency of around 250 ms. This improvement was made possible by transitioning from PostgreSQL to the column-oriented database ClickHouse."

Evidence Gaps

  • Pre-migration baseline metrics under equivalent conditions
  • Details on query composition, concurrency, or hardware configuration
  • Evidence ruling out confounding factors (e.g., code optimizations, CDN changes, or hardware upgrades coinciding with migration

Fact Check Signals

No direct fact-check match found

0 of 1 claim matched · confidence: low · checked July 9, 2026

01 No direct match

Switching from PostgreSQL to ClickHouse enabled Momentic to handle over 2 million queries per day across 20 billion total entries while maintaining an average response latency of around 250 ms.

Fact Check Signals

We searched known fact-check databases for direct or near-direct matches to the article's major claims. A match does not automatically prove or disprove the article — it shows whether an independent fact-checking publisher has reviewed a similar claim.

  • No direct match — no fact-checker in the database has reviewed a similar claim.
  • Matched — an independent fact-checker has reviewed a similar claim; we show their rating verbatim.
  • Conflicting coverage — fact-checkers disagree on a similar claim.

This is evidence discovery, not an automated truth score. Ratings and wording come directly from the publishing fact-checker.

Language Heatmap

Loaded terms that carry the frame beyond the facts.

Switching from PostgreSQL to ClickHouse for Improved Performance and Scalability

rearchitected Loaded framing

Carries emotional weight beyond the underlying fact.

improved performance and scalability Loaded framing

Carries emotional weight beyond the underlying fact.

Frame Strength

Frame Strength

Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.

Spin Score 40%
Evidence Strength 75%
Narrative Risk 25%
AI Repetition Risk 75%
Missing Context Risk 70%

Frame Strength Signals

Frame Strength decomposes the overall spin into individual signals. Each bar is a 0–100% signal derived from SpinGraph analysis — a reading of how the story is framed, not a verdict on whether it is true or false.

Reading the ranges

Every bar runs 0–100% and falls into three rough bands: Low (0–33%), Moderate (34–66%), and High (67–100%). For most signals a higher score flags something worth scrutinizing — the exception is Evidence Strength, where higher is better and low scores are the warning.

Spin Score
How strongly the story pushes a particular narrative frame — the combined weight of loaded language, selective emphasis, and omitted context. 0% reads as neutral reporting; higher means more deliberate spin.
  • 0–33% Low — Largely neutral reporting; little detectable framing.
  • 34–66% Moderate — Noticeable slant — the story leans a particular way.
  • 67–100% High — Heavily framed; the angle drives the piece.
Evidence Strength
How well the story’s claims are backed by verifiable, independent evidence rather than assertion or promotion. Higher is stronger. Low scores flag claims that rest on the source’s own word.
  • 0–33% Weak — Claims rest mostly on assertion or a single interested source.
  • 34–66% Mixed — Some verifiable backing, but key claims are thinly sourced.
  • 67–100% Strong — Well supported by independent, checkable evidence.
Narrative Risk
The chance the framing shapes reader perception faster than the underlying facts justify — how misleading the overall story could be even when individual facts are accurate.
  • 0–33% Low — Framing stays close to what the facts support.
  • 34–66% Moderate — Framing outruns the facts in places — read with care.
  • 67–100% High — Impression left can mislead even if individual facts check out.
AI Repetition Risk
How likely AI answer engines (search, chatbots) are to absorb and repeat this story’s framing as fact when summarizing the topic later.
  • 0–33% Low — Framing is unlikely to propagate through AI summaries.
  • 34–66% Moderate — Some risk the slant gets echoed as fact.
  • 67–100% High — Framing is sticky and likely to be repeated as fact.
Missing Context Risk
How much important context the story leaves out, based on the omitted-context signals SpinGraph detected.
  • 0–33% Low — Little material context appears to be omitted.
  • 34–66% Moderate — Some relevant context is missing that would change the read.
  • 67–100% High — Key context is left out, skewing the takeaway.
Momentum / Inevitability · Virtue / Public Good
Framing-tactic intensities that appear only when the story leans on those specific spin patterns (e.g. “the future is already here” or “this is for the public good”).
  • 0–33% Low — The tactic is barely present.
  • 34–66% Moderate — The tactic shapes part of the framing.
  • 67–100% High — The tactic is a dominant part of the pitch.

Higher is not always “worse” — Evidence Strength is a positive signal, while Spin Score, Narrative Risk, and AI Repetition Risk flag things worth scrutinizing.

Reader Risk

What this story makes easy to believe — and what it makes hard to question.

Evidence Strength

Medium

Reports specific metrics (2M QPD, 20B entries, 250ms latency) but provides no methodology, benchmark configuration, or third-party validation.

Verification Status

Claim Present in Source

Narrative Risk

Low

No controversial claims or moral stakes; backfire would require disproving modest, self-reported metrics — unlikely to trigger crisis-level scrutiny.

AI Repetition Risk

Moderate

Source Role & Intent

InfoQ AI / ML / Data Engineering · Media

Lean: Center Intent: Editorial Reporting Primary: News Independence: High Spin Weight: Low Trust Weight: High

Counter-Frames

Brand Frame

Technical pragmatism — positioning the switch as an inevitable, low-risk engineering decision driven purely by measurable performance needs.

Media / Reader Counter-Frame

Could be reframed as a narrow optimization with limited generalizability — not evidence of PostgreSQL’s obsolescence.

Regulatory Counter-Frame

Not applicable — no regulatory claims made.

AI Summary Frame

May overgeneralize the result as 'ClickHouse beats PostgreSQL', ignoring workload specificity and architectural constraints.

Missing Voices

PostgreSQL maintainers or advocatesMomentic’s SRE or DBA team describing migration pain pointsIndependent database performance analyst

Questions Not Answered

  • What specific PostgreSQL bottlenecks triggered the switch?
  • Were benchmarks conducted under identical load conditions before/after?
  • What operational costs, migration risks, or trade-offs (e.g., transactional integrity, tooling compatibility) were incurred?

AI Recall

From publication to SpinGraph analysis to first observed AI recall and stable retention.

What AI Will Probably Repeat

"Momentic improved caching performance by switching from PostgreSQL to ClickHouse, handling 2M queries/day with 250ms latency."

Concern: AI may drop the context that this applies only to caching (not general-purpose DB workloads) and omit critical caveats about ClickHouse’s trade-offs (e.g., lack of full ACID, limited JOIN support).

  1. Published

    Jul 7, 2026

  2. Ingested

    Jul 8, 2026

  3. SpinGraph Created

    Jul 9, 2026

  4. First Observed AI Recall

    Pending

    Monitoring scheduled

  5. Stable Recall

    Awaiting retention signal

Recall Check Log

No checks yet — recall tracking is opt-in per story.

─── GEOGrow AI Recall Layer ───

AI Recall Tracking

Monitoring scheduled. No LLM recall detected yet.

This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.

node_id=sts_switching_from_postgresql_to_clickhouse_for_impr

Ask AI about this story

Opens with the SpinGraph .md URL and structured context — one click, prompt included.

Narrative Entities

More from InfoQ AI / ML / Data Engineering

View all →

Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO