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.
Sure we can't all be the genius architect I am (or possibly as good at dissecting other people's information) but you trade what you store and how you store it, in order to optimize for the platform. But again it always comes back to people trying to make GAE act like other platforms, It isn't. Is it better? Guess that depends on if you Like Ruby's Philosophy of there are 10 ways to do everything, and not Wrong answers. Or Python's There is only one way to do something and that way will be right. GAE is about understanding what you need to do, and optimizing for the way GAE wants you to do it. To Be honest I have never worked in a platform so Rigid in architecture, or so limitless in potential. I think "creative" problem solvers don't thrive on GAE. The rigidity stifles them as they attempt to solve problems that don't need to be solved. And Architects thrive because the Lego Pieces to play with are so abundant. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Schnitzer Sent: Wednesday, December 14, 2011 2:11 PM To: [email protected] Subject: Re: [google-appengine] Re: Isn't .08/hr 1.92/day $59.52/month for a 600 MHZ CPU instance with 128 MB memory a LITTLE EXPENSIVE On Wed, Dec 14, 2011 at 5:36 PM, Brandon Wirtz <[email protected]> wrote: > But if you are building Data Intense apps you can't touch it on price. Only if you can use the indexes provided. If you need a slightly different index (say, a spatial index), you're forced to maintain it in a third-party cloud. This was one of the original design goals for Backends; I recall one of Ikai's posts describing a fulltext search index as a use case. And yet backends are totally useless as index repositories because they're priced 10X what it would cost to put the index *anywhere* else. 1) You can't use backends as fast indexes because they are too expensive. 2) You can't use backends as persistent state because they aren't reliable enough. What can you use them for? They let you execute a single task longer than 10minutes. Pretty weak sauce. They could have solved that problem just by enabling long-running frontend requests url-by-url in the app.yaml - that wouldn't require me to split my code and create separate deployment modules. I love Appengine, but Backends are a non-feature just like Email. It would be better if Google engineers didn't waste their time creating features nobody can use. 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. -- 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.
