Will this release have an impact on the latencies and error rates for applications that use (and will use) Master/Slave ? (hopefully in a better way) I was wondering if the increase of the latencies and errors in the last few months were caused by the intense work of making the new option available.
On Jan 6, 3:19 pm, Alexander Maslov <[email protected]> wrote: > I have tried to post this comment GAE blog, but my message was deleted > several times. So let me post it here. > > Thanks for this update. The is one think I would like to comment. Why do you > limit developers to use only one datastore per app? It mite be much better > to include additional parameter in datastore API to allow developers to > access data in both datastores. As application developer it's hard to tell > before hand what replication method better for any specific application. > Personally I prefer more reliable solution for any project. But in some > large applications there mite be some critical data and some less important > data. > > Speaking about current implementation. It's really weird that we do not have > any way to migrate to High Replication Datastore without creating new > application. It mite look not a big issue from Google's point of view, but > that makes a lot of troubles to those developers, who use appspot.com domain > to host applications. New application name means new domain name, etc. -- 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.
