9 responses

  1. Shivan
    January 20, 2012

    Thanks for yet another interesting post Krishnan. I’m intrigued that you define mobile and social aspects as must haves for enterprise cloud applications. The cloud offers more access and ability to enable mobile and social components in enterprise applications. But not all traditional enterprise applications contain such components. Could you please define what you mean by ‘enterprise’?

    What about those enteprises’ objectives with respect to cloud, which may or may not require mobile / social interaction (for privacy reasons as an example)?

    From my experience, many traditional enterprises are tied to backend systems that are not cloud compatible so I’d be interested to hear your thoughts on enterprise applications that are not entirely on cloud.


    *Note – I work at RightScale.

    • Krishnan Subramanian
      January 20, 2012

      Shivan, Thanks for the response. I am trying to distinguish enterprise applications built for the cloud from the traditional enterprise applications. I do agree that they cannot have these components built in. I am only arguing that the newer cloud based enterprise apps should have these components as the core.

  2. Gilbert Pilz
    January 23, 2012

    Interesting post. I assume by the way you capitalize “Open APIs” you are trying to convey a specific meaning to that term. Could you provide your definition?

    • Krishnan Subramanian
      January 23, 2012

      Though personally, I prefer to emphasize on *Open*, for the sake of this position paper, I am keeping it to mean any API which lets other services programmatically access their functionality without any unnecessary restriction. Yes, it is a bit loaded definition but I think it is a topic for a separate discussion.

Back to top
mobile desktop