The second fear is vendor lock-in, which may or may not be completely allayed by the emergence of an industry-wide standard, given the habit most big players have of flouting them at their convenience.
Are there any answers on the horizon that might help dispel these fears? Is there an up-and-coming standard that everybody is going to follow?
Another thing to look at is network capabilities. We have all seen instances where additional network connections provide greater throughput. If you are running data-intensive applications or are providing desktop applications over the blade, you do not want to be limited to only a few network connections without a means to add more to increase throughput. Weighing all features with future considerations in mind will provide the best answer, but with all the various vendors with varying capabilities, this is best approached on a vendor-by-vendor basis. Since you are the end user, they should be happy to do this work for you.
As for vendor lock-in -- I think this is valid for a while. At the BladeSystems Alliance, we have done interoperability booths for some time; however, we don't find a push to have one vendor's blade card fit another vendor's chassis. Interoperability has been more centered around storage and supporting gear. A new standard that may help is IEEE 802.3ap (Ethernet in the backplane). This standard is still in the works, but may provide some interoperability through a less complex backplane. But I think at this point it is too soon to tell what the blade vendors will do with this technology. It will certainly speed things up if we no longer have to convert native Ethernet packets, but beyond that...? Also from an ease of use standpoint, it may be easier to stick with a single vendor. Finger pointing is a reality and no end user likes being stuck in this scenario.
Storage standards have also opened up creating better storage interoperability. IBM did a great thing when they created their open systems storage solutions. Organizations like SNIA also helped. DMTF also has some active support for their SMASH program. See my blog for more info.
This was first published in March 2006