We at SearchSOA.com have a number of SOA user stories in the works at the moment and it strikes me that we could just about churn out a case study a day at this point in time. Last month at the IBM Impact conference, I blogged that seemingly every type of business imaginable has been embracing service orientation.
We're encountering more big SOA projects than ever before and you've got to wonder what the working rationale is these days for an app dev project that isn't loosely coupled and conformant with an enterprise architecture. What's the counter argument? Obviously it can be less expensive in the short term and less complex to throw applications together in piecemeal fashion, but over time that approach becomes costly. It's also a mess from an engineering standpoint.
Here are some of the most recent examples:
You can find links to 18 other SOA case studies in ourtop stories of 2007 compilation. The number of users who can document proven success with SOA is exploding. Does it deliver as advertised in every situation? No, nothing does and that's why we go out and try to find the users with best practices to share. This is a complex field, but the ranks of users who've found the benefits justify tackling the complexity are growing almost daily.
Here's a question for those who don't count SOA as a core competency in their app dev shop: why?
To twitter
Using Gmail
at 05/19/2008 02:22 PM
109 views
