Free Newsletters

   All InfoWorld Newsletters
Real World SOA | David Linthicum » SOA as a SaaS...What to Plan For

March 02, 2007 | Comments: (0)

SOA as a SaaS...What to Plan For

I've been working with a number of clients that use outside-in services, or services that are hosted remotely, but leveraged within one or many internal systems. Typically this is around some ad-hoc business driver, such as using a remote services for B2B or access to vertical applications, such as those leveraged by finance, healthcare, and retail.

So, I've been thinking a bit about how you become a services provider, or SOA as a SaaS...an organization that stands up Web services for consumption by others. As the trend to share services continues, you'll find that many of you are put into this position, as SOAs learn to reach across the Internet and touch each other.

Those that design and post services will have to understand a few basic principles, they are:

1. Focus on granular services that are part of a holistic solution.
2. Consider many service externalizations scenarios.
3. Track usage.
4. Quality in the design.

Focus on granular services that are part of a holistic solution means that you consider the problem you're solving, versus just the service you're implementing. Moreover, you're willing to provide many services that together will solve a business problem, but at their instance solve a tactical problem.

Consider many service externalizations scenarios means that you're building a service that may be externalized to humans or other computer systems through a variety of interfaces. In essence you're interface agnostic, understanding that the value of the service will need to be realized within a variety of systems, all having different looks and feels.

Track usage. Not to be too big brother, but it's nice to know who's using the service and where.

Quality in the design. If you're going to provide services for others you need to understand the quality of that service needs to be impeccable. In essence you're becoming part of an application that's unknown to you, thus you need to design that into the service as well as test the service, more so than any application. Not doing so means you'll be disruptive to those using your service, and your service won't add value, thus won't be used.

137506981_35f7507229_o.png

Posted by Dave Linthicum on March 2, 2007 05:34 AM


RATE THIS ARTICLE:





 

  •  
  • COMMENTS




David,
Many of our customers are leveraging our solution for just what you highligh in your post. We should re-engage on our discussions as we have made changes since we last spoke. We should speak regarding how Kapow is important to SOA, SaaS, etc.
John

Posted by: John Spears at March 6, 2007 12:47 PM

Where is all of this going? SOA and SaaS are mutually very compatible and may overlap, but they are not mutually inclusive.

SaaS is really more of a business model for reaching end customers - delivering a business over the Internet, generally through a browser instead of requiring the end user to install a client or other software on their side. The method of creating a SaaS can be done as a SOA, but in most cases, it is developed as a vertically integrated platform that the SaaS provider can control, even if some parts of the SaaS are exposed as Services.

On the other hand, delivering a reusable Service in SOA fashion, even for profit, is not necessarily a SaaS. That Service might need interpretation and certification as a "good citizen" before being offered to the end customer. The real question, and maybe this is just a point of distinction for the pundits and analysts, is: Does a SaaS need to be a complete business offering - or core to the business model, or is any Service offered for profit technically a SaaS?

For my part, I'd say the terms belong to different software disciplines, one architectural, the other marketing related:

1. SOA is a business strategy for aligning IT assets as Services in a loosely-coupled way to support business processes with more flexibility and agility.
2. SaaS is a business model for offering or selling software (or a business service, with a small "s" and not a technology Service) to end customers without the installation or client requirements. Most SaaS offerings are actually vertically integrated web implementations of software under a single brand's authority domain, which isn't always in the SOA spirit.

Of course, the discussion does have value, especially if we look back at it in a year or so. We expect someday to offer certified Services that obey expected behaviors in a "for profit" way, yet to do SOA these services need to be cooperative at the same time. But enough for now, we could make distinctions with SOA, SaaS, Web 2.0, etc. all day long, without even getting into the underlying technologies or the overarching Governance strategy.

Posted by: Jason English at March 20, 2007 08:20 PM

Technology White Papers

 

InfoWorld Technology Marketplace

» Technology White Papers Library

Technology White Papers by Topic

Technology White Papers E-mail Alert

Find out when the latest white paper is available:
 
 
» BUY A LINK NOW

Sponsored Technology Links