SOA: A Frankenstein in the Enterprise?
Categories: Software, ArchitectureI recently came over an article that interestingly enough clearly described some issues regarding service oriented architecture. Especially the fact that SOA is the direct opposite to “Set it and Leave it” products. SOA requires maintenance and an overall picture to avoid redundancy in services. If an organization looses control over it’s services, information or functionality might become available to the wrong people.
A Quote from the article:
“… SOA presents new challenges to enterprises – challenges that some companies may be ill-equipped to handle. As a technology that allows far greater flexibility, even creativity, it requires far more governance.”
“SOA is the exact opposite of a “set it and leave it” technology. Like a garden that constantly grows and changes, a SOA-enabled architecture needs carefully tending to prevent it from growing into a riot of unplanned consequences.“
Read it all here: http://itmanagement.earthweb.com/netsys/article.php/3639996
(article written by James Maguire for earthweb.com)
Instead of putting them up against each other, why don’t we think of them combined? In fact, combining the two words I like the best within software, Agile and Architecture, (oh, the phrase “it works!” is still my favourite though), an Agile Architect seems like a pretty good role to have on board! But what are the characteristics of an Agile Architect?