For Enterprise Architecture Professionals

Defining Your SOA Platform Strategy

Sorting Through The Confusion Of Overlapping SOA Functions And Features

    Why Read This Report

    Defining an SOA platform is not as simple as some in the industry make it out to be. Serious pursuit of service-oriented architecture (SOA) requires new and different characteristics in your application infrastructure. New product categories such as SOA repositories and enterprise service buses (ESBs) provide part of what's needed, but vendors are also making SOA enhancements to existing product categories such as application servers and IT management software. An effective SOA platform must be a cohesive integration of both new and existing products. Why? To deal with the many feature and function overlaps between specialty products, to manage feature and function overlap between specialty products and existing software infrastructure, and to achieve the smooth handoffs among SOA platform elements necessary to attain high quality of service (QoS) for your services. Sorting through the confusion requires that architects define their SOA platforms function-first — starting with the specific design and architecture characteristics of SOA — and not product-first (like some in the industry do). Forrester presents a model for defining a comprehensive SOA platform.
    US $ 499
    Become A Client

    Get objective, pragmatic guidance that helps you make tough decisions and succeed in a complex world. Contact us to learn more.

    Already A Client?
    Log in to read this document.

    TABLE OF CONTENTS

    • The Breadth And Depth Of An SOA Platform
    • The Major Functional Areas, Boundaries, And Features Of An SOA Platform
    • Sorting Through The Confusion Of Overlapping Product Categories
    • RECOMMENDATIONS

      Define Your Strategic SOA Platform Function-First, Not Product-First
    • Supplemental Material
    • Related Research Documents