best practices

18 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Optimization priority for cost reduction

Optimization priority should be: 1) Actions optimization (usually provides the largest cost reduction opportunity), 2) Active Storage optimization (relevant for long-running Workflows or large payloads), 3) Retained Storage optimization (relevant for high volume combined with long retention periods).

Temporal Cloud consumption-based pricing components

Temporal Cloud uses consumption-based pricing with two primary cost components: Actions and Storage.

Over-optimization at expense of observability anti-pattern

Aggressively optimizing costs without maintaining sufficient visibility for debugging and operational needs compromises the ability to diagnose issues. Balance cost reduction with observability requirements. Merging Activities reduces Actions but loses per-step visibility and independent retry control. Removing Heartbeats saves Actions but prevents Worker failure detection and progress tracking.

High Actions costs generally indicate workflow patterns

High Actions costs generally indicate: many Activities per Workflow, frequent Signals, Queries, or Updates, long-running Activities with Heartbeats, high Activity retry rates, or extensive Query usage.

High Storage costs generally indicate workflow patterns

High Storage costs generally indicate: large payloads in Workflow inputs, outputs, or Activity results, long retention periods with high Workflow volume, long-running Workflows without Continue-As-New, or Workflows accumulating large Event Histories.

Active Storage vs Retained Storage pricing

Active Storage applies to open Workflows and their Event Histories and is significantly more expensive than Retained Storage. Retained Storage applies to closed Workflow History during the retention period.

Default Namespace retention period and configuration

The default Namespace retention is 30 days and is configurable between 1 and 90 days. Shorter retention reduces costs but limits historical analysis. Audit investigation patterns before shortening retention and ensure compliance requirements are met.

Workflow export for compliance

Temporal Cloud supports exporting Event Histories to external storage for compliance while maintaining shorter retention periods. Workflow export costs one Action per export.

Actions represent majority of costs for most workloads

For most workloads, Actions represent the majority of total costs, with storage typically accounting for 10% or less of a monthly bill.

Establish baseline metrics before optimizing

Establish baseline metrics before optimizing and validate impact after implementation. Specifically measure: Actions consumption (per Workflow, per day/month, by Namespace), Storage consumption (Active and Retained), monthly costs (total, per Namespace, per Workflow Type), and observability metrics (time to debug, incident detection).

Optimization validation approach

Optimization validation should follow: 1) Test in non-production to validate functional correctness before production deployment, 2) Monitor comprehensively using the Usage dashboard in the Cloud UI to track the impact on Actions and Storage after optimizations are made, 3) Progressive rollout to a small percentage, validate, then expand using Worker Versioning for rolling out changes to Workflows, 4) Continuous review to re-evaluate optimization effectiveness quarterly as system evolves.

Cost optimization success criteria

Optimization success criteria include: Cost reduced without increasing mean time to repair (MTTR), Workflow success rates maintained or improved, and reduced observability does not increase mean time to detect (MTTD) incidents.

Build Workflows following best practices first, then optimize

Build Workflows following best practices first, then optimize based on observed costs. Premature optimization can compromise observability and create operational challenges.

Best practices documentation overview for Temporal Cloud

Comprehensive best practices guides exist for Temporal Cloud covering namespace management, security, operational excellence, and development standards. These guides provide validated, opinionated frameworks to help teams establish robust Temporal standards and ensure workflow orchestration implementations are maintainable, scalable, and aligned with platform best practices.

Best practices guide sections available

The best practices documentation includes guides for: Managing a Namespace (configuring, managing, and optimizing Temporal Namespaces), Managing Temporal Cloud Access Control (access control and user management guidelines), Security Controls for Temporal Cloud (comprehensive security practices), Worker Deployment and Performance (deploying and optimizing Workers for performance and reliability), Cost Optimization (optimizing costs while maintaining Workflow reliability and observability), Pre-Production Testing (failure injection, load testing, and operational validation), and Knowledge Hub (building internal Temporal knowledge bases for developer onboarding and consistent standards).

Target audience for Temporal best practices documentation

The best practices documentation is intended for developers responsible for building a Temporal Cloud practice within their organization, anyone building tutorials, courses, onboarding paths, or documentation, and partners or vendors creating Temporal-related learning materials.

Problems addressed by Temporal best practices standards

Without clearly defined Temporal standards, organizations often struggle with inconsistent Workflow implementations, fragmented best practices, and misaligned development approaches. Established standards help ensure maintainability, scalability, and alignment with platform best practices.

.NET workflow parameters best practice

Temporal workflows may have any number of custom parameters. However, it is strongly recommended to use objects as parameters so that individual fields may be altered without breaking the signature of the workflow.

Give your agent this brain