Hi Jeff,
thanks for the feedback.
From previous discussions here, HRD eventuality is usually seconds,
sometimes minutes, and in catastrophic scenarios could be hours.
That's interesting. So there is no guarantee for a maximum delay of the
eventually consistency.
I understand you right, that in
On Tue, Oct 25, 2011 at 2:52 AM, Mos mosa...@googlemail.com wrote:
That's interesting. So there is no guarantee for a maximum delay of the
eventually consistency.
I understand you right, that in practice it could take hours for a new blog
post to show up in a query?
Here's the thread:
Thanks for the feedback.
Regarding eventually consistency one advice of this talk was:
Accept it.
I think for many use-cases in typical web-application this is ok.
For showing a use his own post immediately, you can remember the key of the
entity and add it manually to the query-list (if not yet
I used to advise people to use shared entity groups as little as possible.
That was on M/S. I have found that the HRD changes everything, and now I
use hierarchical entity groups quite a lot.
From previous discussions here, HRD eventuality is usually seconds,
sometimes minutes, and in
+1 to your approach :)
In Siena, I introduced the so-called aggregation which is entity group in
a more generic way.
It gives a very interesting way to design your models and fits lots of
situations!
Pascal
On Mon, Oct 24, 2011 at 9:39 PM, Jeff Schnitzer j...@infohazard.org wrote:
I used to
If you design it right you can benefit from strong consistency in the
situations you need it while still not hitting the 1 write/sec/group
cap, see the Google IO talk about it (in particular the user centric
design):
http://www.youtube.com/watch?v=xO015C3R6dw
And the slides of the talk:
