HybridITFiles

A Hybrid cloud exists when a single workload spans multiple infrastructures (public and private, public and public, private and private, etc..)

can you elaborate on the workload issue or is it just a infra issue

It's a workload issue. A single workload (application) must span multiple infrastructures to be considered hybrid.

to me, a Hybrid cloud is a Frankenstein Cloud - bandaging disparate components.

is the definition also about the deployment or architecture? like on premise or off prem

@cloud_opinion great definition: hybrid cloud = frankenstein. Hopefully in a good sense?!

@CenturyLinkEnt ha ha - was Frankenstein ever good ? :)

@mikeonsing For hybrid, the location of the infrastructure doesn't matter. It's about the architecture of the deployment.

self service, API, Agile apps,.. great point Jesse Proudman

hybrid can be in the datacenter https://twitter.com/...

@cloud_opinion > Frankenstein Cloud, for all the cloud conversation, hadn't heard that one. I like it.

We need to distinguish hybrid clouds and hybrid cloud applications. The former may be defined independent of workload. The latter is what @blueboxjesse is talking about. Both are interesting, for different reasons (infr federation & mgmt vs app mgmt).

@samcharrington Curious on the distinction you'd make? What's hybrid mean without a workload?

I can have a hybrid cloud not running hybridized applications, i.e. per ur def single workload spanning infrastructures.

@samcharrington Still don't totally understand... How is it a hybrid cloud without an application? :)

I see multiple clouds without a unified orchestration as "multi-cloud"

No one is saying there is no application, just that one can have a hybrid cloud without a single application that spans the entirety of it.

I believe @samcharrington means federated applications (spanning locations) vs having some apps on-prem, some in public and some as SaaS with no bursting or moving

@samcharrington I just disagree. :)

@stu @samcharrington Yes, that makes sense. Depending on what those infrastructures are, that could simply be "cloud" or IMO would be categorized as hybrid cloud.

Right @BrianMirise, there is a spectrum. Multi-cloud = JBOCS, Hybrid cloud = multiple clouds with common provisioning, identity, cost performance and application management.

JBOCs = Just a Bunch Of Clouds if not obvious

Said another way, I believe Hybrid is itself an architectural principle, that may be applied independently at the infrastructure tier and the application tier.

Which raises the interesting q, can you have hybrid cloud applications without a hybrid cloud in my view. Of course. Just because you run your backend on GCE and your DB on RDS does that mean you have a hybrid cloud. Your def yes, mine no.

But if you take steps to unify identity, deployment, management across the two such that the user doesn't care what cloud they're using, then you can of course incorporate GCE and AWS into a hybrid cloud.

@samcharrington Super helpful. So your definition requires both application and orchestration spanning multiple infrastructures. I think that's logical.

Ummm. I would say to have a hybrid cloud application running on a hybrid cloud then yes. Where we disagree is that I think you can have either a hybrid cloud or a hybrid cloud application without the other.

The reality is: Just about every org on the planet is using a hybrid approach to services today. #cloud

@tcrawford i was said earlier that born in the cloud vs connecting to the cloud is a great demark line for what is hybrid

@furrier That's an interesting perspective. Not sure how I think about it. Must think more.

seeing much more RFPs and POCs and CF is involved in all of them

#CloudFoundry become the defacto PaaS standard a year ago like #OpenStack became the defacto Private Cloud. Over the coming years, we'll see significant adoption.

As a further proof point, Pivotal just announced bookings of $40M last year. #CloudFoundry isn't going away.

Rob Smoot says two types of applications "born in cloud" and "connecting to the cloud from somewhere" - app workload depends both use cases valid. Excellent comment

Cloudfoundry was smart to take a "rising tide floats all boats" by circling the wagons on the partnerships. That was key success tactic

that $40m was not cloudfoundry lots of other legacy rev (eg greenplum)

Still impressive from a standing start. ;)

John, stop mis reporting facts. The 40 was 100% Cloud Foundry software as articulated in our PR

http://www.prnewswir...

the EMC annoucement gave the PCF + Big Data suite number which was $80M.

@wattersjames Thanks for sharing that

I stand corrected "falling on my sword"

@blueboxjesse How did #cloudfoundry affect the development in your organization?

James we'll be at IBM event next month so have to ask how's the partnership plans coming

@arianagradow They've rewritten 350 legacy LOB apps to 125 modernized apps on CF. This included things written in COBOL. They've been able to deliver business value MUCH faster than their previous efforts.

this is why Pivotal crossed over to success - open PaaS movement was a good call http://blog.pivotal....

The PaaS market is heating up with over 70 platforms and #cloudfoundry as the cornerstone. It's the new normal for modern application development.

@BGallagher32 great to see EMC executive in this chat!!! Brian Gallagher is someone that we follow thx

@BGallagher32 Brian how does a customer from EMC deploy hybrid when they want converged infrastructure as their path?

still education needed in market in typical IT department

> I'm still surprised you're not wearing your Hawk's Jersey.

In your opinion, what's next after PaaS?

@JeffFrick doh! I got my 12th man flag in the background though.

#PaaS and #container worlds are coming together with Diego/Garden in #CloudFoundry & GearD in #OpenShift