UNIX & cats

Both are individually awesome, and when mixed they are invincible (?)

In this post I’m sharing two videos: Continue reading


Disaster aftermath…

… or how companies choose to communicate with their users when the worst happens.

Two cases this week.
Go Daddy: http://www.godaddy.com/newscenter/release-view.aspx?news_item_id=410&isc=smtwlp&iphoneview=1
GitHub: https://github.com/blog/1261-github-availability-this-week

I can hear any excuses or reasons for GoDaddy’s way of detailing the problem, but I can’t help but love the level of honesty from GitHub and feel underestimated by GoDaddy.

nginx as a proxy server: farming & failover of a node.js app

While developing for high traffic projects I’ve encountered a common problem not to far into the planning process: how do you do application farming and failover, in a simple way?
First of all, I’ll make clear what I mean by farming and failover. Farming in my mind means a single entrance point through where the users access the server, a domain name, that hosts behind itself a “bunch of severs”, “instances” or “resources” that respond in a transparent manner to the request. Failover is the action taken when any of those “resources” fail to respond, by which load is redistributed automagically (auto and magically).
So both of these features are offered by a lot of services providers and software applications. Also, you always have the option to build one yourself. Since I’ve found paid solutions too expensive, and software apps too complicated, I was on the verge of writing my own load+fail balancer… until I started digging on nginx. Continue reading