Ssssshhhh Telling all my secrets :-)
We are actually looking at using MS as the "front" and "HR" as the Back. This seems to work well enough. The "no write" periods of time are such that it is doable for our needs. For our need the expire time on datastore makes this possible. For others this would require writing your own synchronization logic to make sure both versions were up to date after maintenance. For us the bigger factor was that MS is faster than HR, and we are trying to decide if the average is faster in a tiered approach or not. From: [email protected] [mailto:[email protected]] On Behalf Of Ikai Lan (Google) Sent: Wednesday, May 25, 2011 1:43 PM To: Google App Engine Subject: Re: [google-appengine] Re: Why an app can't be Master/Slave and High Replication hybrid? There are a few reasons, but they are implementation details. This is significantly more work than it looks like from the outside. It also isn't something we're currently pursuing. That being said, if you really need the characteristics of both, I suppose you could have two applications and use URLfetch to talk between them. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Wed, May 25, 2011 at 9:22 AM, Robert Kluin <[email protected]> wrote: It will not be exactly what you're looking for, but you could look at EVENTUAL_CONSISTENCY. See the create_config function. http://code.google.com/appengine/docs/python/datastore/functions.html#alloca te_id_range Robert On Mon, May 23, 2011 at 06:29, Brendan Doherty <[email protected]> wrote: > This is what a hybrid would mean to me: > Some entities are very important and require High Replication. Some tables > are just generated data which could be reproduced easily and don't require > the high availability. > > -- > 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] <mailto:google-appengine%[email protected]> . > 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 [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:google-appengine%[email protected]> . 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 [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. -- 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.
