I'm using CouchDB and Apache Web server on Ubuntu 16.04 on the server side and PouchDB, Bootstrap, and JQuery on the client side. While maybe not a "Stack" in t

I'm using CouchDB and Apache Web server on Ubuntu 16.04 on the server side and PouchDB, Bootstrap, and JQuery on the client side. While maybe not a "Stack" in the traditional sense it's a solid approach with a lot of benefits. Personally, I believe this is a sweet spot right now that's mostly being overlooked. CouchDB and PouchDB have come a long way in the past two years. They are now solid and offer an incredibly rich API that's well documented with a lot of example code and an active and helpful user base to help keep you moving forward. It may not sound as jazzy or have the media hype of some of the newer tools out there, like React and Angular, but once you start building with them you'll find things come together quickly. I've not dug too deep into CouchDB "Views" yet but that's another powerful tool to get and present data that is very fast and efficient. Since almost everything is written in Javascript you have a huge number of existing libraries of code you can drop in to add needed features and you end up with an app that runs almost entirely on the client side, and can run offline there if you want or need it to. When you add "Service Workers" to cache those app files the web server doesn't do much besides deliver the app once and update it as directed. In this setup the Apache web server is redundant since CouchDB is also a web server. I use it because I'm familiar with it and it provides an option to separate the DB server from the app file server that I figured might offer some management and scalability benefits. So far I haven't come close to needing that, but I didn't have to spend anytime learning how to configure the CouchDB web server so I saved a bit there. YMMV