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
|
« SOA tops FBI's Most-Wanted List -- for Technology, That Is | Main | More Patience From a High Flier to SOA » October 23, 2006Patience Can Be a Virtue, Especially with SOA Moving into SOA involves the orchestration of many combinations of services and technologies that can deliver an endless range of new applications to the business. Given all the messages bombarding the market, one can be forgiven for thinking that the time to jump full-force into SOA is yesterday. However, some experienced SOA pros advise a go-slow-and-think-carefully-about-what-you're-doing approach. One such seasoned veteran, Stuart Johnson, general manager for integration and service-oriented architecture at Commonwealth Bank of Australia, has been overseeing an SOA effort since 2002, and found that while his technical staff was ready to service-oriented the entire bank, the business side was perplexed, or even unaware of what SOA was all about. As recounted in this article in CIO Insight, Johnson said that when the whole effort began back in 2002-2003, his staff quickly got up to speed on fine-grained, atomic Web services, and they quickly started to push for building complicated composite services that would combine many services. However, Johnson resisted these urges. "I wanted to keep the technology as simple as possible. SOA is already the next buzzword, but a huge SOA architecture will make it difficult to build anything." For example, the bank's technical and business analysts wanted to push to use services to expose more data online to customers and to partners on back-end systems. In fact, the bank did not launch its first orchestrated service until 2004, and this was only after careful study and consultation with the bank's major vendor, Microsoft. The first service was designed to help customers open a direct-deposit account, which requires a series of steps that took as long as six weeks, and potentially access up to 40 different data sources. The bank employed SOA within this process to verify customer identity, make sure there was money in a checking account before a checkbook was issued, and to issue a bank card. Posted by joemckendrick in SOA | Digg This | Add to del.icio.us Trackback Pings TrackBack URL for this entry:
|
