This blog post is a public copy of our monthly newsletter. If you’d like to receive upcoming updates by email, you can subscribe to our newsletter here.
It’s been a packed year at Temporal. In this issue: a quick highlight reel of major product launches (including Nexus GA, new High Availability options, and more), a builder spotlight from Netflix on how they improved deployment reliability, and two fresh “How to Temporal” resources on AI fraud detection and end-to-end observability with OpenTelemetry. We’re also sharing a couple of great community Q&As on Activity idempotency.
For more information and other things we’ve been working on, just keep reading! And as always, we’d love to hear from you. Feel free to share feedback in our Community Slack.
Recently shipped#
2025 was a big year at Temporal, with tons of new and exciting features to play around with and make your applications even more resilient. Check out the highlight reel:
-
Temporal Nexus went GA this year, allowing users to connect Temporal applications across (and within) isolated Namespaces. Nexus provides all the benefits of Durable Execution across team and application boundaries with improved modularity, security, debugging, and fault isolation.
-
The OpenAI Agents SDK + Temporal Integration launched this summer. This means that AI agents you build with the OpenAI Agents SDK can stand up to the challenges of production, powered by Temporal’s Durable Execution.
-
A suite of High Availability features were released, including same-region replication, multi-region replication, and multi-cloud replication. When you enable High Availability features, Temporal deploys your primary and its replica in separate isolation domains, giving you control over the location of both. Fear no outages!
-
Worker Versioning entered Public Preview. This allows you to confidently deploy new changes to the Workflows running on your Workers without breaking them.
-
SCIM User Management went GA, allowing you to integrate your identity provider (IdP) with Temporal Cloud to automate user provisioning and access.
-
Temporal’s Ruby SDK went GA this fall, adding our seventh SDK for building applications on Temporal. Ooh, shiny!
-
Temporal Cloud’s OpenMetrics endpoint went Public Preview, providing operational metrics for your Temporal Cloud workloads and enabling comprehensive monitoring across Namespaces, Workflows, and Task Queues using your existing observability stack.
Builder spotlight#
Netflix has used Temporal since 2021, and they’ve expanded usage to multiple teams for many different use cases. Check out their recent blog post where they discuss the operational challenges they faced with Spinnaker that motivated their adoption of Temporal, and how Temporal helped Netflix reduce the number of transient deployment failures from 4% to 0.0001%.
How to Temporal#
- Learn how to build an AI-powered fraud detection application with Temporal and MongoDB. Move beyond static rules and manual processing with a context-aware system that detects sophisticated patterns in real time.
- See how to integrate Temporal with OpenTelemetry for production-ready observability, which enables you to trace requests across Workflow boundaries, monitor performance bottlenecks, and gain additional context to resolve issues faster.
Questions from the field#
- Justin Schulz posed a question about how to ensure consistency of an application database when an Activity responsible for updating it fails. Tihomir Surdilovic explained several edge cases that show why Temporal recommends idempotency for Activities, and also described a few potential workarounds that can help achieve the desired result even when an Activity is not idempotent.
- David Hernando asked about strategies for avoiding the payload size limit and Event History size limit when processing large datasets in Temporal Workflows. Tihomir Surdilovic shared key design considerations, while Raymond Ji described an approach using a loop with Activity Heartbeating. David also referenced a helpful example of batch processing.