“If the “best of breed” solutions are all very “different” there may be a great deal of training and overhead that may not be there if they are all from a smaller set of vendors with a similar “technology”.”
In addition to all the other pros and cons of each, the multi-vendor approach does indeed come with an additional up-skilling overhead.
As you all know, OSS activities tend to aggregate in the form of end-to-end workflows that traverse different OSS systems or modules. In a single-vendor approach, workflows are normally designed to flow from one module to the next, giving a relatively seamless user experience (UX). In a multi-vendor approach, the UX don’t necessarily match. This leads to a slightly more challenging training and process design.
But more importantly, the challenge lies with the OSS administrators. Different OSS tend to have different underlying technologies (eg database, operating system, high availability mechanisms, etc). Each of these have to be learnt and maintained in addition to the OSS tools themselves.Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email