Re: [google-appengine] Re: Frameworks on GAE
Jeff... regarding your Objectify optimisations... I'd be interested in details if you have any to hand please :-) I've personally made the introspection stage lazy load (moving it to trigger inside the getMetadata methods)... it's probably limited in scope to my specific needs (I'm not using any polymorphic queries, and I've made assumptions that all entities are @cached)... but it does the trick for me and reduces startup time significantly on my 60+ entities. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/AwtigY9GOCEJ. 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.
Re: [google-appengine] Re: Frameworks on GAE
Look likes there's a niche for a new framework. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/9RiGLtk17W4J. 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.
RE: [google-appengine] Re: What are the pros and cons of using Google App engine for my startup?
Excuse my butting in guys... v interesting debate I tend to veer towards the "pro" app engine side of the argument myself. However, IMHO, the idea of implementing a decent SOA with different "subprojects" running on different instance environments is one of my own personal gripes. I can't quite agree that the use of "versions" is an adequate solution to the problem. If only Google allowed the Datastore to be shared across different applications then we'd be cooking with gas (I'd say the same for blob store, but cloud storage looks like its stealing it's crown there anyway). There's an issue raised for it which could benefit from a couple more stars if you agree :-) http://code.google.com/p/googleappengine/issues/detail?id=1300&can=5&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/gV3FDeHXezAJ. 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.
[google-appengine] Re: What are the pros and cons of using Google App engine for my startup?
Firstly, I've got to agree with all of the the comments made by Andrei Volgin... App Engine is an excellent environment for startups and, having made a similar decision to yourself a couple of years ago, I couldn't be happier with my choice. However, a word of caution for your specific requirement. The social networks rate limit some of their APIs to IP address. Being in App Engine means you're sharing your infrastructure (and IP addresses) with millions of other projects. This makes it almost impossible to connect to some (particularly Twitter) APIs. This might not be a problem if you're OAuthing specific users but its definitely worth checking out. To end on a positive note though... in the past 2 years, our startup business has benefited from having an infinitely scalable architecture coping with numerous unexpected traffic spikes (up to 40x on occasion), with 0% downtime ... all at a cost of <$350 a month. When you look at App Engine alongside its new bed fellows of Cloud SQL, Cloud Storage and Big Query... Google's Cloud Platform is frankly looking like a top notch choice. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/h4liRDYdi6kJ. 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.
[google-appengine] Re: How to solve the aggregate query with condition in Google App Engine
I'd say horses for courses on this one. IMHO the Datastore may not be the best fit to solving your requirement. Perhaps Cloud SQL or BigQuery might be better suited? Personally, i've consciously had to decide to make better use of all three; rather than hoping that Datastore'll solve all my needs (not saying that's necessarily what's happening here tho... don't get me wrong). Im starting to find the following:- Datastore's great for object persistence and basic querying With a bit of live indexing onto Cloud Sql i can achieve the more complex searches i need i copy Log type data into BigQuery for bigdata analytics. And i guess there's also a legitimate place for the full text search Api too (tho i personally haven't used it yet). -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/_QhhWG8HVkAJ. 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.
