You may also have a slight misconception - the write limit applies to
each individual entity, not the entity as a class. So you can only
update Thing1 once per second, but you can also update Thing2 once per
second, etc. You should have no problem being able to handle
creation of lots of same
I am thinking of using Google App Engine for next web application, but
have some concerns about Datastore (High Replication Datastore). In
video explaining High Replication Datastore they told that writes take
some time (45 ms). As I understand that means that many users won't be
able to update
Of Andrew Romanov
Sent: Saturday, December 10, 2011 9:40 PM
To: Google App Engine
Subject: [google-appengine] Datastore question
I am thinking of using Google App Engine for next web application, but have
some concerns about Datastore (High Replication Datastore). In video
explaining High Replication
Hello,
I am a newbie to Datastore. Here's what I am trying to accomplish:
Trying to set an Unowned one-to-many relationship between 2 objects. (I
chose unowned because I wasn't sure if I could have an owned
many-to-many. Also wasn't sure if lazy loading is available for the
children. Is owned
Hi,
I'm very new to GAE and was curous if there is a performance penalty
with regards to queries and exploding indices, etc. etc... if one
implements tags (a list of category names for a record if you will) as
dynamic properties vs. just listdb.Category.
As a dynamic property I was thinking a
Hi Guys,
My app is Twitterautofollow. I have a question about the quota, basically
my app was serving between 6-13 requests a second and jumped up to 32
requests per-second and subsequently went over the quota. I am not sure
where the 32 requests a second are comming from although some of them
