Hi, I think that the Appengine team is recommending that folks use the HR datastore for new applications.
That said the only benefit seems to be that you can write to the datastore even during maintenance so if that is not important to you, and your data is likely to be very large then master/slave might be a better choice. If I were you I would probably go with HR. Ian On Tue, Mar 1, 2011 at 8:41 PM, mscwd01 <[email protected]> wrote: > 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. > > -- Ian http://www.ianlewis.org/ -- 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.
