|
|
|
|
|
|
by CodesInChaos
1797 days ago
|
|
|
Timestamps have monotonicity issues as well: 1. If you create it in the application, clocks need to be synced well enough between all application servers. If you create it in the database, this shouldn't be an issue. 2. The transaction completes some time after the the timestamp was created, and that time can vary between concurrent transactions. This is a fundamental problem. The MAX + 1 approach should guarantee strict monotonicity, but might lead to scalability issues for highly contented counters. |
|
|