LinkedIn Twitter
Director, OpenShift Strategy at Red Hat. Founder of Rishidot Research, a research community focused on services world. His focus is on Platform Services, Infrastructure and the role of Open Source in the services era. Krish has been writing @ CloudAve from its inception and had also been part of GigaOm Pro Analyst Group. The opinions expressed here are his own and are neither representative of his employer, Red Hat, nor CloudAve, nor its sponsors.

4 responses to “ComputeNext: Google For Compute Resources”

  1. Husein

    Your comment “they have their task cut out before they could become the Google of compute resources” may be an incorrect analogy.

    A better analogy is a Visa/MC network or a stock exchange. Given data centers need to join and deploy proprietary software from ComputeNext it resembles more of a closed market place than the www upon which a Google search model flourishes. For example, unless Spot Cloud makes its resources available, which I would presume requires deploying ComputeNext technology, it would not be searchable nor discoverable.

    I see Computenext as a Confederation, not federation. It is an elastic membership for data centers that can turn a number of Confederation members into a federation.

  2. Capacity aggregation: Cloud’s great experiment

    [...] Platform (specifically it’s new federation features), and stealth start-up ComputeNext (outlined by CloudAve blogger Krishnan Subraramian) have their way. These services aim to make the acquisition [...]

  3. Incomplete Thought: Cloud Capacity Clearinghouses & Marketplaces – A Security/Compliance/Privacy Minefield? | Rational Survivability

    [...] ComputeNext: Google For Compute Resources (cloudave.com) [...]