Busy site? hr, it remains available for reads and writes during planned downtime and is extremely resilient in the face of catastrophic failure
2011/3/1 mscwd01 <[email protected]> > I've done my research but still cant fully decide whether to use the > High Replication or Master/Slave datastore. Hypothetically speaking, > if my app were to become popular it would require many reads and > writes (it's an advert serving platform). > > I realise the High Replication datastore uses more resources, is > slower reading and writing and would be more costly, but it does have > the reliability I need. On the contrary the Master/Slave is faster > which is important to me. > > Basically, what is the opinion of people who have used both in a > production environment? Should I stick with Master/Slave or make the > change before it's too late? > > Thanks > > -- > 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. > > -- gr, Wim den Ouden Custom Google App Engine <http://code.google.com/intl/nl/appengine/> based webapps <https://neighborshare.appspot.com/>. Free open source neighborshare framework <http://code.google.com/p/relat/>. -- 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.
