Skip to main content
This article is a little more involved than the nodejs community and detractors give it credit for. Taking a quote from the article as the quintessential challenge for nodejs instead of the use your tools properly.  While they share a like sentiment they are vastly different and have a deeper meaning.
What did we learn from this harrowing experience? First, we need to fully understand our dependencies before putting them into production.
I did some programming in nodejs when I was working on a zero downtime migration project. It worked and the nodejs tools were solid. My project failed when my SQL requests became more complicated than counting the number of rows in a table... when a number of round trips or consecutive queries were needed.

Install nodejs
$ brew install nodejs

Install expressjs
$ npm install express

Install hapi
$ npm install hapi

Both express and hapi required 24 packages.

Now that I installed them both... I created my first express project. Now I have installed another 54 module dependencies. When I performed the like hapijs task it did not install anything more than the original hapijs installation.

Grunt required a minimal number of packages while bower seemed to require about 50.

And now it comes to me. Looking at the console from the installation I performed above there was a small note that requires investigation:

> sqlite@1.0.4 preinstall /private/tmp/ha/node_modules/sqlite

Does this mean that all of the modules and submodules that I used to install in my projects as a dependency are now installed by default in nodejs? If so then this is even more egregious a design flaw as the netflix statement. I admit that I'm not certain these dependencies are preinstalled and the net side effect. I decided that I no longer have the time and inclination to pursue nodejs unless I'm getting paid and there are many more security reasons for compiled applications. That netflix suggested that deep dependency understanding is important only serves to reaffirm my position.


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…