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

Why a context engine needs Durable Execution: How Unblocked rebuilt its ingestion backbone on Temporal

Blog post from Temporal

Post Details
Company
Date Published
Author
Martin Scotta
Word Count
853
Company Posts That Month
14
Language
English
Hacker News Points
-
Post removed?
No
Summary

Unblocked, a context engine for AI-driven software development, transitioned its architecture to Temporal to address challenges in continuously computing against the current state of various data sources, such as code, PRs, and Slack conversations, without relying on cached answers. Originally utilizing a DIY actor model with custom queues and retries, Unblocked found this approach resource-intensive and opted for Temporal due to its polyglot SDK support, durable execution primitives, and robust capabilities. By integrating Temporal, Unblocked improved system reliability and efficiency, enabling deployment-free workflows and eliminating complex orchestration code. This shift allowed the engineering team to focus more on product development rather than infrastructure, significantly enhancing the overall value of the platform. With Temporal, Unblocked now efficiently runs about 1 million workflows daily, with plans to further streamline its code ingestion and expand Temporal's adoption across all engineering processes.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
AI Agents 1 6,829 1,441 261 +10%
Kubernetes 1 2,771 402 114 +33%
MCP 1 10,922 895 210 +41%
Observability 1 4,170 814 198 -2%
Serverless 1 775 251 99 -24%
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.