Home/ Questions/Q 3237032
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T17:41:26+00:00

I have a design pattern I have been struggling with on how best to

  • 0

I have a design pattern I have been struggling with on how best to prevent duplicate posting of data.

Here are the steps:

  1. Client submits data with a unique guid (client generated guid – guaranteed unique)
  2. Server side software makes sure client guid doesn’t exist yet in the DB
  3. begins transaction
  4. process data (can take between 1-20 seconds depending upon payload)
  5. commits transaction

Here are the scenarios:
Client submits data with guid “1”, and then resubmits data with guid “1” before step (5) is hit for the original data submission, then the transaction is processed twice.

What is the best design pattern to prevent this without using semaphores or blocking? The user should be able to resubmit, in case the first submission fails for some reason (hardware issue on the server side, etc.).

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Store the GUID in a column with an SQL UNIQUE constraint.

    When you attempt (within the transaction) to insert a second duplicate GUID, the operation will fail, at which point you roll back the entire transaction.

    • 0