When it comes to service-oriented architecture, there's no shortage of technology questions to be answered. How do you successfully incorporate a lightweight ESB? What does the latest release of Glassfish have to do with SOA? We delved into those issues last week.
Though there is another set of concerns with SOA, having to do with business. While for some SOA revolves around performance benchmarks, its bottom line is probably best represented in dollar signs. Let's face it, if SOA can make you money, it will get funded.
Last week we asked who owns the SOA business case? Getting your business involved in a technology initiative isn't a simple task. To a degree it requires you to make the argument that what you're doing is trying to adopt technology that's involved in their business initiative. Aside from everything else, it might help you avoid what the ZapThink guys are calling vendor driven architecture. This week we'll be looking into SOA business case best practices.
It should be noted that we pursued these stories partially because we heard back from our readers that they're interested in more information having to do with business case issues. Yes, believe it or not, we listen to our readers. I mention this because this week we'll be putting out a reader survey that's going to give you, our readers, a chance to give us a clearer picture of the issues that you're facing with SOA. We put a lot of stock in what you have to say.
In fact, we consider ourselves a platform for what you have to say. So if any of you out there in the user community feel like you have something of value to share with your peers, then feel free to e-mail me at email@example.com. We thrive on feedback and, given the proper guidance, we are committed to helping you turn that SOA into a moneymaker.