Linode Is Dead, Long Live Amazon Web Services



Prior to our incorporation, we hosted sites that we managed on shared servers such as Hostony and 1and1. The cost per month per server for a shared server was ~$10. Just as virtualisation was getting hot we got introduced to Linode. For a bunch of techies getting root access to a production ready server for $20 was too good to resist. On top of that Linode had pretty decent support docs and a neat interface to get going quickly. We got onboard and stuck with them for 4.5 years. But all the goodness of Linode started to get dated. Rackspace, Amazon Web Services (AWS), Google App Engine and many other cloud computing providers had surfaced and were providing even greater control and pay-as-you-go pricing but the inertia to switch and acclimatise was too high. It’s not that we didn’t study the pros and cons of Linode’s alternatives, and it’s not that we didn’t provide AWS and other cloud computing providers as hosting options to our clients, but realistically the traffic we estimated for our clients made them fit in Linode’s pricing sweet spot.

So, what happened? Why did we move?

In a nutshell, it was an experience with them that made us realise that Linode was going extinct, and that if we continued overpaying an endling believing it was competitive with others in its species, we’d soon be defunct too.

Continue reading

Vade Mecum


Android SDK
Android API Guides
Android API Reference

AngularJS
Guide to AngularJS Documentation
AngularJS API Docs

Cordova
Apache Cordova Documentation

GIT
Git Tutorial: A Comprehensive Guide
git – the simple guide
Comparing Workflows
A Successful Git Branching Model
Revert to a previous Git commit

iOS SDK
iOS Developer Library

Laravel
Official Documentation
Laracasts

MongoDB
Official Documentation
Webinar: Back To Basics 1: Thinking In Documents

NodeJS
Node.js Manual & Documentation

RegEx
Learn Regex The Hard Way

Utilities
RegExr

Analytics

And We’re Back…


  • September 2014
    • Back in Business: I sweated it out as an employee and left that company with the 2011 keeda still in me. In the middle of defining the next product to work on, new projects started trickling in and the decision to restart Tacto was made in an instant. We’re on a new journey with a new & growing team working with new technologies and on new problems and solutions!

    Continue reading