Blog post to introduce the Temporal Swift SDK #1221
+63
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FranzBusch
requested review from
a team,
davelester,
shahmishal,
timsneath and
tkremenek
as code owners
Member
|
Youtube link is up if you want to link to it |
davelester
requested changes
Nov 7, 2025
Co-authored-by: Dave Lester <[email protected]>
Co-authored-by: Dave Lester <[email protected]>
davelester
requested changes
Nov 7, 2025
davelester
requested changes
Nov 7, 2025
|
|
||
| Building reliable distributed systems requires handling failures gracefully, coordinating complex workflows across multiple services, and ensuring long-running processes complete successfully. Rather than develop these resiliency features into every application or service you develop, Temporal offers the pattern of a __workflow__. Workflows encapsulate your code so it runs durably and handles many common failure scenarios. | ||
|
|
||
| With the Temporal Swift SDK, you can build resilient workflows that survive infrastructure failures. The SDK brings another essential tool for developers that build highly reliable and scalable production cloud services. |
Contributor
There was a problem hiding this comment.
Suggested change
| With the Temporal Swift SDK, you can build resilient workflows that survive infrastructure failures. The SDK brings another essential tool for developers that build highly reliable and scalable production cloud services. | |
| The SDK brings an essential tool for Swift developers building highly reliable and scalable production cloud services. |
davelester
requested changes
Nov 10, 2025
|
|
||
| ## Writing durable workflows in Swift | ||
|
|
||
| The Temporal Swift SDK enables developers to write reliable and durable workflows. Previously, Swift developers had to resort to more traditional approaches for building fault-tolerant workflows, such as implementing custom state machines on top of database systems or message queuing services, solutions that often required significant boilerplate code and careful handling of edge cases that Temporal manages automatically. |
Contributor
There was a problem hiding this comment.
Suggested change
| The Temporal Swift SDK enables developers to write reliable and durable workflows. Previously, Swift developers had to resort to more traditional approaches for building fault-tolerant workflows, such as implementing custom state machines on top of database systems or message queuing services, solutions that often required significant boilerplate code and careful handling of edge cases that Temporal manages automatically. | |
| Durable workflows run to completion even when infrastructure fails. If your server crashes mid-execution, Temporal automatically resumes the workflow from where it left off with no lost state or manual intervention required. By bringing this capability to the Swift ecosystem, developers can focus on application logic while Temporal handles state management, retries, and recovery. |
| - Leveraging Swift's strong type system to catch errors at build time rather than runtime. | ||
| - Providing macros to reduce boilerplate when authoring workflows. | ||
|
|
||
| The design and implementation of the Temporal Swift SDK has been informed and validated by multiple production use-cases, ensuring that the SDK meets real-world requirements for performance, reliability, and developer experience. |
Contributor
There was a problem hiding this comment.
Suggested change
| The design and implementation of the Temporal Swift SDK has been informed and validated by multiple production use-cases, ensuring that the SDK meets real-world requirements for performance, reliability, and developer experience. |
Contributor
There was a problem hiding this comment.
It may be worth removing this paragraph.
| - Providing macros to reduce boilerplate when authoring workflows. | ||
|
|
||
| The design and implementation of the Temporal Swift SDK has been informed and validated by multiple production use-cases, ensuring that the SDK meets real-world requirements for performance, reliability, and developer experience. | ||
|
|
Contributor
There was a problem hiding this comment.
Delete newline if the paragraph above is also delete.
|
|
||
| The design and implementation of the Temporal Swift SDK has been informed and validated by multiple production use-cases, ensuring that the SDK meets real-world requirements for performance, reliability, and developer experience. | ||
|
|
||
| The Temporal Swift SDK can be used across a wide range of real-world scenarios where reliability and coordination are paramount, including: |
Contributor
There was a problem hiding this comment.
Suggested change
| The Temporal Swift SDK can be used across a wide range of real-world scenarios where reliability and coordination are paramount, including: | |
| Temporal workflows are particularly valuable for handling multi-step coordination in applications that must survive failures, such as data pipelines, business automation, payment processing, and operational tasks. |
| The design and implementation of the Temporal Swift SDK has been informed and validated by multiple production use-cases, ensuring that the SDK meets real-world requirements for performance, reliability, and developer experience. | ||
|
|
||
| The Temporal Swift SDK can be used across a wide range of real-world scenarios where reliability and coordination are paramount, including: | ||
|
|
|
|
||
| The Temporal Swift SDK can be used across a wide range of real-world scenarios where reliability and coordination are paramount, including: | ||
|
|
||
| - E-commerce and payment processing where multi-step payment processing requires automatic retry and rollback capabilities. |
Contributor
There was a problem hiding this comment.
Suggested change
| - E-commerce and payment processing where multi-step payment processing requires automatic retry and rollback capabilities. |
| The Temporal Swift SDK can be used across a wide range of real-world scenarios where reliability and coordination are paramount, including: | ||
|
|
||
| - E-commerce and payment processing where multi-step payment processing requires automatic retry and rollback capabilities. | ||
| - Data processing & ETL where you may be performing large-scale data transformation pipelines. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Data processing & ETL where you may be performing large-scale data transformation pipelines. |
|
|
||
| - E-commerce and payment processing where multi-step payment processing requires automatic retry and rollback capabilities. | ||
| - Data processing & ETL where you may be performing large-scale data transformation pipelines. | ||
| - Business process automation with approval workflows and human-in-the-loop interactions. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Business process automation with approval workflows and human-in-the-loop interactions. |
| - E-commerce and payment processing where multi-step payment processing requires automatic retry and rollback capabilities. | ||
| - Data processing & ETL where you may be performing large-scale data transformation pipelines. | ||
| - Business process automation with approval workflows and human-in-the-loop interactions. | ||
| - Monitoring and operations with scheduled maintenance and cleanup tasks. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Monitoring and operations with scheduled maintenance and cleanup tasks. |
davelester
requested changes
Nov 10, 2025
|
|
||
| [Temporal](https://temporal.io) is an open source platform for building reliable distributed applications. At its core is the concept of durable execution, your code runs to completion even in the face of infrastructure failures. When a worker crashes or restarts, Temporal automatically resumes your workflow from where it left off, without requiring you to write complex retry logic or state management code. This is achieved through Temporal's architecture, which separates workflow orchestration from actual work execution: | ||
|
|
||
| - **Workflows** define the overall business logic and coordination. They describe the sequence of steps, decision points, and error handling for a process. Workflows must be deterministic given the same inputs and history, they must always make the same decisions. |
Contributor
There was a problem hiding this comment.
Suggested change
| - **Workflows** define the overall business logic and coordination. They describe the sequence of steps, decision points, and error handling for a process. Workflows must be deterministic given the same inputs and history, they must always make the same decisions. | |
| - **Workflows** define the overall business logic and coordination. They describe the sequence of steps, decision points, and error handling for a process. Workflows must be deterministic. Given the same inputs and history, they must always make the same decisions. |
|
|
||
| Modern distributed systems face common challenges: coordinating multiple services, handling partial failures, ensuring consistency across operations, and managing long-running processes. Traditional approaches require building custom retry logic, state machines, and coordination mechanisms. Temporal provides a platform that handles these concerns, allowing you to focus on your business logic. | ||
|
|
||
| Temporal has also published a [blog post](https://temporal.io/blog/announcing-the-swift-temporal-sdk) detailing the introduction of the Temporal Swift SDK highlighting the unique advantages this brings to Swift developers building distributed systems. |
Contributor
There was a problem hiding this comment.
Suggested change
| Temporal has also published a [blog post](https://temporal.io/blog/announcing-the-swift-temporal-sdk) detailing the introduction of the Temporal Swift SDK highlighting the unique advantages this brings to Swift developers building distributed systems. |
Contributor
There was a problem hiding this comment.
Moving to Getting Started section
| Modern distributed systems face common challenges: coordinating multiple services, handling partial failures, ensuring consistency across operations, and managing long-running processes. Traditional approaches require building custom retry logic, state machines, and coordination mechanisms. Temporal provides a platform that handles these concerns, allowing you to focus on your business logic. | ||
|
|
||
| Temporal has also published a [blog post](https://temporal.io/blog/announcing-the-swift-temporal-sdk) detailing the introduction of the Temporal Swift SDK highlighting the unique advantages this brings to Swift developers building distributed systems. | ||
|
|
|
|
||
| ## Getting started | ||
|
|
||
| To get started with the Temporal Swift SDK, explore its [documentation](https://swiftpackageindex.com/apple/swift-temporal-sdk/main/documentation/temporal) which provides detailed guides for implementing workflows and activities. The repository also includes a rich collection of [example projects](https://github.com/apple/swift-temporal-sdk/tree/main/Examples), demonstrating the SDK's capabilities across different use cases from simple task orchestration to complex multi-step business processes. For a deeper understanding of Temporal's core concepts and architectural patterns, be sure to check out the [general Temporal documentation](https://docs.temporal.io/), which provides valuable context for building robust distributed systems. |
Contributor
There was a problem hiding this comment.
Suggested change
| To get started with the Temporal Swift SDK, explore its [documentation](https://swiftpackageindex.com/apple/swift-temporal-sdk/main/documentation/temporal) which provides detailed guides for implementing workflows and activities. The repository also includes a rich collection of [example projects](https://github.com/apple/swift-temporal-sdk/tree/main/Examples), demonstrating the SDK's capabilities across different use cases from simple task orchestration to complex multi-step business processes. For a deeper understanding of Temporal's core concepts and architectural patterns, be sure to check out the [general Temporal documentation](https://docs.temporal.io/), which provides valuable context for building robust distributed systems. | |
| To get started with the Temporal Swift SDK, explore its [documentation](https://swiftpackageindex.com/apple/swift-temporal-sdk/main/documentation/temporal) which provides detailed guides for implementing workflows and activities. The repository also includes a rich collection of [example projects](https://github.com/apple/swift-temporal-sdk/tree/main/Examples), demonstrating the SDK's capabilities across different use cases from simple task orchestration to complex multi-step business processes. | |
| For a deeper understanding of Temporal's core concepts and architectural patterns, check out the [general Temporal documentation](https://docs.temporal.io/), which provides valuable context for building robust distributed systems. Temporal published a [blog post](https://temporal.io/blog/announcing-the-swift-temporal-sdk) highlighting the advantages the SDK brings to Swift developers building distributed systems. |
|
|
||
| ## Community and feedback | ||
|
|
||
| Temporal Swift SDK is an open source project and we're eager to hear from the Swift community. Whether you're building microservices, coordinating long-running processes, or simply curious about durable execution, we'd love to know how the Temporal Swift SDK works for you. The SDK provides a powerful foundation for building reliable distributed systems in Swift. |
Contributor
There was a problem hiding this comment.
Suggested change
| Temporal Swift SDK is an open source project and we're eager to hear from the Swift community. Whether you're building microservices, coordinating long-running processes, or simply curious about durable execution, we'd love to know how the Temporal Swift SDK works for you. The SDK provides a powerful foundation for building reliable distributed systems in Swift. | |
| Temporal Swift SDK is an open source project and we're eager to hear from the Swift community. Whether you're building microservices, coordinating long-running processes, or simply curious about durable execution, we'd love to know how the Temporal Swift SDK works for you. |
|
|
||
| The project is actively developed and we welcome contributions, bug reports, and feature requests. As with any distributed systems tool, different applications and environments present unique challenges, and community feedback is essential for improving the SDK's effectiveness across diverse Swift codebases. | ||
|
|
||
| Ready to start building reliable distributed systems? Visit the [Temporal Swift SDK repository](https://github.com/apple/swift-temporal-sdk) to get started. No newline at end of file |
Contributor
There was a problem hiding this comment.
Suggested change
| Ready to start building reliable distributed systems? Visit the [Temporal Swift SDK repository](https://github.com/apple/swift-temporal-sdk) to get started. |
| Temporal Swift SDK is an open source project and we're eager to hear from the Swift community. Whether you're building microservices, coordinating long-running processes, or simply curious about durable execution, we'd love to know how the Temporal Swift SDK works for you. The SDK provides a powerful foundation for building reliable distributed systems in Swift. | ||
|
|
||
| The project is actively developed and we welcome contributions, bug reports, and feature requests. As with any distributed systems tool, different applications and environments present unique challenges, and community feedback is essential for improving the SDK's effectiveness across diverse Swift codebases. | ||
|
|
|
|
||
| Temporal Swift SDK is an open source project and we're eager to hear from the Swift community. Whether you're building microservices, coordinating long-running processes, or simply curious about durable execution, we'd love to know how the Temporal Swift SDK works for you. The SDK provides a powerful foundation for building reliable distributed systems in Swift. | ||
|
|
||
| The project is actively developed and we welcome contributions, bug reports, and feature requests. As with any distributed systems tool, different applications and environments present unique challenges, and community feedback is essential for improving the SDK's effectiveness across diverse Swift codebases. |
Contributor
There was a problem hiding this comment.
Suggested change
| The project is actively developed and we welcome contributions, bug reports, and feature requests. As with any distributed systems tool, different applications and environments present unique challenges, and community feedback is essential for improving the SDK's effectiveness across diverse Swift codebases. | |
| The project is actively developed and we welcome contributions, bug reports, and feature requests. Ready to start building reliable distributed systems? Visit the [Temporal Swift SDK repository](https://github.com/apple/swift-temporal-sdk) to get started. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.