Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've been using:

Server side: Apache Web Server CouchDB Perl or Python

Client side: Pouchdb jQuery Bootstrap Moustache/Handlebars

On client side that toolset provides an almost seamless API that gets you authorization, authentication, offline/mobile first, and data sync among all connected devices. And it's a very fast app because it runs almost entirely on the client side and transfers very little data between the client and server.

There's not a lot to do on the server side with this setup. PouchDB/CouchDB work together to handle the CRUD routines for both the client and server side and to sync data automatically and/or on-demand when the client is online.

You can also setup a 2nd CouchDB on a remote server to replicate your data to for automated backups. And it's fairly easy to configure a cluster of CouchDB servers with load balancing.

Productivity is what we're really looking for in a framework. To achieve that you want a very low learning curve and a very rich feature set. You want to leverage what you already know, as opposed to "learning a new way" to do things.

For me, this "stack" provided that.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: