Why we moved our analytics engine from MongoDB to ClickHouse.

{
  "signal_id": "301e6a30-9974-4359-ae61-d96b1a14e1a5",
  "signal_type": "news",
  "signal_subtype": "signs_new_client",
  "detected_at": "2026-06-18T03:30:00+00:00",
  "company": {
    "name": "ClickHouse",
    "domain": "clickhouse.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.",
    "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": "ClickHouse signed new client VIEW26 GmbH on Jun 18th '26.",
    "planning": false,
    "image_url": "https://cms.view26.com/api/media/file/compare-clickhouse.png",
    "confidence": 0.6579,
    "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"
  }
}

curl https://signals.autobound.ai/v1/signals/301e6a30-9974-4359-ae61-d96b1a14e1a5 \
  -H "X-API-KEY: $AUTOBOUND_API_KEY"

curl -X POST https://signals.autobound.ai/v1/companies/enrich \
  -H "X-API-KEY: $AUTOBOUND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"clickhouse.com","limit":20}'