I think it would be great if GAE had better support for restoration of accidental deletes. For example, if you could store a unique Id for a transaction and somehow undo all the writes/deletes later. That would be great.
Given the nature of distributed systems, and the complexity required in engineering them, and the backup tools already provided, it seems obvious that the most likely error states wrt data loss will be bugged code or devops error. Effectively, managed data removes the traditional data loss mechanisms, so it makes sense for GAE to provide supportive tools in this space. I'd be interested if anyone has used the data store versioning features - do they scale and perform well in the real world? I've not heard anyone else even acknowledge them let alone that they use them. I'd love to get a recommendation on whether it's worth using. Re: deleting data - historically I've favored using a delete flag on important entities, and filtering those out in queries. This was pragmatic and also relatively favored by the platform before the delete costs changed. -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/c16a43ab-0789-443a-923e-4e24276112d6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
