For Enterprise Architecture Professionals

Primary Analyst Photo	Document Information	Rate this Document
	October 9, 2008 Building Interoperability And Federation Into Your SOA Platform Strategy by Mike Gilpin with Randy Heffner, Larry Fulton, Wallis Yu, Justinas Sileikis, David D'Silva	Average: 9  (4 ratings)

This is an excerpt

Executive Summary

As large and heterogeneous enterprises reach greater service-oriented architecture (SOA) maturity, enterprise architects often find that different business areas or domains need different things from an enterprise-level SOA platform. Accommodating these requirements may call for architects to segment their SOA platform strategy and build in an extra level of interoperability and federation between different SOA domains. SOA platform federation may be driven by heterogeneity of SOA infrastructure and products across domains, but it can also occur in a homogeneous platform that is configured differently for each domain. Architects should separate true business requirements from accidents of history that may reflect weak architectural governance, decide which patterns of interoperability and federation are truly necessary, and then expand the SOA platform strategy to accommodate these requirements. And in the future, architects at firms large and small will find that these same patterns will help their business participate in peer-to-peer B2B communities enabled by software-as-a-service (SaaS) and cloud computing.

TABLE OF CONTENTS

• SOA Infrastructure Varies Widely Across Most Large Enterprises
• Interoperability And Federation Are Key To Future Enterprise SOA Success
• Interoperability And Federation Should Shape Your SOA Platform Strategy

RECOMMENDATIONS

• Build Interoperability And Federation Into Your SOA Platform Strategy

WHAT IT MEANS

• Federated SOA Will Support Future SaaS And Cloud Computing Shifts
• Related Research Documents

This is an excerpt