<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/etech_amazon_cto_aws.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2009:/1/tag:72.47.210.69,2007://1.3647-</id>
  <updated>2009-10-30T14:51:43Z</updated>
  <title>Comments for ETech: Amazon CTO Werner Vogels on Building Web-Scale Computing</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.23-en</generator>
  <entry>
    <id>tag:72.47.210.69,2007://1.3647</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/etech_amazon_cto_aws.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=3647" title="ETech: Amazon CTO Werner Vogels on Building Web-Scale Computing" />
    <published>2007-03-27T21:35:30Z</published>
    <updated>2007-12-16T23:11:17Z</updated>
    <title>ETech: Amazon CTO Werner Vogels on Building Web-Scale Computing</title>
    <summary>Alex Iskold is reporting live from ETech 2007 Werner Vogels, VP and CTO of Amazon.com, took the ETech stage to discuss the challenges in building a large-scale, reliable web infrastructure. Amazon spent a decade and a whopping $2 billion dollars to build the world class technology that powers their web sites. Today Amazon makes available...</summary>
    <author>
      <name>Alex Iskold</name>
      <uri>http://www.adaptiveblue.com</uri>
    </author>
    
    <category term="Amazon" />
    
    <category term="ETech 2007" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><em>Alex Iskold is reporting live from <a href="http://conferences.oreillynet.com/etech/"> ETech 2007</a></em></p>

<p><img border="0" src="http://www.readwriteweb.com/images/aws_logo.jpg" align="left" hspace="5" vspace="5" width="150" height="61"><a href="http://www.allthingsdistributed.com/">Werner Vogels</a>, VP and CTO of Amazon.com, took
the ETech stage to discuss the challenges in building a large-scale, reliable web infrastructure.
Amazon spent a decade and a whopping $2 billion dollars to build the world class technology that powers their web sites.
Today Amazon makes available their own infrastructure to the anyone, via <a href="http://aws.amazon.com/"> Amazon Web
Services</a>. We have extensively <a href="http://www.readwriteweb.com/archives/amazon_webos.php">analyzed</a>
Amazon Web Services, as well as companies that are already
<a href="http://www.readwriteweb.com/archives/amazon_web_services_success_stories.php">leveraging
it</a> in their businesses.
</p>
<h2>AWS value proposition</h2>
<p>Why build on Amazon Web Services? Vogels said because there are compelling business and technical advantages:</p>
<ul>
    <li>Total Cost: Running services via Amazon is substantially lower than building infrastructure and running it on your own;</li>
    <li>Pay as you go: Pay only for what you consume;</li>
    <li>Time to market: AWS lets businesses focus on their core competency instead of
      infrastructure;</li>
    <li>Scalability: Automatic scalability is guaranteed by adding more hardware;</li>
    <li>Robustness: Amazon guarantees 99.9999% of up time;</li>
    <li>Security: Using Amazon Services collectively makes your offering more secure;</li>
    <li>Technical complexity: Building things from scratch requires a lot of knowledge and experience.</li>
