Reliable API Publishing: Handle Unknown Outcomes Before Retrying
When a publishing request times out, the most dangerous assumption is that nothing happened. The remote server may have created the article and lost the response on the way back. Repeating the request can then produce a second public article. A content publishing service should model this uncertainty explicitly. This article describes a practical design for publishing through a third-party API.…
We haven't written up this one. Dev.to has the full story — the link below goes straight to it.