Yeah, yeah, I know that many of my old M/S applications are running on the 
officially deprecated database. And I know that they might suffer a little more 
downtime as a result. But I also know that they are working just fine, and I'm 
not particularly interested in going through the pain of migrating 
(particularly working around all those annoying consistency things -- I've done 
that twice now, and each time it took quite a lot of programming to hide this 
stuff from the users).

So the question: Is this notice just a helpful reminder, or is there an 
implicit "or else" between the lines that I'm not seeing?

-Joshua

On Aug 24, 2012, at 9:10 AM, Google App Engine <[email protected]> 
wrote:

> Dear App Engine Developer, 
> 
> We’ve noticed that you are running at least one application configured to use 
> the Master/Slave (M/S) datastore. This application configuration was 
> officially deprecated on April 4, 2012, in accordance with our deprecation 
> policy, in favor of the more reliable High Replication Datastore (HRD). HRD 
> uses the Paxos algorithm to serve your application out of multiple 
> datacenters, meaning better redundancy in the face of datacenter issues, more 
> consistent datastore performance, and no planned downtime. 
> 
> When we deprecated the M/S datastore, we introduced a migration tool that 
> allows you to easily migrate all your datastore and blobstore data to a new 
> HRD application. Migrating your application will not require you to change 
> your application’s URL, whether it serves from appspot.com or a custom domin. 
> Please note that even if your application does not store any data in the 
> datastore, it will still benefit from the automated datacenter failover that 
> is only available to HRD applications. 
> 
> Before migrating your application, you should read about the differences 
> between M/S and HRD, and understand how the consistency policy for HRD might 
> affect the queries in your application. 
> 
> All HRD applications that have billing enabled are covered by App Engine’s 
> 99.95% uptime SLA. Along with the substantial reliability improvements, many 
> new App Engine features are only being made available to HRD applications, 
> including the Python 2.7 language option, Full Text Search (FTS), and Page 
> Speed integration. 
> 
> We strongly encourage you to migrate your applications as soon as possible. 
> If you have technical questions about HRD or the migration process, you can 
> post them to Stack Overflow. Any general migration discussions can be posted 
> to our Google Group. 
> 
> 
> Thank You,
> 
> The App Engine Team 
> 
> © 2012 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043 
> You have received this mandatory email service announcement to update you 
> about important changes to your Google App Engine account.

-- 
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.

Reply via email to