We are looking at restructuring some of our calls, optimizing again for speed, we are thinking that rather than having a datastore call for a single cell, we'd serialize things. This makes searching suck, and we have had a few issues where serialized and unserialized data didn't quite match when we were done (because of weird encoded characters from sites)
Serializing also locks you in to a single data structure for the most part. We are also just considering: data as a zipped, delimited array uncompressed, delimited Double storing, so that we pay twice for writes, and can run analytics, but so that reads are against the serialized data, and faster and cost less. What are anyone's thoughts? Have you had these discussions with your dev team? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
