News for hackers. Stuff that matters.
Re:How AWS came to be by albasha on Saturday July 02, 2016 @05:00PM (#12023771)
Still, don't use AWS for your new startup. Move to it once you outgrow the offers from Linode and DigitalOcean. You'll save a ton of money.
Re:How AWS came to be by Johnie on Saturday July 02, 2016 @05:21PM (#12023831)
As a startup, how is this cheaper than the AWS free tier?[1] Once you outgrow the free tier, you'd also outgrow Linode and DigitalOcean.

[1] https://aws.amazon.com/free/

Re:How AWS came to be by billmalarky on Saturday July 02, 2016 @07:07PM (#12024124)
AWS is incredibly convenient, but it's priced at a premium. The main cost liability to building on AWS is the cost of bandwidth is insane, 5X the cost of DigitalOcean or Linode, 10X the cost of co-location.

Of course this depends on the type of startup you are building, a video startup is gonna be crazy expensive on AWS, Non-media heavy SAAS it may not matter.

Of course you can always build on AWS and place a caching layer in front of your bandwidth heavy media using DigitalOcean boxes to save big.

Re:How AWS came to be by webtechgal on Sunday July 03, 2016 @04:50AM (#12025287)
> Of course you can always build on AWS and place a caching layer in front of your bandwidth heavy media using DigitalOcean boxes to save big.

This IS a brilliant idea!!

Re:How AWS came to be by billmalarky on Sunday July 03, 2016 @04:10PM (#12027412)
I like reactions like that to my suggestions!

I'm building a video startup so bandwidth solutions have been on my mind these days.

Re:How AWS came to be by psadauskas on Saturday July 02, 2016 @06:13PM (#12023965)
I agree, the AWS free tier is incredible for getting a project off the ground. For a side project of mine, I'm spending a little over $10/mo on AWS:

- 2x 1GB instances (one free, one $10/mo)

- Free ELB to load-balance between them

- Free 1GB Postgres RDS

Then I spend less than a buck or two a month when I spin up a c4.large for a few minutes to compile a new AMI periodically. This would all cost at least 3-4x on something like Linode or Digital Ocean.

Re:How AWS came to be by albasha on Saturday July 02, 2016 @07:08PM (#12024127)
And when the year is over, you'll be paying +$50/mo for your setup instead of $5.
Re:How AWS came to be by psadauskas on Saturday July 02, 2016 @08:40PM (#12024345)
Well, $30/mo. As opposed to the $40 I'd be paying DO for the same setup, except I had to do the load balancer and database myself.
Re:How AWS came to be by Scarbutt on Saturday July 02, 2016 @05:32PM (#12023865)
ermm, AWS is not just about virtual private servers.
[dead]
Re:How AWS came to be by Scarbutt on Saturday July 02, 2016 @09:13PM (#12024430)
yep, you are pretty clueless.
Re:How AWS came to be by dang on Sunday July 03, 2016 @03:34AM (#12025136)
This comment breaks the HN guidelines, obviously, and I've already warned you recently not to do this (https://news.ycombinator.com/item?id=11784145). It doesn't matter whether the other person is breaking the rules, being provocative, or whatever. Please don't do it again or we'll end up having to ban you as well.
[dead]
Re:How AWS came to be by dang on Sunday July 03, 2016 @03:34AM (#12025137)
We've banned this account for repeatedly breaking the HN guidelines.