Don’t waste your time with a hybrid cloud

I’m often asked about paired private and public clouds, aka hybrid clouds. What are they? How do you use them? Should you use them?

I’m not talking about hybrid clouds that are defined as traditional systems paired with public clouds or as multicloud architectures composed of more than one public cloud, but hybrid clouds as defined by NIST in 2011. The definition is important because I’m finding that people use the “hybrid cloud” term very sloppily still.

The problem with hybrid clouds is that they are typically defined to be paired private and public clouds, which is the correct definition. The problem with this architecture is that they have the concept of “private cloud” in the architecture, and that dog does not seem to hunt anymore. 

To read this article in full or to leave a comment, please click here

I’m often asked about paired private and public clouds, aka hybrid clouds. What are they? How do you use them? Should you use them?

I’m not talking about hybrid clouds that are defined as traditional systems paired with public clouds or as multicloud architectures composed of more than one public cloud, but hybrid clouds as defined by NIST in 2011. The definition is important because I’m finding that people use the “hybrid cloud” term very sloppily still.

The problem with hybrid clouds is that they are typically defined to be paired private and public clouds, which is the correct definition. The problem with this architecture is that they have the concept of “private cloud” in the architecture, and that dog does not seem to hunt anymore. 

To read this article in full or to leave a comment, please click here