There is one final thought here, that probably does cause a lot of confusion in the LEGO® box… that, often, the “ABB implementations” are not actually just one thing.
Vendors will be really happy to say – “my product X is a really good implementation of ABB Y… and Z too!” Which means their product X is actually a package of stuff, probably reasonably cohesive and self contained, but sufficiently “bloated” for them to say “it does everything!”. So the same thing’s in loads of compartments… sorry, ABB Categories.
Is this a good thing? It depends! Do you want “best of breed” implementations for each of your well defined ABBs, relying on adherence to standard interfaces and so on to ensure thy work together? Or can you manage risk more effectively by taking a coherent collection, a package of ABB implementations that one vendor’s ensured work together in an sensible way?
It’s the old 1970’s conundrum of “Hi-Fi separates” or “Music Centres”! I guess it depends on how confident you are that you can make the parts work…
...who makes the parts work? You, the Architect caring for the ABB Framework, or you the Solution Designer using it's contents as you design an IT system to solve a business problem?
No comments:
Post a Comment