Zusammenfassung der Ressource
Service Oriented Architecture
- What
is it?
- Architecture for
building business
applications
- Building BA as a set of loosely-coupled black box components
- Deliver well defined level of
Service by linking together
business processes
- Set of services that a
business wants to expose
to
- Customers
- Partners
- Portions of the
organisation
- Key Principles
- Loose Coupling
- Simplicity
- Autonomy
- Components offer small
range of simple services to
other components
- Overall infrastructure
much more flexible
- Service
Contract
- Services adhere to a
communications agreement,
as defined by the service
description
- Black box
component
design
- Service has
control over the
logic they
encapsulate
- Service
hide the
service they
encapsulate
- Reusability
- Designed with intention
of reuse
- Composability
- Collections
of services
can be
coordinated
and
assembled to
composite
- Statelessness
- Services minimise
retaining information
relating to an activity
- Discoverability
- Service must be designed to
be outwardly discriptive
- Making SOA happen
- SOA registry
- Used to view services
available and group
services to form
business processes
- SOA Repository
- Stores all source code and
linking information used to
build all programs
- Business Process
Orchestration Manager
- Connects whole
business process from
end-to-end
- Modelling Capabilities
- Organisation provide service
- IT systems must serve the needs
of the organisation
- Business focused approach required
- To make best
use of existing
IT assets
- Create new
services
- Facilitate the
inevitable
changes