Speaking in Tech: Apple, Oracle and Google SUCK at cloud
Plus: Does VMware's acquisition of DynamicOps change the game?
Our special guest this week at El Reg's enterprise tech-cast is George Reese, CTO and co-founder of enStratus, a cloud infrastructure management solution for deploying and managing enterprise-class applications in public, private and hybrid clouds. Your hosts Greg Knieriemen, Ed Saipetch and Sarah Vela spoke with the cloud biz man about the Amazon fiasco, cloud strategies and good "application hygiene" - and tore apart some of the moves of the biggest vendors.
Amazon outage hits Netflix, Heroku, Pinterest and Instagram
We all know the story by now: Bad weather knocked out power to Amazon’s EC2 services in Virginia and before you know it, Netflix subscribers were deprived of Bad Girls from Mars and Californians were unable to post snaps of plates of foie gras they were never going to eat on Instagram.
- But is this really about Amazon or good application "hygiene"?
- Build for failure - If this can happen to Netflix, it can happen to anyone.
- With what we have learned about this outage, what could Netflix have done differently?
- Interoperability - Is this on the infrastructure provider or on the application owner?
- Leap-second issue was a bigger deal than Amazon outage
Burning down the house: 'The Hole in VMware's Whole Cloud Strategy'
- Reese chats about his blog post on VMware's cloud strategy.
- VMware, Apple, Google, and Oracle cloud strategies all get run over by Reese.
- Does VMware's acquisition of DynamicOps change the game?
Listen with the Reg player below, or download here.
Podcast Subscriber Links
Hardly an impartial (or credible) speaker.
Oh, and please note, I'm not saying it is RIGHT, just that it is.
That's different because they're Microsoft. Excluding DOS. which they actually bought from someone else, their write and release model is:
1) Write code for something new. Release it for sale. Have the users do the Alpha testing.
2) Fix the bugs found during alpha testing. Release it for sale as a full number upgrade. Have the users do the Beta testing.
3) Fix the bugs found during Beta testing. Release it for sale as another full number upgrade. Discover users no longer want the product.
4) Kill the product. Let is mold on the shelf for a year or more.
5) Discover need for shelved product. Re-brand it. Do some actual internal Beta testing. Fix bugs found.
6) Release it for sale under the re-branded name. Roll out the hype machine. Get users to buy it and conduct additional beta testing.
7) Fix new bugs found in beta testing. Release it as a .x upgrade at a discounted price.
8) Corner the market.
So nobody is actually expecting MS to have a working Cloud product. The only thing we know for sure is that when they have a working product, it won't be a Cloud product.