On Sep 2, 2010, at 2:05 PM, harryf wrote: > > This is kind of a re-post of a question I asked on stackoverflow - > http://stackoverflow.com/questions/3630641/whats-the-most-productive-frontend-framework-to-use-with-solr-as-the-backend/ > which Massimo invited me to ask here. > > To repeat, I want to build a web app using SOLR as the backend ( no > RDBMS or other backend ). Most of the data will be stored in SOLR via > offline jobs but there is some need for CRUD from the web app. The > schema will probably move fairly slowly ( in fact it already exists ) > so creating / changing models manually is acceptable from a > maintenance point of view. > > Have only got so far as a web2py "Hello World" so don't have deep > insight but would appreciate any hints on how this might be > accomplished in web2py. Also if anyone has any general experience of > using web2py with a RESTful backend as the primary data source, would > be great to hear about it.
My main web2py application is a manager for a collection of servers running my company's network services. The server API is xml-rpc, but I imagine that a RESTful API would work just as well. I have a local database for users, and another one that basically provides access info for the managed servers. The servers themselves I treat as a kind of distributed "database". Not that I try to do SQL or anything, but in that they store their own data, and I don't try to keep local copies of it (except for backup & restore, which is another matter). It works quite well. I encapsulate each managed server in its own object, and use threads so that I can talk to a bunch of them in parallel when I need to. I'm pleased with the way it turned out.
