How to Get Ahead in Architecture
Nurture Vendors
A Technology Platform has been identified. How can we improve the chances of that platform continuing to support the infrastructure over the lifetime of the architectural project?
* * *
The rate of technological change causes severe problems to architectural development, which by its nature takes a long view. What appear to be sound technology choices made at the beginning of a project might be undermined by a competitor releasing a technically superior product, or by unforeseen problems arising as developers push the bounds of the technology.
In an ideal world, standards such as CORBA would make (for example) the choice of an ORB product or vendor immaterial. As it is, we don’t yet have even the technical ability to chop and change at will. If we did, this would not be desirable: for strategic middleware the choice of product must clearly take into account
This isn’t to imply that investigations and evaluations of competing products should not occur. But the standard panicked technologist’s response to the promise of a faster, more stable, technically superior product needs to be tempered by a desire to work within a known and established relationship to improve the currently-used technology.
It may be that the architectural vision relies on capabilities not yet delivered by any vendor. Sometimes the only way to make sure that the required technology platform will be available is to work closely with a vendor to specify and implement that platform.
The best relationship results in a vendor responsive to the technology requirements of the architectural organisation, who will canvass the customer for requirements, who will listen to the architect’s views on technology and the market, and who will respond appropriately and effectively when shortcomings or failures in the product arise. Make it clear to the vendor that investing in this relationship is an investment in technical credibility.
Therefore:
Establish contact with strategic software vendors at all levels. Work at the relationship: like marriage, be prepared to forgive (minor) transgressions, but also be prepared to suggest, direct and influence where necessary.
* * *
Appropriate Infrastructure supports and builds on the capabilities of the technology platform, and can sometimes be used to enhance or correct functionality provided in third-party products.
© 1998 David Harvey
Created 6 September 1998
Last updated 6 September 1998