Great job ermouth, you are always on the front line on pushing couchapp borders!
JS rewrites seems to really enable them to any kind of use. Performance may be a limit if you are really interested to squeeze each available cpu cycle, ok.... but, from a business perspective, how does it cost to reach and mantain this speed? May be an interesting question for your article too. For me, choosing a 1-tier architecture(couchdb with js rewrites and default vhost) over the usual 3-tier(web-app-db) is mostly a matter of costs. Choosing couchdb means keeping costs low by choosing extreme ease of development(in-browser development, same javascript language for frontend and backend) ease of maintenance and reduced set of skills(one server only to learn, configure and mantain with no licenses). Would I mind spending some more bucks on hardware (which keeps constantly improving and getting cheaper) to reach the same performance level of a more complicated and thus expensive architecture? Of course not. Thanks for your work, --Giovanni 2016-09-02 0:00 GMT+02:00 ermouth <[email protected]>: > Tried out more or less pure couchapp approach in 2016 realities, I mean JS > rewrites and PouchDB. > > Written down a story about the project, from the couchapp side: > http://lesorub.pro/how-it-works > > It was interesting experience, couchapps still might be useful, in very > rare cases ) > > ermouth >
