On Wed, Dec 14, 2011 at 6:29 PM, Brandon Wirtz <[email protected]> wrote: > I have a spatial Index running on GAE using Calculated Tessellations as > indexed values. Based on a talk given by someone at Google About How they > optimized map searches for doing "with in radius" searches.
Yeah yeah yeah, we can (and often do) come up with workarounds when necessary. I use geohashing in a couple of my production apps. But it these workarounds provide *very* narrow bounds around the problem domain. One change to the sort, or one more inequality, and all bets are off. And that only works if your index is a well-known problem domain. I was one of the early testers of Backends and used it for the index that makes http://www.similarity.com/ run. I thought it was great. Then Google announced pricing, and I quickly migrated the index to rackspace cloud for one sixth the price. I'm not saying there isn't always a workaround. But often that workaround is "abandon GAE for part of your application". Of the four major (and wildly-different) applications I've built on GAE, all have required this "workaround". I'm pretty ok with that, except when the only reason it's necessary is because of a bonkers pricing decision. Jeff -- 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.
