Five great unsolved mysteries of SOA
There’s a lot of mystery still surrounding service-oriented architecture. Many people — even in IT — say they don’t fully understand what it can do, or how to go about building one. For a subject that is being hyped to incredible levels by vendors and analysts, there is precious little information about the fundamental implications of this new approach.
Nine places where SOA is making a difference, right now
What kind of a year was 2007 for SOA? Yes, there was plenty of disgust and eye-rolling at all the hype around this still-emerging concept. But at the same time, we started seeing more and more examples of companies putting the methodologies and associated tools and platforms to innovative uses. Can ROI be far behind? Some companies report seeing it already, proof that SOA isn’t necessarily some pie-in-the-sky dream foisted on us by vendor marketing departments.
What the statistics are telling us about SOA
There were plenty of surveys and studies around SOA adoption and issues this past year. Overall, the surveys point to widespread interest in SOA, and results among those companies with SOA already in progress. Joe McKendrick presents a few highlights from this year’s studies of SOA adoption.
Miller Time for SOA
Miller Brewing Co. has plans to begin an SOA implementation in 2008 that will move mainframe COBOL applications, including those that help manage beer distribution, into the Web services world. Like a brewmeister contemplating a new beer, Tim Heeley, senior systems analyst at Miller Brewing, is proceeding with care. “We’re not totally into an SOA environment,” he said. “We’ve just scratched the surface.”
Integrate legacy systems into your SOA initiative
You want to include Service-Oriented Architecture (SOA) in your organization to make processes flexible, adaptable, and supple. But you already have a set of systems in use for your business processes. The solution? Integrate SOA with your legacy applications to get more value out of them. This article takes you through the steps you need to make it happen—and the pitfalls to avoid.
Linthicum’s SOA Predictions for 2008
- IBM will purchase one big SOA company and one small SOA company.
- More SOA projects will highlight a lack of qualified SOA talent.
- SOA and “traditional” enterprise architecture will continue to merge.
- Resources on the new Web will drive many enterprises towards SOA.
- The press will highlight huge SOA failures.
- Large consulting organizations will continue not to get SOA.
The Seven Levels of Loose Coupling
According to ZapThink, there are really seven levels, or perhaps aspects, of loose coupling that architects should consider in their SOA initiatives. The more degrees and levels of loose coupling they add to their SOA efforts, the greater those systems can deal with change.
Mashups: Moving SOA Out of The Back Office
Enterprise mashups complement SOA efforts very well and actually help the business realize the benefit quickly. If SOA is on your enterprise to-do list, make sure you get enterprise mashups on that plan as well. It could move your SOA from the cool, soothing datacenter into the hands of your business users.
What Do SOA and the Credit Crisis Have in Common?
“Those who consider SOA have a critical strategic need that takes careful planning , and they will do well with the notion if they do their homework before the purchase. Those who jump into SOA feet first, following the hype with little consideration of the effects, wont’ do well. Just because you’re approved for the loan does not mean you can afford the house. Just because you can buy a SOA technology product does not mean it’s right for your specific needs.”
Align IT with a health information exchange for SOA solutions
Healthcare organizations are actively looking to SOA for an IT solution to help transform the industry. But making sure the solutions delivered for these initiatives meet the needs of business users is challenging. Analyzing business vision and requirements and linking them to technology is the most essential step for SOA implementation. Using a health information exchange network as an example, this article illustrates a methodology and best practice of managing such requirements, using software tooling to ensure that the technology investment aligns with the business objectives during SOA adoption.
