But Rippert’s use of those particular technologies to describe the phases really bothered SOA consultant and ZapThink managing partner David Linthicum. In fact, this week, Linthicum used his weekly InfoWorld podcast to outline exactly why he’s bothered by this list.
He begins by agreeing with Rippert’s initial point that people are doing the first couple of steps for SOA — primarily, building out Web services, and then not driving it to the next level. But he heartily disagreed that it’s necessary to use Web services, ESBs or BPEL at any phase of your SOA.
He started with the Web services phase. No doubt about it – Web services can play a key role in a SOA. It’s the enabling standard for externalizing services out of existing systems, Linthicum said. But sometimes, it just doesn’t fit the bill and you need to use J2EE or even a proprietary system.
Read more at: IT Business Edge


Discussion
No comments for “One Technology Does Not Fit All SOAs”