News for hackers. Stuff that matters.

A comment on Netflix: Lessons We’ve Learned Using AWS. Parent comment

Re:Netflix: Lessons We’ve Learned Using AWS by recampbell on Thursday December 16, 2010 @02:50PM (#2013333)
Having built a non-trivial production system, I have a love-hate relationship with AWS. I love the possibilities and potential, but I'm deeply disappointed when it fails to live up to the hype.

It's just a matter of alternatives. There's frankly no other IaaS out there that can match the features of EC2 (eg, EBS, elastic IP). These guys are unstoppable, they come out with more features every week.

[ Parent | on HN ]
Re:Netflix: Lessons We’ve Learned Using AWS by wmf on Thursday December 16, 2010 @03:01PM (#2013384)
Yeah, EC2 is the best cloud but it's a shame that it's still missing features that ESX 2.0 had (and Amazon has shown no interest in fixing it).
[ Parent | on HN ]
Re:Netflix: Lessons We’ve Learned Using AWS by jeffbarr on Thursday December 16, 2010 @04:06PM (#2013682)
Wes, what features are you looking for?
[ Parent | on HN ]
Re:Netflix: Lessons We’ve Learned Using AWS by agmiklas on Thursday December 16, 2010 @07:08PM (#2014488)
Not the original poster, but here's some stuff I really wish AWS had:

a) Ability to map an elastic IP to an ELB. The CNAME thing it uses now has way too many drawbacks [1].

b) Ability to make an RDS instance a slave to or a master for a normal MySQL instance. This would make it possible to use RDS as a backup to our ordinary DB infrastructure using normal MySQL replication (and eventually, vice versa)

c) Retention periods for EBS snapshots. You can get this yourself by writing a few simple scripts, but it would be really nice if snapshots could simply be labelled "delete after 90 days".

d) A cross-availability zone, synchronously replicated EBS volume. This is probably fairly specific to our use case, but it would be neat if AWS natively provided something like DRBD.

[1] http://blog.pagerduty.com/2010/08/31/load-balancers-need-sta...

[ Parent | on HN ]
Re:Netflix: Lessons We’ve Learned Using AWS by wmf on Thursday December 16, 2010 @04:50PM (#2013893)
It's not me in particular, but if you read the EC2 forum going back to 2006 people have been asking for full virtualization, multiple IPs, multicast, non-NAT, reverse ARP, shared EBS, etc.
[ Parent | on HN ]
Re:Netflix: Lessons We’ve Learned Using AWS by bmurphy on Thursday December 16, 2010 @10:25PM (#2015021)
Disk I/O performance that doesn't suck.

Let us add dev pay instances to an ELB.

More ram.

Elastic private ip addresses.

Change security groups of running instances.

I have a lot more, but those are my big ones.

[ Parent | on HN ]
Re:Netflix: Lessons We’ve Learned Using AWS by jollojou on Friday December 17, 2010 @01:36AM (#2015466)
While it is true that you cannot add new ones or remove existing ones, you can modify an existing security group of a running instance: http://aws.amazon.com/articles/1145?_encoding=UTF8&jiveR....
[ Parent | on HN ]
Re:Netflix: Lessons We’ve Learned Using AWS by gcr on Thursday December 16, 2010 @04:39PM (#2013840)
Do you work with AWS?
[ Parent | on HN ]