SOA in difficult times
Happenings in the recent weeks have turned many tables and raised many eyebrows. It has been a crash from fantasy to reality for many organizations in the need to make IT real, effective, cheaper, faster, cleaner. Organizations are in a hurry to get unproductive assets, esp Cap-ex, off the books.
This is a big change for suite vendors who have positioned their products to “capture” the solution space by selling software in an integrated package form, wherein many aspects aren't necessarily being utilized.
This is especially true in the case of SOA, where there is no hurry and sometime no need for components like registry, repository, accelerators, test suites and the like. These components unlike the ESB and messaging components, the WSDL, workflow and rules components may or may not be implemented. However, organizations who have bought suites already use infrastructure to run, monies to license, Op-ex (train and maintain) seemingly unused software.
This is a big change for suite vendors who have positioned their products to “capture” the solution space by selling software in an integrated package form, wherein many aspects aren't necessarily being utilized.
This is especially true in the case of SOA, where there is no hurry and sometime no need for components like registry, repository, accelerators, test suites and the like. These components unlike the ESB and messaging components, the WSDL, workflow and rules components may or may not be implemented. However, organizations who have bought suites already use infrastructure to run, monies to license, Op-ex (train and maintain) seemingly unused software.
