Deploy to Linode and wait or go direct to AWS?
Hi guys,
I know this been asked a gazillion time in different form but ...
we''re about to launch our startup (matchFWD) and need a true hosting solution. We're tempted to go with Linode as it's cheap and easy to set-up and deal with the fact that we'll need more in a few months when it's time... or go directly to AWS, take the extra time to set it up and be done with it.
Any advice and experience with either approach ?
Thanks,
(
12 comments
| 6 points
| on HN
)
My advice would be to use a DevOps tool like Puppet or Chef to create recipes to make deploying new infrastructure as painless as possible. If you take it far enough, it could completely build your new infrastructure in a new datacenter, but even in its simplest form it will help you when it comes time to migrate. Spooling up more nodes in your current datacenter to handle spikes in traffic becomes much easier, too.
A friend has been talking to my lead dev quite a bit about Chef. I'll spin it to him again.
Also, you have to think about possible downtime migrating from Linode to AWS (or increasing your Linode resources) or setting up a mechanism for no-downtime.
I agree with what you say here: "go directly to AWS, take the extra time to set it up and be done with it." To me, if the initial time/resource cost is negligible (which in this case, IMHO, it is), I'm going for the permanent solution instead of what seems to be a stop-gap solution. Less headaches, more time to devote to other parts of your start-up at a time of growth where your time and resources will be scarce, and fewer things to worry about. I'd rather pay the time up front when I'm still starting out, rather than later where it will be more difficult and most probably more costly.
This applies only because you already know AWS is the end-game. Otherwise, I'd just launch in Linode first since it's quick and I (and you) know how it works already, then deal with scaling later when you actually know you need to scale.
And don't knock Linode; it can take a beating.
Using Linode for my app and host static files on S3 and maybe another cloud provider like Rackspace for failover in case the clouds go down.
I am hoping that I would have a luxury problem once my app is doing well. When I have that kind of traction, it's a different story. But until then, it's more logical to stick with a VPS.
By the way, are you making updates to your production site frequently? Your carousel isn't working correctly yet.
I know you use django (from another post I think). Have you thought about using social network login? I used django-allauth and it has been working very well for me. Good luck!
We currently our own LinkedIn login to create account as we use their API to match candidates and jobs. Next step is to add Facebook and Twitter as alternative login.
We were thinking to go with django social-auth to cover al bases. http://uswaretech.com/blog/2009/08/django-socialauth-login-v...
Had you compared it to allauth ? I'll take a look, hadn't seen that one.
thxs !
AWS is somewhat expensive and doesn't deliver the same performance as Linode type hosts.
The only advantage to EC2 is the insane flexibility it allows (i.e. dynamically spawn new nodes based on traffic)
To start off, I'd go with Linode or Rackspace. Keep it simple. Worry about scaling later.