I'm kind of disappointed with Google's recent attitude change. When master/slave was all there was, it was deemed 'production worthy'. Now suddenly it's " If you are running a production service, you should not use Master/Slave datastore. Ever."
Given that the HR datastore has some pretty big problems from a user perspective (costs 3 times more, only supports Eventual consistency), it's not really feasable to use for production code in *every* instance. So I'm very disappointed to hear these kinds of comments coming from Google. You shouldn't make something, then complain when people use it. If you don't want people using Master/Slave, maybe you should remove it. To berate customers for preferring an option you *provide* is just mind blowing. -- 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.
