Skip to main content
MongoDBCustomer loss

Why we moved our analytics engine from MongoDB to ClickHouse.

What happened

MongoDB lost client VIEW26 GmbH on Jun 18th '26.

Source

Article excerpt

Highlighted: the sentence this signal was extracted from

Why VIEW26 GmbH moved its analytics engine from MongoDB to ClickHouse. Why did VIEW26 move from MongoDB to ClickHouse? As Jira Service Management datasets grew, Charts & Reports for JSM needed faster analytics at scale. ClickHouse now powers stronger dashboards, KPIs, filters, and reports for its Atlassian enterprises users As a reporting platform built for Jira Service Management,View26 Charts and Reports helps teams turn their project data into actionable insights through charts, KPIs, dashboards, and detailed tabular reports. As its customers' datasets grew into the millions of rows, VIEW26 GmbH knew it was time to rethink the foundation powering it all. This is the story of why VIEW26 GmbH migrated from MongoDB to ClickHouse, what VIEW26 GmbH learned along the way, and where VIEW26 GmbH is headed next. The challenge: when your database wasn't built for analytics. MongoDB served VIEW26 GmbH well in its early days. Its flexible document model made it easy to iterate quickly and ship features fast. But as its platform matured and its customers started tracking increasingly complex Jira workflows, VIEW26 GmbH began running into a fundamental limitation: MongoDB is a general-purpose database, not an analytical one. Its customers rely on VIEW26 GmbH to aggregate, slice, and visualize their Jira data in real time. They build KPI dashboards that compute metrics across...

Keep reading with a free account

The rest of this article, and every signal for MongoDB, is in your free account.

Extracted by Autobound

From the Signal API record
Event
Customer loss

What this signalsA lost customer often leads to a review of how the company sells and serves.

Takes effect
Jun 18, 2026

Companies

  • VIEW26 GmbHClientview26.com

More customer loss signals at other companies

The full record

From the Signal API record

Details

Ticker
NASDAQ:MDB

Extraction

Confidence
60%
Detected
Jun 18, 2026
signal_type
news
signal_subtype
loses_client

Use this data

Get every customer loss signal for MongoDB and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at MongoDB this week?”

  2. Send it to your own tools

    The Signal API returns customer loss signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full news record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/d8794a77-14b9-4258-8647-83194716935a returns this record as JSON. POST /v1/companies/enrich returns every signal for mongodb.com.

{
  "signal_id": "d8794a77-14b9-4258-8647-83194716935a",
  "signal_type": "news",
  "signal_subtype": "loses_client",
  "detected_at": "2026-06-18T03:30:00+00:00",
  "company": {
    "name": "MongoDB",
    "domain": "mongodb.com"
  },
  "data": {
    "url": "https://www.view26.com/blog/why-we-moved-our-analytics-engine-from-mongodb-to-clickhouse",
    "title": "Why we moved our analytics engine from MongoDB to ClickHouse.",
    "ticker": "NASDAQ:MDB",
    "excerpt": "Why VIEW26 GmbH moved its analytics engine from MongoDB to ClickHouse.\n\nWhy did VIEW26 move from MongoDB to ClickHouse? As Jira Service Management datasets grew, Charts & Reports for JSM needed faster analytics at scale. ClickHouse now powers stronger dashboards, KPIs, filters, and reports for its Atlassian enterprises users\n\nAs a reporting platform built for Jira Service Management ,View26 Charts and Reports helps teams turn their project data into actionable insights through charts, KPIs, dashboards, and detailed tabular reports. As its customers' datasets grew into the millions of rows, VIEW26 GmbH knew it was time to rethink the foundation powering it all.\n\nThis is the story of why VIEW26 GmbH migrated from MongoDB to ClickHouse, what VIEW26 GmbH learned along the way, and where VIEW26 GmbH is headed next.\n\nThe challenge: when your database wasn't built for analytics.\n\nMongoDB served VIEW26 GmbH well in its early days. Its flexible document model made it easy to iterate quickly and ship features fast. But as its platform matured and its customers started tracking increasingly complex Jira workflows, VIEW26 GmbH began running into a fundamental limitation: MongoDB is a general-purpose database, not an analytical one.\n\nIts customers rely on VIEW26 GmbH to aggregate, slice, and visualize their Jira data in real time. They build KPI dashboards that compute metrics across...",
    "summary": "MongoDB lost client VIEW26 GmbH on Jun 18th '26.",
    "planning": false,
    "image_url": "https://cms.view26.com/api/media/file/compare-clickhouse.png",
    "confidence": 0.5995,
    "published_at": "2026-06-18T03:30:00Z",
    "effective_date": "2026-06-18",
    "article_sentence": "Why VIEW26 GmbH moved its analytics engine from MongoDB to ClickHouse.",
    "related_company_name": "VIEW26 GmbH",
    "related_company_domain": "view26.com"
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.