</ul>]]>
      <![CDATA[<h2>A recap of what Amazon offers today</h2>
<p>
Amazon is rapidly moving to build a new kind of infrastructure, one
that can really be considered a new WebOS. The stack of services
offered by Amazon today is quite impressive. Here is how we summarized it in
graph form <a href="http://www.readwriteweb.com/archives/amazon_webos.php">in
November</a>:
</p>
<p><img src="http://static.flickr.com/115/287609089_1d921e11dc.jpg?v=0"/></p>
<p>As we discussed in November, Amazon is likely
to roll out more services in the near future. Here are some further pointers that can be helpful if you are new to AWS:</p>    
    <ul>
        <li><a href="http://www.amazon.com/gp/browse.html?node=3435361">AWS home page</a> </li>
        <li><a href="http://aws.typepad.com">AWS blog by AWS Chief Evangelist Jeff Barr</a></li>
        <li><a href="http://www.amazon.com/gp/redirect.html/ref=sc_fe_c_1_3435361_4/103-8605431-4007801?location=http://www.businessweek.com/magazine/content/06_46/b4009001.htm%3f&token=73F338006AE15743B6FE4E9058BBB2A1B063147F">Business Week coverage of AWS</a></li>
        <li><a href="http://www.amazon.com/gp/redirect.html/ref=sc_fe_c_1_3435361_3/103-8605431-4007801?location=http://www.oreillynet.com/pub/a/network/2006/12/20/web-20-bezos.html%3f&token=DB538E1CCCA7CFFF29DD42B952A08C279BFA9E7D">Jeff Bezos Podcast at Web 2.0</a></li>
    </ul>
<h2>Werner Vogels: focus on your idea!</h2>
<p>Dr. Vogels made the case for why it makes
sense for businesses, particularly startups, to use AWS. He started by pointing out
that building Web-scale services is incredibly difficult. He showed examples of traffic graphs
from major retailers like Target and Walmart that demonstrated that even these companies are not
able to handle peak loads. He added that conventional wisdom is just wrong when it comes to understanding
what it takes to build a scalable infrastructure.
</p>
<p>For startups, Vogels advocated the 37Signals philosophy - build now, scale later. This is not because
scaling isn't important, it is because scaling is just too hard. As a young company, focusing
on infrastructure is very costly. His statistics indicated that up to 70% of resources
can go into what he calls <em>Undifferentiated heavy lifting</em> - work that does not fit
into your company's core competency. Instead, he suggests that businesses should rely on AWS to do
all this work.
</p>
<h2>Conclusion</h2>
<p>AWS is continuing to impress. Amazon is now focused on amplifying the customer success stories
and turning that buzz into more customers. Given the pricing and simplicity of AWS, it appears that
it is not going to be long before a large percentage of small and medium size companies will be
using one or more Amazon Services. Larger companies are likely to lag behind, mostly for political
and branding reasons, so it will be interesting to see if this inflexibility will hurt them in the long run.
</p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.3647-comment:30854</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.3647" type="text/html" href="http://www.readwriteweb.com/archives/etech_amazon_cto_aws.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/etech_amazon_cto_aws.php#c30854" />
    <title>Comment from Emre Sokullu on 2007-03-27</title>
    <author>
        <name>Emre Sokullu</name>
        <uri>http://emresokullu.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://emresokullu.com">
        <![CDATA[<p>Definitely! AWS is as disruptive as Skype and YouTube. In the near future, we may not need anymore to buy hardware from Sun, or lease servers from GoDaddy.</p>]]>
    </content>
    <published>2007-03-27T22:27:11Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.3647-comment:30855</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.3647" type="text/html" href="http://www.readwriteweb.com/archives/etech_amazon_cto_aws.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/etech_amazon_cto_aws.php#c30855" />
    <title>Comment from Steve Severance on 2007-03-27</title>
    <author>
        <name>Steve Severance</name>
        <uri>http://www.steveseverance.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.steveseverance.com">
        <![CDATA[<p>I think that it could be disruptive and that it may have been disruptive and in the future it will be more disruptive. But I have been trying with no luck to get access to EC2 for some time. I love the idea of leased servers and infrastructure that is completely on demand. Now if only they would let me play.</p>

<p>Steve</p>]]>
    </content>
    <published>2007-03-28T01:47:59Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.3647-comment:30856</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.3647" type="text/html" href="http://www.readwriteweb.com/archives/etech_amazon_cto_aws.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/etech_amazon_cto_aws.php#c30856" />
    <title>Comment from Raj on 2007-03-31</title>
    <author>
        <name>Raj</name>
        <uri>http://www.bigswerve.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.bigswerve.com">
        <![CDATA[<p><br />
The bandwidth charges for EC2 are not competitive in my opinion.  I can get 2TB of transfer with my current ISP AND compute power for half of the bandwidth alone with Amazon.  Funny enough -- it just doesn't scale.</p>]]>
    </content>
    <published>2007-03-31T09:51:26Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.3647-comment:30857</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.3647" type="text/html" href="http://www.readwriteweb.com/archives/etech_amazon_cto_aws.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/etech_amazon_cto_aws.php#c30857" />
    <title>Comment from Ernest on 2007-04-03</title>
    <author>
        <name>Ernest</name>
        <uri>http://s3browse.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://s3browse.com">
        <![CDATA[<p>At the moment, S3Browse.com is yet another webfrontend to S3 but our next step is to get EC2 to work on more efficient and volumeous content processing functionality. Thanks to EC2 we can focus on our business and let Amazon take care of the infrastructure.</p>]]>
    </content>
    <published>2007-04-03T12:46:43Z</published>
  </entry>

</feed>