I have to come up with a “event dupe check” system that handles race conditions
where two requests come in at the same time. Obviously this can be solved with
lightweight transactions (if not exists), however I am concerned that there may
be costs/issues hidden to me for doing significant
On Wed, Aug 13, 2014 at 9:16 AM, Wayne Schroeder
wschroe...@pinsightmedia.com wrote:
Are there hidden costs to LWT (paxos) that are not represented in the
total time and number of operations? For example, are there some
under-the-hood locks that could cause contention issues when processing
Well… I didn’t expect them to be free :)
Knowing the price would help weigh the consequences of using them though. I
just don’t want to implement a check/write/double check solution if it ends up
being actually more expensive in total operations and time than simply using
LWT. Any thoughts
On Wed, Aug 13, 2014 at 12:28 PM, Wayne Schroeder
wschroe...@pinsightmedia.com wrote:
Knowing the price would help weigh the consequences of using them
though. I just don’t want to implement a check/write/double check solution
if it ends up being actually more expensive in total operations
