Is It Time To Consider A Service-Oriented Architectur
Any business big enough to use more than a couple programs has
experienced duplication of effort or what might be called info-envy.
It’s the realization, for example, that the sales team’s great and
detailed spreadsheet of customer data would be really helpful to the
customer service department, except that customer service’s standalone
app can’t import the spreadsheet data. Making that import possible
would take at least six months of in-house effort, which isn’t going to
happen because the IT department is too busy with maintenance and
tending to problems.
SOA is today’s solution to that
universal problem. Done well, it can revolutionize an enterprise; done
poorly, it’s a costly and demoralizing failure. A successful
implementation of SOA starts with an understanding of what it is and
isn’t.
