In the past, I've devoted a ton of time and code to making distributed
transactions (kind of) work. I eventually saw the error of my ways.
This paper is a good place to start:
http://www-db.cs.wisc.edu/cidr/cidr2007/papers/cidr07p15.pdf
atomly
On Fri, May 13, 2016 at 1:17 PM, Roland Kuhn <
that somewhere (hazelcast, memcached, redis, etc). If an item is already
marked as processed in this iteration, move on.
atomly
On Tue, May 10, 2016 at 3:41 PM, kraythe <kray...@gmail.com> wrote:
> Ok, I am sorry, I can't be precise. NDAs and so on. Let me try to bullet
> point it.
>
)
forMax(timeout)
}
:: atomly ::
[ ato...@atomly.com : www.atomly.com : http://blog.atomly.com/ ...
[ atomiq records : new york city : +1.347.692.8661 ...
[ e-mail atomly-news-subscr...@atomly.com for atomly info and updates ...
On Tue, Sep 30, 2014 at 1:20 PM, bearrito j.barrett.straus
for you and there is no problem with writing your code that way
from an Akka best practices viewpoint, so you might as well continue with
it.
:: atomly ::
[ ato...@atomly.com : www.atomly.com : http://blog.atomly.com/ ...
[ atomiq records : new york city : +1.347.692.8661 ...
[ e-mail atomly-news
, so that all keys for any given user would be
grouped on a server and would be able to be loaded with one multi-get,
cutting down our latency in a very high load environment-- and it is not
that difficult. If you have any questions, I may be able to help...
:: atomly ::
[ ato...@atomly.com
