Have you ever tried rafting? And did you ever feel the adrenaline rush of a wild ride through white water? Processes are like rivers. Floating. That’s common, of course. But let’s dig a bit deeper. And see how and why white water happens.
For a loose definition I would note that white water is not just a matter of speed but the result of different floating velocities. When passing a chute, water speeds up but just for a short time, because it cannot escape, is always part of the river and surrounded by water at a lower speed. This is the reason why maelstroms suddenly occur, marking the interfacing line between two velocities. These maelstroms are not only dangerous, but malicious – forcing you to seriously “read” the water.
Against this background and thinking about virtualization issues, the analogy that processes are like rivers is not that commonplace anymore. This explains perfectly why the creation of virtualization islands – in our new terms: the creation of “virtualization chutes” – doesn’t lead us anywhere from a process point of view and just produces maelstroms which are difficult to handle and threaten operational efficiency.
They work as short chutes but don’t speed up the river as a whole. And so they don’t speed up the end-to-end process from back-office to the customer’s interface. But having customers in mind and SLAs can you seriously talk about processes without thinking end-to-end? Certainly not. And that’s why we need virtualization automation more than ever. To assure that your automation strategy covers all applications and processes in real AND virtual world – and to increase productivity alongside the river.
Check out this Whitepaper about VMware integration for more technical details.