[Jason] Bloomberg: The integration story is a rather tricky. On the one hand, integration problems lead to SOA discussions because you have this rat’s nest of complexity in these large organizations where integration now becomes the key challenge. Maintaining a complex integration environment can be enormously expensive and inflexible.
That being said, taking an architectural approach is basically starting at the other end of the problem, saying, “How can we organize IT resources so that we don’t have to think about integration in a traditional way.” Instead, we can focus on building services and supporting flexible composition of services and essentially we get the benefits of integration as a result of service composition.
As SOA matures, the use cases are becoming clearer, according to ZapThink managing partner Jason Bloomberg. This week, he explains what situations SOA bests addresses and the benefits of SOA for organizations of varying sizes. Last week, Bloomberg explained that SOA would be coupled with other initiatives, such as BPM and MDM.
Discussion
No comments for “As SOA Matures, Guidelines Clear Up About When and Where to Use It”