Thank you for your update and insight. Maybe I was seeing a trend where there is none.
Actually, there are two separate considerations: (1) some products are replaced by other products, generally for the better, and developpers should plan for migration, this is life I guess, and it's ok as long as there is enough anticipation and not too profound disruption, it's fine. (2) in at least two cases (search and memcache) the replacement product is not a pure API, not "as a service", it has to be deployed on a number of server instances, whereas the former product was a simple service. Maybe it's not a trend, maybe just two isolated cases. But it does have adverse consequences in terms of increased cost and of increased complexity. The Datastore to Firestore migration, on the contrary, seems to be in perfect continuity, both in terms of api (when the Python 3 api comes out of beta) and of billing (I have not looked much into that later point actually). -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/ca4160e5-2037-4c4e-9dfb-c043dfb2c681%40googlegroups.com.
