2009/9/3 Julian Todd <[email protected]>: > Can I suggest to people use Google App Engine for such a stand-alone > data-gathering project? > http://code.google.com/appengine/
I've been using it out of interest for a personal project (http://www.matchfixed.com). I quite like developing with it, and of course it's theoretically stable and scalable, but I'm not sure how it solves the problems of (a) getting developers to code something together, and (b) encouraging people to use the twfy API...? (Beyond just using Google Code as-is, that is) The cons are: - unfamiliar data modelling paradigm (it's not too hard to think about, but if we're trying to lower barriers to involvement, this might not be a good idea) - need to understand the unique constraints and code defensively around them (again, this needs some investment in understanding the platform) - lack of control over the deployment environment often makes debugging quite hard The pro is simple: - very cheap scalability I think that's it! Seb > > Deposit the code in google code and deploy from it. > > I'd like to see how viable the platform is for getting developers to > code something together. > > If it succeeds, then it could be the place we point people towards for > doing something useful with, for example, the TheyWorkForYou API. (So > far, nothing has come of it.) > > Julian. > > _______________________________________________ > Mailing list [email protected] > Archive, settings, or unsubscribe: > https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public > -- skype: seb.bacon mobile: 07790 939224 _______________________________________________ Mailing list [email protected] Archive, settings, or unsubscribe: https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public
