Real-World Examples of Easier Integration with SOA

Loraine Lawson

Last month, I shared big and small use cases for service-oriented architecture and referenced an article by Mike Kavis about start-ups and SOA. The article was theoretical, meaning Kavis didn't offer specific examples, but rather made a strong case for how start-ups might benefit from starting with a service-oriented architecture.

 

This month, Kavis followed up his piece with an article sharing how a real start-up called Service-now.com used SOA to obtain a competitive edge. Kavis focused on demonstrating that SOA is not just for integrating legacy systems -- but along the way, he manages to show that SOA really does have a positive, long-term impact on integration needs.

 

Service-now.com is an on-demand IT service management solution provider. Apparently, the CEO -- Fred Luddy - contacted Kavis after reading the first column and offered his company up as an example of what SOA can do for start-ups.

 

But I think the story also has implications for all companies considering SOA, particularly when it comes to demonstrating how SOA can change integration. Luddy reports that the biggest challenge they now face is when they have to integrate with partners who do not have a flexible architecture. In these cases, they have to write customized adapters. In some cases, they've had to build a SOA layer on top of legacy systems before they could complete the integration.

 

When the partner is already SOA-based, they found their integration time was greatly reduced. In one example, they integrated with SalesForce.com in only one week.


 

Kavis also shared this:

"Also with SOA, Service-now.com claims there are fewer moving parts to complicate integrations. A pure SOA implementation should be largely platform and technology neutral, meaning that .NET to Perl or Perl to Java for example is very easy to achieve. When properly designed, SOA makes versioning of software on both sides of the integration less challenging."

It's a good read, though I really could've done without Luddy's ageist opinion about how the service-oriented approach requires a "young mindset." Please.

 

Bill Chapman of Avnet shared a similar, SOA-related integration success story at InfoWorld's 10th SOA Executive Forum, according to this post by Eric Knorr. Avnet used SOA as a way to integrate companies it acquired and outside partner companies. Chapman estimated that SOA reduced development times by 45 percent and increased order-to-quote efficiency by 30 percent.



Add Comment      Leave a comment on this blog post
Sep 23, 2008 7:09 AM Rhett Glauser Rhett Glauser  says:
I was able to sit in on the conversation between Fred and Mike. Here is some background information to explain Fred's ageism.Fred is a veteran of the tech industry. Before Service-now.com he was the CTO of Peregrine and Remedy for 13 years. He knows about old software.His point was that it is very difficult to rearchitect code that has a legacy to overcome. Service-now.com has had its success because Fred built it from the start on the Internet. I am not aware of a legacy client / server application that has been able to successfully rearchitect to a true SaaS offering (not warmed-over ASP or legacy code with a Web front end).So the 'young mindset' references two things: 1. SOA is easier if you don't have to deal with old code. 2. When we hire developers (they are all ages) we look for someone who thinks about solving business problems with software in ways that have never been done before.Are Fred and Service-now.com employees a bunch of ageists? Guilty as charged. Reply
Sep 24, 2008 6:00 AM Fred Luddy Fred Luddy  says:
Maybe I should have said a contemporary mindset. Being 53 myself, I have had to discard a lot of my prior "industry knowledge" as baggage and adopt newer, fresher approaches. A "young mindset" can belong to anyone, regardless of age. Reply
Sep 25, 2008 10:31 AM Loraine Lawson Loraine Lawson  says:
How about someone with a flexible and open mind? You really can have that at any age and it doesn't come with the implication that being younger is better than being older. Reply

Post a comment

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

null
null

 

Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.