hatchware

You hit the nail on the head with kan.so. I'm not using pouchDB, want to but haven't needed it. As a couchApp I can do a lot of the heavy lifting on the backend through good use of lists, shows, and views. Then I sync large collections through dynamic queries and long polling. I will be bringing in backbone for this soon. The data we are dealing with is a good fit for the eventual consistency model so we do not have to worry about realtime mobile syncing. We do have a AWS server setup though that syncs with Cloudant and allows us to put a ELB in front with our Node service talking directly to couch on the AWS network. This allows us to install our own ssl cert and pass credentials.

This is actually a subject that is surprisingly simple. For package management we have been using Kan.so for npm style package management and deployment (pushing our app to a design doc). I would like to explore just using npm for this, but Kan.so got me there quickly and I learned a lot from the project. Check https://cloudant.com/blog/app-management/ for more. This has worked out really well for us and is easily managed across our team. We all have our own data and just share the code across Github then push with Kanso. Anytime we need example data we just replicate from each other then repush our couchapp and viola.

CORS support has not been an issue as we access our app on Cloudant directly through our couchapp then it does the work. On the backend we have nodejs listeners managing tasks through state that Couch cannot handle (emails, signups ...). If you need CORS support on the front end I suggest replicating your data to AWS and having them sync or better yet asking yourself if you really need it in the first place.

Feel free to hit me up @hatchware if you have anymore questions and subscribe to user-subscribe@couchdb.apache.org as it is a very active community.

I'm on here if anyone has any questions or would like to know more.

Awesome turn around on this one!