Master/Slave Datastore Deprecation Question

[John Wheeler]

When the master slave datastore becomes deprecated, does that mean Google will shut down applications that are using it or just stop supporting it? If it's the latter, what exactly does that mean? For example, will the Master/Slave maintenance periods stop where they flush the memcache or whatever?

John

[Darien Caldwell]

It's already depreciated. It will cease to exist when the deadline arrives.

[John Wheeler]

Hi Darien,

Can you point me to the documentation or information that explains that it will 'cease to exist'? Are you just assuming that or did you read that from a reliable source?

Thanks,

John

--
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/3SymDhYn7mA/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Rafael]

Hi John,

I was at the same boat one month ago. 

The migration was far easier than what I expected. It was just a push of a button and my app is very complex. 

What isn't clear in the documentation and made me think that the migration would be difficult, is that the old app url's with blob keys are actually made as links back to the old app. So it was actually just a push of a migrate button. 

thanks

rafa

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.

[Joshua Smith]

On May 2, 2013, at 9:42 PM, Rafael <mufu...@gmail.com> wrote:

The migration was far easier than what I expected. It was just a push of a button and my app is very complex. 

Lucky for you, but that has not been my experience at all.

In particular, a user can make an update, and then any query made in the next few seconds doesn't return that change. Hiding this from the user requires lots and lots of extra programming.

-Joshua

[Vinny P]

Hello John,

This mailing list isn't the best place for discussions on the Master/Slave datastore. As per the M/S deprecation notice at http://googleappengine.blogspot.com/2012/04/masterslave-datastore-thanks-for-all.html you should be posting M/S related questions to the dedicated mailing list at https://groups.google.com/forum/?fromgroups=#!forum/ms-datastore-deprecation (you need to request an invite to join the group, so be prepared to explain why you need M/S).

Just as a side note, if you don't absolutely need M/S, it's better to migrate to HRD. Yes it can be a bit of a pain, but MS has its occasional outages and slowtimes, and it doesn't support some of the newer features such as PageSpeed.

-----------------

-Vinny P

Technology & Media Advisor

Chicago, IL

My Go side project: http://invalidmail.com/

[Darien Caldwell]

I base that on my interpretation of Google's Depreciation policy:

 

https://developers.google.com/appengine/terms

 

Section 7.3

 

The original terms at the time of the Master/Slave depreciation was for 3 years, so I believe Google still has to honor that timeframe. But after that time is up, They are under no obligation to continue to offer or support the Master/Slave datastore.  I wouldn't make any bets on it continuing to operate.

 

As for the read/write issues, I found the simplest way to handle it is to make good use of Memcache. Store any new data writes in Memcache, and check Memcache before doing any Datastore reads. This way you'll always get the latest data.

[Jeff Schnitzer]

The future of the M/S datastore is:  Increasing neglect and decreasing reliability until at some arbitrary point in the future Google puts a bullet in it completely.

Migrate now.

Jeff

On Thu, May 2, 2013 at 1:36 PM, John Wheeler <jo...@highvolumeseller.com> wrote:

--

You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.