If you schedule writes it is not a big deal. I have several apps (admittedly not yet ported to GAE) that I only update the data from time to time.
Recipe Databases, little league stats. In those cases you just delay the write, no big deal. This doesn't work for everything, but there are definitely cases where M/S makes sense From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of vlad Sent: Saturday, March 05, 2011 2:43 PM To: google-appengine@googlegroups.com Subject: [google-appengine] Re: HR Vs. Master-Slave Comparison. Is it worth extra cost? "Mission Critical" is just "PR packaging" around a simple fact that Master/Slave has serious performance issues and team is giving up on it. That was my read on the situation and now Ikal is confirming it. Ikal, thank you - it takes balls to admit a failure. This is a dev forum so no need to sugar coat things too much. I too feel like Darien mostly because 3x pricing bump for HR. I am not a all concerned about eventual consistency issues. Just wondering if you take a regular car with 4 wheels (M/S) and add 8 more wheels does it make it better? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
