Today we live in an extremely hybrid IT world due to a number of macro-level factors including the maturity of the IT industry and the Consumerization of IT over the past decade. Much like the automotive industry where the first hybrid car was actually built in 1899, hybrid IT is not a new phenomenon, but today it creates complexities for CIOs that are leading to new architectures and new approaches for operating and managing the systems associated with hybrid IT.

In prior years, much of the hybrid IT debate centered around operating systems and application development languages. At that time, the “hybrid IT” term hadn’t yet been coined (or at least wasn’t in widespread circulation) and the challenge of the time was in dealing with heterogeneous operating systems (e.g. Windows vs. Unix) and development environments (e.g. .Net vs. Java). Back then the objective was more around an interoperability and integration play as opposed to what we now consider as a component of hybrid IT. Each disparate system played a unique role in the computing environment and integration was just a necessity for data exchange.

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