Usage of a SOA "soft appliance" for Federated SOA

In my last several posts I have been sharing the concepts of a new product category I have been referring to as a SOA "soft appliance".  Those posts have covered the origin of the idea, features, benefits and how is it similar to and different from other types of service-enabling infrastructure.

Going forward for a while, I plan on posting on the deployment architectures and usages of a SOA "soft appliance" platform like Intel SOA Expressway.

One primary architecture and deployment scenario we often run into is a situation where there is not a single unifying SOA architecture or infrastructure across an enterprise.  Instead different business units, functional groups and/or geographies (which I will call "SOA domains") have a local SOA implementation including registry, service inventory, ESB, portals, and security infrastructure.  More often than not this is due to the fact those different "SOA domains" have made a substantial investment in a major software vendor to power the application functionality for that aspect of the business (like Oracle, IBM, SAP, Microsoft, etc.).  These major vendors deliver an integrated SOA stack and in many cases they have been adopted by that domain.  This results in islands of "SOA domains", that need a vendor independent, secure, and high performance integration platform to exchange and aggregate key enterprise services like employees, financials, orders, vendors and customers.  This situation is sometimes refered to as a Federated SOA and in the Gartner conference in June this was described as the predominate model for SOA deployment.

A SOA "soft appliance" like Intel SOA Expressway is uniquely suited to connect these "SOA domains" across an enterprise.  We have a video available on YouTube which describes this usage model and the value proposition of the SOA "soft appliance" in meeting the needs of this Federated SOA use case.

I will be sharing more uses cases in many upcoming posts, uncovered through our engagements in the market.  We have captured many of the uses cases and practical implementation experiences of a Service Oriented Architecture in a book from Intel Press, titled "Service Oriented Architecture Demystified".  It is worth reading if you are interested in going a level deeper than can be expressed in a few blog posts.

Thanks for getting this far.  I look forward to hearing from you about your SOA deployment and how your federated or unified SOA architecture is progressing.


For more complete information about compiler optimizations, see our Optimization Notice.