infrastructure-api-race-condition-creating-a-score-and-deleting-it-within-20-seconds-00dd33c1

THEN Implement idempotency or ensure that the delete operation waits for the creation to be fully committed. Consider using a distributed lock or transactional approach to avoid race conditions between POST and DELETE on the same resource.

// Conceptual example: ensure create is committed before delete
postScore(scoreId);
await waitForCommit(scoreId); // e.g., wait for eventual consistency
deleteScore(scoreId);