TechPrufer
Get started
Temporal
Temporal logoTemporal · Feature trail

ROI Analysis of Temporal Cloud Migration

3 posts · Apr 2024 – Dec 2024

What this trail covers

Temporal Cloud offers a compelling ROI for organizations migrating from self-hosted solutions or complex homegrown systems. This thread tracks the economic and strategic benefits, including cost savings, developer productivity gains, and faster time-to-market. It highlights how Temporal Cloud can replace legacy systems, improve reliability, and reduce infrastructure and staffing costs, making it a preferred choice for various industries. Recent updates focus on detailed cost attribution and migration tooling, with ZoomInfo reporting significant cost savings and operational efficiency gains by migrating from a self-hosted solution to Temporal Cloud for their dynamic audience management and AI-powered account summary features, handling hundreds of millions of operations monthly with reduced debugging and faster development cycles.

All Temporal trails
  1. How ZoomInfo Built a Scalable Cluster with Temporal CloudThis post details ZoomInfo's successful migration from a homegrown, challenging data processing system to Temporal Cloud for their dynamic audience management and AI-powered account summary features. It highlights the challenges of their previous system, including throughput limitations and debugging difficulties, and explains why Temporal's workflow-as-code approach and built-in observability were key decision factors. The post quantifies the benefits, noting a reduction in weekly debugging time from an entire day to near-zero maintenance mode, a two-week sprint for migrating four to five audience types, and a monthly cost saving of approximately $1000 by moving to Temporal Cloud from a self-hosted deployment. It also showcases the scalability of Temporal Cloud by handling 200 million actions per month for their new Copilot product with Account AI feature without requiring cluster adjustments, only rate limit adjustments. ZoomInfo's advice emphasizes trying Temporal for small projects and recognizing its versatility beyond traditional workflow systems, citing a sub-second response time for a workflow fetching and processing data from Bigtable.
  2. How to Migrate to Temporal Cloud from Self-HostedThis post outlines the technical steps and considerations for migrating from a self-hosted Temporal instance to Temporal Cloud. Key technical aspects include introducing a new Temporal Client that points to a different endpoint, securing the connection with API Keys and mTLS, implementing a Data Converter for data encryption, and strategizing the lifetime of existing Workflow Executions (either draining to completion or refactoring to pass state). It also mentions updating code that calls Workflows to route requests to the Temporal Cloud Namespace and the importance of a test and verification plan. The post clarifies that migrations are application-level, not database-level, and do not require migrating event histories.