Enterprise Architecture Enterprise Architecture Integration (EAI) Traditionally proprietary silos, vendor lock-in, e.g. CRM Web Services Can support SOA if services are coarse-grained enough Web Services are: SOA plumbing WS is to SOA what HTTP is to Amazon Middleware Can support SOA if message-based and works well in a heterogeneous environment - ESB Client/Server Architecture No dynamic discovery Object-Oriented Programming Too chatty, network communications bloat Objects have state, services are complete-and-forget Distributed Computing Traditionally not scalable & loosely coupled Unwanted intimacy required between entities SOA does use Dist Comp, but that’s not all it is IT-only Need to be driven by business needs SOA cuts across the entire enterprise IT will have a big role to play
This is a typical implementation such as is used for Web Services. As such, it is one way in which the day-to-day use of services in an SOA could work.
Here, we’re just trying to show that a service comes about when one party has a capability that another needs. So, the dichotomy of a service is provider/consumer.
Service-Oriented Architecture (SOA)
Topics Sec. TOPICS 5 5. The Road Ahead 4 4. How Does It Work? 3 3. Benefits 2 2. What is SOA? 1 1. The Setting
The main drivers for SOA-based architectures are to facilitate the manageable growth of large-scale enterprise systems, to facilitate Internet-scale provisioning and use of services and to reduce costs in organization-to-organization cooperation.
The concepts used in SOA are not new, but using them to align the business strategies together with IT initiatives is.