Thank you Ryan the post provided exactly what I needed to hear about
Datastore api behaviour. I will be tuned in for your Google I-O
presentation.
In some respects I am relieved to read that an App is usually only
served from one location because if not I would have remained puzzled
as to how
On Wed, Apr 22, 2009 at 1:49 PM, javaDinosaur jonathan...@hotmail.co.ukwrote:
Thank you Ryan the post provided exactly what I needed to hear about
Datastore api behaviour. I will be tuned in for your Google I-O
presentation.
In some respects I am relieved to read that an App is usually only
On Apr 22, 2:49 am, javaDinosaur jonathan...@hotmail.co.uk wrote:
Last year I noticed that GAE hosted my trial App within 30ms of my UK
location i.e. somewhere in Europe. Such automatic hosting geo affinity
is highly impressive but what if an App's admin is UK based but the
you might be
One aspect that neither Ryan nor anybody else in this thread touched
upon is the entity hierarchy relationship. I understand that
transactions that involve multiple records are only honored among
entities that have the same GAE ancestry. This along with hints in the
documentation and
On Apr 22, 10:38 am, Panos pa...@acm.org wrote:
Anyway, I would appreciate if Ryan or somebody else who is familiar
with the implementation elaborate further on whether today's
implementation uses the ancestry hints when it decides how to
partition the application data.
it does! details in
I cant find the reference now, but the Datastore (and even memcache I
beleive) works as a single global 'entity', there is only one.
Transactions are global too, and the datastore is consistant.
basically you the application designer has to make so consideration if
the app runs on a single, or
I cant find the reference now, but the Datastore (and even memcache I
beleive) works as a single global 'entity', there is only one.
I agree that from an API usage perspective the Datastore is a single
global resource but typical single entity Datastore fetch times are
less than
Hi,
...typical single entity Datastore fetch times are
less than intercontinental IP packet travel times...
Maybe my assumption that GAE would spin up multiple web processes for
a single app dispersed around the globe is incorrect...
The first doesn't necessarily imply the second. Remember
