AWS Cloud Computing Start-Up Event today in Seattle
The Mariners were practicing today at Safeco Field where Amazon Web Services held a developer and start-up afternoon. Adam Selipsky and Matt Tavis of AWS covered the business layer as well as what was under the hood. Four customers gave their perspective about how they use AWS. Trains passed by as did the occasional crack of a bat to add background music to the presos.
I came away from the afternoon thinking that cloud computing has shifted into 3rd gear. We’re not yet at freeway speeds but it is clear that a lot of the theory is being hammered into practical application. Adam and Matt’s job is to solidify the current AWS story. Given that I’ve seen Werner Vogels recite the AWS lineage on numerous occasions, I can’t say that I heard anything new. Paradoxically, that makes me feel good. It suggests that AWS is in the midst of the tedious though critical task of truly productizing the offer. It’s easy for snarky analysts to harp about cloud computing being another form of time sharing, something we’ve had since the 1960s. But while it’s one thing to understand what something is, it’s quite a different challenge to make that something work at scale. Kind of like the physicist who can model a fastball. Very good, professor. Now, hit the sucker when it’s thrown at you at 96mph. Thus, I’m not particularly fussed when I hear AWS repeat its basic story with some incremental additions thrown in. Indeed, I’d say their success measure by 2015 is to become as boring and crucial as the power companies they seek to emulate.
To me, the customers provided the more exciting content. Jeff Lawson, Twilio’s CEO, spoke about how they offer telephony as a web service using multiple cloud providers, not just AWS. Strip out the black magic, and Twilio is about making telephony app development accessible to web developers. So if your expertise isn’t SIP, 3GPP or some other exotic telecommunications protocol, no worries. You can add various telecom services to your web app using traditional web standards and tools. Cloud infrastructure, much of which is AWS, enables Twilio to split its internal world into three large domains, continents if you will. There’s a DEV zone in which Twilio’s staff developers access a simple, powerful API that has only five blocks for building voice mail systems, IVR, PBX, click-to-call and other telecom services. Then there’s a STAGE zone that lets the developer test the app. Then there’s a PROD zone which is the only cluster that touches external customers (e.g. web developers). Media providers and marketers need to take note that branded comms is a huge future growth and community building area. Nearly every marketer I know bleats about how they’re fed up with using page views as a negotiating currency for media buys. They want more engagement (whatever the hell that is) from consumers. Nothing seems more engaging than a direct conversation, either between a brand and a consumer or consumers communicating in the context of a branded environment. I can’t say that Twilio solves the engagement problem (let alone how to use telephony as an ad currency). But you don’t get more guts level customer dialog than when it’s spoken instead of written so something is bound to shake out. Cloud now makes it far more likely that a savvy web developer will catch lightning in a bottle by using telephony in a new way. Watch this space.
However, you can bet that serving up telephony or other latency-sensitive applications beg for more robust testing. John or Jane Q Public won’t be thinking, “oh well, the app’s still in BETA. They’ll get it right with the next rev.” Far more likely, ordinary people will think “this sucks!” and move on when they encounter a communications or media app that is late in delivering the goods. Enter SOASTA, which uses the cloud to be an Underwriters Laboratory equivalent for websites and web based apps. They remind me of those demo guys who bring down city office buildings with explosives except SOASTA’s job is to stress test major web sites for latency issues. A case in point is Intuit. Many remember April 15, 2007 when Turbotax melted at 1015pm, not the company’s best day. The problem, however, is that to get a proper test, you need to simulate a proper load. SOASTA uses AWS and other providers to simulate massive traffic loads (eg. 300,000 simultaneous users) in various combinations without the need to construct a separate test facility. According to SOASTA’s CEO Tom Lunibos, the dirty little secret of most Web 2.0 apps (1.0 for that matter) is that they were lit without having done more than cursory load testing. The idea was that you got it out there, had it melt, apologized to the users with some cute stick figure with a hard hat, and fixed your latency problem. Mainstream adoption and recessions are curing that stunt pronto. TomĀ declared (rightly) that latency can be measured as lost sales. Outages in 1998 that were reported in PC Magazine of Information Week now grace the front pages of the New York Times and Wall Street Journal. Bottom line for media providers (especially gaming companies) is that latency is money. So blow up your pre-launch site. You’ll be glad you did.
Don’t want to get too long so I’ll follow up with Melodeo (cloud-based music serving) and Zumobi (mobile applications as marketing) in a separate post.




Hi John,
Great post, I love the way you set the scene.
To clarify, I noted in the presentation how Twilio uses three separate AWS accounts to firewall off our internal development environment from internal staging systems from our live production systems. It’s an internal development process that I thought would be of interest to developers using the cloud, but nothing that our customers actually touch.
Cheers,
-jeff
Ah, got it…thanks for the distinction