Hi Yegor, thanks for your suggestions.
But I yet cannot understand how to cope with transactions in the
scenario you have described.
Let's say that I have the following (usual) example:
public class User {
Long userID; //it is the PK of the object
ArrayListContact contacts;
...
}
public
I had to strongly synchronize my app using Java options (locka,
synchrnized objects, and so on...).
I have to warn you that all this synchronization will be in vain once
your application grows beyond 1 JVM. Java keyword synchronized is
only effective within a single instance of JVM. That is not
Thank you Didier,
I had to strongly synchronize my app using Java options (locka,
synchrnized objects, and so on...).
I think it is quite unbelievable that a huge giant like BigTable is so
weak in concurrency issues...
Perhaps my approach is geared from my experience in relational DBs,
but I'm
Hi,
I guess that you should read the Background parag of
http://code.google.com/appengine/articles/scaling/contention.html to
see what's happening to your app and then find out a way to
rearchitect it in order to avoid touching same data at same time from
different transactions
Don't have enough
