Anda di halaman 1dari 1

Service Oriented Architecture (SOA)

Monday, May 11, 2009
10:55 PM

SOA-High Level Definition: A paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownerships.

Technically
• A client/server software design approach in which an application consists of software services and software service consumers (also known as clients or service requesters).
• SOA differs from the more general client/server model in its definitive emphasis on loose coupling between software components, and in its use of separately standing interfaces.

Why SOA? Predecessor to SOA


• Drivers: • Modular Designs
• Large scale systems • Object-Orientated Approaches
• Provisioning of services • Component Based Software like COM, DCOM
• Reduce the cost • Problems Successfully Addressed: • SOA should be task oriented
• Benefits • Complexity Management • Not just a marketing hype…
• Build scalable, evolvable systems • Re-use (to some extent) • SOA is a way of thinking
○ Scalable because minimizes assumptions • Problems Still Present: • SOA is not Web Services
• Manage complex systems • Deployment • Loosely coupled architecture that uses messaging
• Encourage re-use • Maintenance Problems Successfully • Enriched by creating composite apps
• Integration of complex systems Resolved by SOA • Move from batch to real-time

• SOA is about constructing software components that


Key Concepts in SOA Components to Services can be reused in context unknown at design time
• Loose Coupling • Composition versus Extension (OO)
• Implementation Neutrality „ Requires a client library „ Loose coupling via
„ Message exchanges
• Flexible Configurability
„ Policies
• Granularity
Long Lifetime „ Client / Server „ Peer-to-peer
„ Extendable „ Composable
„ Stateless „ Context independent
Key Components of SOA
→ Services
→ Messages „ Fast „ Some overhead
→ Service Discovery „ Small to medium „ Medium to coarse
granularity granularity
Attributes of Service
What is A service in SOA: Is an • Well defined, easy-to-use, somewhat standardized interface Protocols
exposed piece of functionality with • Self-contained with no visible dependencies to other services WSDL‐‐>Web Service Description Language: For describing Services
three properties: • (almost) Always available but idle until requests come UDDI‐‐>Universal Description, Discovery & Integration: Serves as Registry
• The interface contract to the service is • “Provision-able” SOAP‐‐>Simple Object Access Protocol: For message based access to WS
platform-independent. • Easily accessible and usable readily, no “integration” required HTTP‐‐>Hyper Text Transmission Protocol: As transport mechanism
• The service can be dynamically located • Coarse grain
and invoked. • Independent of consumer context, WSDL, UDDI, & SOAP are XML (eXtensible Markup Language)
• The service is self-contained. That is, • but a service can have a context
the service maintains its own state. • New services can be offered by combining existing services
• Quantifiable quality of service © Available at: http://www.computer‐science‐notes.blogspot.com

soa Page 1

Anda mungkin juga menyukai