Preventing duplicate writes during Ballerina client retries
Handling Idempotency in Network Retries Ballerina provides built-in retry mechanisms for service clients to manage transient failures. However, when performing non-idempotent operations—such as POST requests to a database or external API—automatic retries can lead to duplicate resource creation if the initial request was processed but the response was lost.