Documents/PGFSOA/3: Infrastructure

4.3: Infrastructure

Implement the Service Oriented Infrastructure

Other Information:

The keys to implementing the Service Oriented Infrastructure focus on some of the most complex and demanding architectural concerns. Without the infrastructure that enables service-oriented architectures, the rest of these concerns are moot. It is critical to the growth of your SOA to understand the key infrastructure needs early in order to support the growth in services. Recommendations for Service Oriented Infrastructure: • Adopt a Federated approach to security and privacy for defined Communities of Interest (COI) that identifies common security and privacy solutions based on a risk/reward approach. • Determine the most effective approach to achieve semantic interoperability, either through processes like NIEM or through semantic technologies. • Incorporate run time and build time service management functionality to define, monitor, enforce, and adjust Service Level Agreements (SLA). • Utilize a Registry/Repository to discover needed services during application build and to insure that key criteria such as reliability, efficiency, dependency, and adherence to and/or violations of policies are fulfilled. • Adopt a trust model that addresses both security and privacy and also quality of service. • Establish a collaborative test/evaluation and certification/accreditation process for services. • Evaluate emerging technology against relevant test cases. Using better technology can lead to working smarter rather than just working harder. For example, Internet Business Logic is a kind of Wiki for applications written as business rules in open vocabulary, executable English. As befits a Wiki, shared use is free. It also works as an advanced SOA endpoint on the Web. See www.reengineeringllc.com.

Objective(s):