ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
EF Core's EnableRetryOnFailure execution strategy retries a failed operation as a whole, including explicit transactions. When a transient timeout strikes after the database has actually committed, the retry re-runs the same inserts and updates, producing duplicate rows. The documented escape hatch is IExecutionStrategy.ExecuteInTransaction with a verifySucc
Ensure that side‑effects inside a Firebase Realtime Database transaction execute only once despite the SDK’s automatic retry mechanism. The SDK may invoke the transaction function up to 25 times when a conflict is detected, and it does not expose a retry count or provide built‑in deduplication, leaving developers to decide whether to make the function idempo
Goal Determine whether Jira Align’s bidirectional sync engine treats retry attempts after a transient failure as idempotent operations, so that a retry does not result in duplicate writes to either Jira Align or Jira Software. Constraints and uncertainty The sync runs every few minutes, uses a last‑write‑wins strategy based on detected timestamps, and provid
Goal The goal is to guarantee that a single user intent results in at most one write to the database, even when network instability triggers automatic retries of the same Action request. Current Constraints Remix’s Action functions are invoked via HTML Form submissions or the useSubmit hook, but the framework does not provide a built‑in idempotency key or re
Goal: Ensure that retrying a failed HTTP request does not result in duplicate writes to the backend. Constraints: Elm’s update function is pure, so emitting the same Msg repeatedly produces the same Cmd; the Http module provides no built‑in retry, backoff, or deduplication mechanisms, and the runtime does not track in‑flight requests. Uncertainty: The core d
The goal is to achieve exactly‑once write semantics when a Pulsar IO JDBC sink retries a message after a transient failure. Transactional producers bypass broker‑side deduplication, so relying on deduplicationEnabled=true does not prevent duplicate inserts on retry. The sink receives the same message again and, if the JDBC operation is a plain INSERT, each r
chat.postMessage Retries Without Duplicate Writes A background worker posts notifications to a Slack channel through the Web API and follows Slack's documented retry guidance: exponential backoff on 5xx and network timeouts, honoring Retry-After on 429 responses. The desired behavior is that a retry after an ambiguous failure — the request timed out but the
Goal Determine how to guarantee that a write operation performed inside a SurrealDB transaction is not duplicated when a retry is triggered by a transient failure. Constraints SurrealDB uses optimistic concurrency control; a retry requires re‑reading the state before re‑executing the write. Without an idempotency key, a retry can produce a duplicate‑key erro
Goal Determine how to guarantee that audit events forwarded from Teleport to an external sink are not duplicated when the Teleport backend retries delivery after a transient failure. Constraints & Uncertainty Teleport’s audit sink delivery is documented as at‑least‑once – retries are automatic but no exactly‑once guarantee is enforced. The platform emits
entityframeworkcore
firebase
jiraalign
remix
slack
surrealdb