Yes, 1 post a minute is fine. Even 1 write a second is fine. Where you will run into issues is when your application does something like ~hundreds of writes a second. There are very few systems that will do this well, and you will have to start looking into sharding your writes - but for now this is a premature optimization.
-- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com On Thu, Jan 26, 2012 at 1:57 PM, Andrei-Ştefăniţă Cocorean < [email protected]> wrote: > Hi, > > I want to develop a web service which will be used by a few thousand > clients to save new pieces of data at a rate of aprox. 1 post/minute. I've > been looking at what App Engine has to offer but I'm not sure if it's the > right platform for this kind of system. At a glance it seems the datastore > is optimized for efficient reads, but not so much for write intensive > applications. > > I'd appreciate any help on deciding whether it's worth to try and build > this service on App Engine. Also, if you implemented something similar I'd > be interested in hearing what problems you encountered along the way. > > Regards, > Andrei > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/bW3pKqHKcSEJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
