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

Benchmarking Latency: Temporal Cloud vs. Self-Hosted Temporal

Blog post from Temporal

Post Details
Company
Date Published
Author
Rob Holland and Meagan Speare
Word Count
1,388
Company Posts That Month
5
Language
English
Hacker News Points
-
Post removed?
No
Summary

Developers often worry that using Temporal will increase latency in their applications. However, Temporal provides various features and design patterns to help meet the latency requirements of most apps. The minimum latency depends on network latency between Workers and the Temporal Service, as well as how well the service is tuned. Contrary to popular belief, end-to-end application latency is significantly lower when using Temporal Cloud compared to self-hosted Temporal due to its custom persistence layer and other architectural advancements. Benchmarking results show that Temporal Cloud offers lower latency across various metrics, making it a better choice for internet scale and low latency workloads.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Kubernetes 1 1,327 144 77 -36%
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.