Joe McKendrick, ebizQ's SOA in Action Blogger, is a nationally published author and consultant
with deep knowledge and insights regarding trends and developments in
the technology industry. He is a contributing editor to a number of
national and international publications and Websites including
Database Trends & Applications, ZDNet, and Webservices.Org. He also
serves as analyst for Evans Data Corp., and is lead analyst for Evans'
Web services and enterprise development management issues surveys.
SOA in Action Blog
|
« 2007: A Year of Convergence for SOA and Business Process Management | Main | Survey: We're Getting Faster, Better, at SOA Projects » December 18, 2006Building the Perfect SOA Beast Service oriented architecture -- at least in its current incarnation -- has now been on the scene for a few years, and we're beginning to benefit from a growing base of experience in growing and managing these beasts. David Linthicum -- who has built his share of service organizations -- boils his insights down to the important points in a new article, Ten Things to Think About When Building the Perfect SOA" published over at Sys-Con. 1. Focus holistically, act locally: SOAs are not mere "projects" -- its about the entire enterprise. 2. Define the value: This gets said a lot, but can't be said enough -- build a business case for SOA. 3. Don't neglect service design: Design services for reuse, not tied to any specific applications or platforms. 4. Embrace legacy systems. They may be the majority of services that you leverage within your SOA. (The System i rules.) 5. Learn to deal with semantics: "If you don't understand application semantics, or, simply put, the meaning of data, then you have no hope of creating a proper SOA," David says. 6. Orchestrate: Define how the services work together, including business logic, sequencing, exception handling, and process decomposition, including service and process reuse. 7. Security now -- not after the fact: Web services are not for internal user anymore. 8. Classify the patterns of use: "Determine how the SOA will be leveraged within the enterprise - not only now, but in the future." 9. Persistence is important: Since services may come out of more than a dozen different systems, so "it makes good sense to centralize the persistence for the composites and processes, as well as some supporting services to a central data tier or central data service." 10. Test, test, and test some more: Develop a test plan -- this is particularly important because of the difficulty of testing an SOA solution. "Most source and target systems are business-critical and therefore cannot be taken offline," David writes. "As a result, testing these systems can be a bit tricky." Posted by joemckendrick in SOA | Digg This | Add to del.icio.us Trackback Pings TrackBack URL for this entry:
|
