Sunday, February 05, 2006

Me-Too On SaaS and Mashups...

There have been a flurry of postings recently on Software-as-a-Service (SaaS) and Mashups.
Sandy Kemsley posted on this recently and folks like Robert McIlree were quick to pick up on her thoughts.

My two-cents on SaaS is that it poses an interesting angle for accessing external data and hosting opportunities (for me especially with disaster planning). The analysts seem to be pushing hard on this... For the mid-sector this may provide a try-before-you-buy opportunity. For the larger sector, not so sure. There needs to be a key differentiator with uniqueness/specialization of the service, performance, ease of engagement, or quality of the results. I will chime in with the others with my cautions on security, business continuity of your data and scalability. On the hosting matter, servers get bigger and bigger...and come in smaller and smaller boxes. What happened to doing real capacity planning and did not have to worry about what server and what hardware provider will demand manage and provision it new? Am I alone with this one?

FYI, the term SAAS has a both interesting and respectful meaning for Muslims .

Now on to Mashups...uh boy. Where's James McGovern and his B-Boy references... I think mashups are on a fast hype curve.

Bottom-line composing two or more heterogeneous services into a single solution is the job of every portal, enterprise integration project, and sometimes orchestration solution out there...Hello? Again...different play for the smaller sectors...but we really need to educate our customers on where wisest to spend their money. What is it that these providers have figured out that we haven't to deliver on the benefits of EA and SOA? Looking to be educated by someone with a mature thought who knows of a quality and worthwhile option. Please comment and help me out here.


Blogger James McGovern said...

Hmmm. So when should a portal integrate composite services vs. creating a composite service on the "bus" and having a portal talk to it...

6:48:00 AM  
Blogger JT said...

This comment has been removed by a blog administrator.

7:04:00 PM  
Blogger JT said...

Interesting question...part of me thinks that its the same solution...but multiple answers are possible. Portals can integrate fine or coarse grained services via WSRP. Simply put...deliver the markup with the payload. Portals can also integrate multiple services via cross-portlet aka inter-portlet communication. This is the best portal fit...and will come even more powerful when marrying SAML 2.0 with JSR-168. As for the 'the bus' , by that I assume you mean an ESB platform. If so, services are designed for reuse so exposing them via the bus is possible assuming ots scaled accordingly. All-in-all both are possible. The ESB platform may have an easier time integrating more granular technical and utility based services. As I stated above there is more than one way...and if you need quick (read tactical) implementations consider composition at the integration layer with RPC and other Java based services when using Sharepoint or DotNetNuke and the opposite for creating services proxies to .NET services and SAAS when using Java-based portals i.e. Websphere, Weblogic or Liferay ;-)

7:56:00 PM  

Post a Comment

Links to this post:

Create a Link

<< Home