Home / Companies / PostHog / Blog / Post Details
Content Deep Dive

Why and how we moved exports to Temporal

Blog post from PostHog

Post Details
Company
Date Published
Author
Ian Vanagas
Word Count
1,674
Company Posts That Month
3
Language
-
Hacker News Points
-
Post removed?
No
Summary

PostHog has revamped its data export system to address scalability and reliability issues that plagued its previous export apps, which were unable to efficiently handle larger customer data flows. This new system, currently in public beta, leverages Temporal, a workflow engine that manages failure modes, retry logic, and timeouts, significantly enhancing the reliability, transparency, and cost-effectiveness of data exports. The previous export apps faced challenges like failure detection, data duplication, and high operational costs due to their reliance on an inefficient app service structure that was better suited for stateless apps. By adopting Temporal, PostHog has been able to implement retry and timeout logic, improve workflow visibility, and reduce the burden of manual interventions on its pipeline team. The new system includes a batch export abstraction layer that defines configurations for data exports and destinations, and it allows users to interact with their exports through a dedicated page where they can manage and monitor export activities. With this upgraded system, PostHog aims to enhance its customer data platform and warehouse functionality, while planning future improvements such as expanding destination support, enhancing performance, and adding features like roles-based access control and schema definition capabilities.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Real-time 1 2,396 582 180 -6%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.