Pure Play Maintenance Costs Consuming IT Budgets?

ContractualObligatio asks: "The Register asks the question of whether businesses are at risk of having no budget to develop code, from maintaining too many 'pure play' applications. What has the experience been among Slashdot readers? Are people spending too much time maintaining code and integrations because the business is adopting too many applications? Do IT teams have the time and money to actually improve and innovate the way their companies do business?"

Comments

I'm going to guess here...

[khasim]

I'm guessing that this means an application that does only one thing. Seemingly with a limited API or hooks to link it with other apps. From TFA:

But in practice, the level to which any pure play application integrates with an infrastructure management suite can be a significant variable, and there is always the possibility that adding something like lifecycle management means adding yet more pure play applications to the maintenance list.

So, kind of a limited version of the old *nix ethic. Do one thing, but do it well.

So their point seems to be that you want to evaluate the ability to hook your apps together when you consider which ones to purchase.

Oh, and remember that SOA is a cool buzzword.