Temporal
Read post

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

Unblocked, an AI context engine for software development, replaced a custom actor-model ingestion system with Temporal to handle continuous, durable ingestion across heterogeneous data sources. The team evaluated Prefect (ruled out for being Python-only), rolling their own (already doing that), and Temporal — which won on polyglot SDK support, native Durable Execution, and depth of capability. A thin Kotlin shim over Temporal's Java SDK collapsed pages of orchestration code to a few lines per workflow. Key gains include deployment-free long-running jobs, elimination of deploy-time DB spikes, unified cron and user-triggered flows, and built-in observability via the Temporal UI. Today Unblocked runs ~1 million Temporal Workflows per day with 3.6 million live workflows, self-hosted on Kubernetes with Aurora Serverless persistence and KEDA autoscaling.

    #kotlin#distributed-systems#workflow-orchestration
Yesterday•5m read time•From temporal.io
Post cover image
Table of contents
What Unblocked is, and why ingestion is hard #Before Temporal: The DIY actor model #The evaluation #The implementation #The payoff #Scale, and what’s next #
29 Impressions
Temporal's image
Temporal

Temporal's platform is a central hub for developers interested in distributed systems, workflow orch...

45 Followers

•

204 Upvotes

Would you recommend this post?

Copy link
WhatsApp
Facebook
X
New Squad
  • © 2026 Daily Dev Ltd.
  • Guidelines
  • Explore
  • Tags
  • Sources
  • Squads
  • Leaderboard