Home/ Questions/Q 153289
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T09:46:30+00:00

I need to generate unique, incremental, numeric transaction id’s for each request I make

  • 0

I need to generate unique, incremental, numeric transaction id’s for each request I make to a certain XML RPC. These numbers only need to be unique across my domain, but will be generated on multiple machines.

I really don’t want to have to keep track of this number in a database and deal with row locking etc on every single transaction. I tried to hack this using a microsecond timestamp, but there were collisions with just a few threads – my application needs to support hundreds of threads.

Any ideas would be appreciated.

Edit: What if each transaction id just has to be larger than the previous request’s?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. If you’re going to be using this from hundreds of threads, working on multiple machines, and require an incremental ID, you’re going to need some centralized place to store and lock the last generated ID number. This doesn’t necessarily have to be in a database, but that would be the most common option. A central server that did nothing but serve IDs could provide the same functionality, but that probably defeats the purpose of distributing this.

    If they need to be incremental, any form of timestamp won’t be guaranteed unique.

    If you don’t need them to be incremental, a GUID would work. Potentially doing some type of merge of the timestamp + a hardware ID on each system could give unique identifiers, but the ID number portion would not necessarily be unique.

    Could you use a pair of Hardware IDs + incremental timestamps? This would make each specific machine’s IDs incremental, but not necessarily be unique across the entire domain.

    —- EDIT —–

    I don’t think using any form of timestamp is going to work for you, for 2 reasons.

    First, you’ll never be able to guarantee that 2 threads on different machines won’t try to schedule at exactly the same time, no matter what resolution of timer you use. At a high enough resolution, it would be unlikely, but not guaranteed.

    Second, to make this work, even if you could resolve the collision issue above, you’d have to get every system to have exactly the same clock with microsecond accuracy, which isn’t really practical.

    • 0