# Dealing with failure

DevFeed: [Dealing with failure](<https://devfeed.tech/articles/dealing-with-failure-35764.md>)

Original publisher: [Read original article](<https://temporal.io/blog/dealing-with-failure>)

Author: Sergey Bykov

Published: 2021-01-21T04:00:00Z

Content type: opinion

Language: en

Sources: [Temporal Blog](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>), [retry](<https://devfeed.tech/topics/retry.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [client](<https://devfeed.tech/topics/client.md>), [servers](<https://devfeed.tech/topics/servers.md>), [systems](<https://devfeed.tech/topics/systems.md>)

Tags: [conference](<https://devfeed.tech/tags/conference.md>), [distributed-system](<https://devfeed.tech/tags/distributed-system.md>), [error](<https://devfeed.tech/tags/error.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [http](<https://devfeed.tech/tags/http.md>), [opinion](<https://devfeed.tech/tags/opinion.md>), [retry](<https://devfeed.tech/tags/retry.md>), [rpc](<https://devfeed.tech/tags/rpc.md>)

## AI overview

The article examines how to handle failures in cloud and distributed systems, focusing on request-reply or RPC, persistent queues, and workflows. It explains the simplicity and limitations of RPC, including timeouts, ambiguous outcomes, retries, unavailable systems, and partial failures.

## Source excerpt

I recently gave a talk at the CodeMesh conference, and I spent half of it reflecting on the seemingly boring topic of dealing with failures.