I love using CouchDb. It can sometimes frustrate me to the border of insanity but most of the time it lives up to its "time to relax" byline. Its design functions (views, lists and shows) are written in JavaScript and since I use Node for back-end it means that I…
I think I've previously written on my desire to not be locked-in nor to be in "lock-in" business model (whatever its mask may be). I've designed Nido and MemOfSim from ground up with this committment. But as I was asking Orchestrate.io on what they mean by "zero lock-in" it…
Recently I stumbled on Orchestrate service: Orchestrate unifies multiple databases through one simple REST API. Orchestrate runs as a service and supports queries like full-text search, events, graph, and key/value. Orchestrate handles security, monitoring, backups, and replication. There are no licenses to buy, no software to download, no hidden…
This originally appeared on coderwall. Today I ran into an issue with Heroku and the way its official buildpack for Node caches node_modules. Namely, I was forced to fork a couple of modules so I updated package.json to point to GitHub repositories (see this tip). Unfortunately, Heroku stubbornly…
This originally appeared on coderwall. I have read How to fork & patch npm modules and followed the instructions but I couldn't make it work for me. Looking at npm log I figured that the problem was with zip files being downloaded and not tarballs. So here's the trick on…
During development I often host an express server for frontend and one or more backends in a single node process. They all listen on different ports and communicate over HTTP, keeping the modules completely separated and the interfaces clean. But that doesn't work on Heroku which gives each dyno just…