SOA Still Isn't Just For Integrating Legacy Systems
Service-oriented architecture is not just for legacy systems but can be strategic for Startups as well. Service-now.com, a SaaS provider of IT Service Management solutions, has used SOA as a competitive advantage.
CIO — A few weeks ago I wrote how SOA is not just for integrating legacy systems but could also be a strategic approach for launching a brand new startup. I argued that startups can build their products and services from scratch in a true service oriented fashion without the burden of culture change issues, business process reengineering efforts, and changing the way the firm develops. Starting from scratch creates a tremendous opportunity to build it right from the start.
Fred Luddy, CEO of Service-now.com agrees with me. This is exactly the approach his company took to gain competitive advantages on its competition. Service-now.com is an on-demand IT Service Management solution provider. Their SaaS solution combines ITIL v3 with Web 2.0 technology and SOA to provide a rich user experience to address a firm's problem management needs.
Luddy, former CTO of Remedy and Peregrine founded his company knowing there had to be a better way of delivering software solutions then the way traditional shrink wrapped solutions of his past were being delivered. Previous systems were too inflexible, took too long to change, and were not customizable enough for the users. After spending several years with companies who are now his competition, Luddy came to the realization that it was time for "significant simplification." In 2004, he formed Service-now.com with the intent of leveraging the Internet as the platform to build his product on. His vision of the underlying architecture was that software must be "simple, approachable, configurable, and easy to integrate" and had to be as "restless and stateless as possible." Luddy also wanted to eliminate the data formatting issues and figuring out how to communicate with various other applications. In his own words he states that "there were no alternatives, no decisions to be made. There was no other way then with a SOA mindset."


