“Recently, there’s been a lot of commotion on twitter and in #node.js about the new streams2 API. The official stream docs leave a lot to be desired, which has lead to general confusion. That’s too bad, because using new streams can really simplify your code once you understand how they work. Let me take you there…
If you’ve never used node streams before, I highly recommend you read Max Ogden’s introduction. For the lazy: a stream pipes data from a “source” to a “sink” without reading the entire dataset into memory all at once. (Think unix pipe, but for node.)…”
“More and more we see an intersection between science and hypnosis. Following is physicst Richard Feynman on hypnosis, which is great reading for anyone interested in understanding what being hypnotized is like. This is excerpted directly from page 67 of his autobiography “Surely You’re Joking, Mr. Feynman!”
As it turns out, curious, brilliant minds like to see what hypnosis is all about.”
“I had interview for the Flask book recently and some questions were related to realtime functionality – how it works, how to integrate realtime portion with conventional WSGI applications, how to structure application code and so on.
We used Google Hangouts and it was supposed to record interview, but it failed. So, I decided to write elaborate blog post instead, in which I will try to cover basics, give short introduction into asynchronous programming in Python, etc…”
“Distributed systems are characterized by exchanging state over high-latency or unreliable links. The system must be robust to both node and network failure if it is to operate reliably–however, not all systems satisfy the safety invariants we’d like. In this article, we’ll explore some of the design considerations of distributed databases, and how they respond to network partitions.
IP networks may arbitrarily drop, delay, reorder, or duplicate messages send between nodes–so many distributed systems use TCP to prevent reordered and duplicate messages. However, TCP/IP is still fundamentally asynchronous: the network may arbitrarily delay messages, and connections may drop at any time. Moreover, failure detection is unreliable: it may be impossible to determine whether a node has died, the network connection has dropped, or things are just slower than expected…”
“Dokku is a mini-Heroku powered by Docker written in less than 100 lines of Bash. Once it’s set up on a host, you can push Heroku-compatible applications to it via Git. They’ll build using Heroku buildpacks and then run in isolated containers. The end result is your own, single-host version of Heroku.
Dokku is under 100 lines because it’s built out of several components that do most of the heavy lifting: Docker, Buildstep, and gitreceive…”
“When businesses implement an automation strategy for new or existing technology, proper development and deployment technologies are overlooked. Deployment to Production should not only be low risk, but also take seconds.
Even for this silly static content blog, I have set up a seamless, zero-configuration system using Docker…”