A shift is
taking place in the server market that is starting to look very much like a
throw back to simpler times. As enterprises gain comfort with x86 server
virtualization, they are starting to push for higher and higher consolidation
ratios, which are driving a return to scale up server purchases. Where a
single-socket server with 8GBs of RAM was the most popular choice a few years
back when scaling out was all the rage, we are starting to see beefier
configurations become the norm to accommodate server
A Forrester survey from just last year showed that while adoption of x86 virtualization was ramping
quickly among enterprise infrastructure & operations (I&O) leaders, the
ratios of servers consolidated were low, averaging 4:1. But this may have been
as much a byproduct of the new technology comfort curve as it was server buying
Wouldn’t it be nice if the enterprise software world were on board with your server virtualization efforts? Imagine downloading the latest version of PeopleSoft or Crystal Reports in a virtual server format that could be loaded on to VMware ESX and would just run – no installation, no configuration hassles, just instantiate and go.
In today's LinuxWorld session by Simon Crosby, CTO of XenSource, and shepherd of the Xen open source project made the contention that the open source community is holding itself back by not ensuring compatibility between Xen, KVM and the other open source virtualization efforts. He's right to a degree in that standards for foundation functions would allow the greater community to enhance virtualization for all, but should we honestly hold out hope of this happening? As is always the case in the open source world, the crowd goes where the excitement is and popularity wins. It would be a waste of the community's efforts to try and drive standardization where it isn't wanted and to try and ensure compatibility between competing implementations when everyone expects a winner to emerge.
Enterprise customers want things they can count on, especially if they are pitched for use in production. The fickleness of the open source community runs counter to this desire which keeps open source technologies in the fringe until a commercial entity hardens them and wraps them in professional support offerings. This commercialization collects the interest of the community that wants to make a profit and, voila, the winner emerges. It's not the community that holds back open source projects its failure to bridge the desires of the commercial customers and ISVs and the community enthusiasts - the key to this is collective advancement of the chosen project.