<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Failure-Handling on Brian Faust</title><link>https://vacua.dev/tags/failure-handling/</link><description>Recent content in Failure-Handling on Brian Faust</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://vacua.dev/tags/failure-handling/rss.xml" rel="self" type="application/rss+xml"/><item><title>A Third-Party API Is an Unreliable Collaborator</title><link>https://vacua.dev/thoughts/a-third-party-api-is-an-unreliable-collaborator/</link><pubDate>Thu, 01 Feb 2018 00:00:00 +0000</pubDate><guid>https://vacua.dev/thoughts/a-third-party-api-is-an-unreliable-collaborator/</guid><description>&lt;p&gt;A scheduled import begins by listing remote orders. The list request returns a
502 HTML page, so there are no trustworthy item identifiers to process.&lt;/p&gt;
&lt;p&gt;On another run the list succeeds. One order then returns a 504 while its
details are being loaded. The remaining orders are still independent and can
continue.&lt;/p&gt;
&lt;p&gt;These failures share a provider, but not a recovery boundary. Treating both as
“the API is down” either discards useful work or pretends to know more than the
response established.&lt;/p&gt;</description></item></channel></rss>