Over a million developers have joined DZone.
Platinum Partner

The Cloudcast - The Enterprise Debate in 2013

· Cloud Zone

The Cloud Zone is brought to you in partnership with Iron.io. Discover how Microservices have transformed the way developers are building and deploying applications in the era of modern cloud infrastructure.

The Cloudcast (.net) #71 - Enterprise Cloud - The Debate Rages on in 2013 (37:20)

Date: January 13, 2013

By: Aaron Delp and Brian Gracely

Description: Aaron and Brian give a brief “State of the Podcast” for 2013, and then discuss Enterprise Cloud Computing and some of the debates about how it is evolving.

State of the Podcast - 2013
  • Entering Year 3 of the Show
  • 600% Year over Year listener growth (podcast) with only 2x the # of podcasts
  • Launched The Cloudcast “whiteboard” channel on YouTube
  • Need to make sure we can remain at least semi-independent, non-biased
  • Bring back some more “news” shows, or at least “news segments”
  • Potentially going to spin-off a few new shows: Mobile, PaaS, European-centric
  • Continue to bring the show to industry events, community events

Enterprise Cloud - Lots of Debates & Discussions

 - 6 Reasons while AWS will struggle in the Enterprise

 - Focused on Innovator’s Dilemma, Disruption use-cases

 - Clouderati always give AWS a pass for downtime, “design for failure”

- Interesting analysis of AWS usage by customers

 - Following up on Forrester’s comments on “cloudy apps”

Discussion Points
  1. Are all “clouds” the same?
  2. What is the cost of new cloud-aware apps, vs. SaaS apps?
  3. How lacking is the market for “public cloud” skills?
  4. AWS currently has (approx) $1.5-2B in revenue. There was a financial-analyst report saying it will go to $4B in 2013 and could be $20-30B (market cap) if independent.

The Cloud Zone is brought to you in partnership with Iron.io. Learn how to build and test their Go programs inside Docker containers.


Published at DZone with permission of Eric Genesky .

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}