Published on

Software Orientated Architecture

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. SOAPresented By : Travis Frisinger
  2. 2. SOA : An overview• What is SOA o An architecture for building businesses applications o Loosely coupled blackbox modules o These modules are composed into well defined services o Promotes reuse at the macro (service) level rather than micro (classes) level
  3. 3. SOA : An overview• SOA is not Webservices o DCOM (Distributed Component Object Model ) Microsoft version of RPC o CORBA (Common Object Request Broker Architecture ) Cross language open standard for RPC o Java RMI (Java Remote Method Invocation) Javas implementation of RPC o WCF
  4. 4. SOA: Architectural Style
  5. 5. SOA Manifesto• Business value over technical strategy• Strategic goals over project-specific benefits• Intrinsic interoperability over custom integration• Shared services over specific-purpose implementations• Flexibility over optimization• Evolutionary refinement over pursuit of initial perfection
  6. 6. SOA Service Attributes• Stateless o A service neither remember what it did, nor cares what comes next. There is no dependence upon other services state• Discoverable o A service must be discoverable by consumers of the service. Usually via the SOA service directory.• Self-Describing o The service interface describes, exposes and provides an entry-point into the service. o A consumer never needs to know about the technology used to create the service.
  7. 7. SOA Service Attributes• Composable o A service is created from other services in a composite manor. In turn other services may use the composed services to create new services, hence new business value.• Loose Coupling o Separation of concerns through boundaries; a logical or physical delineation of responsibilities. o i.e. An account service with : open, authorize and audit features.
  8. 8. SOA Service Attributes• Governed by Policy o Services are built by contract. The relationship between services is regulated by an SLA.• Indifferent to Location, Language and Protocol o A service shall be accessible by an authorized user in any location on any platform.
  9. 9. SOA Service Attributes• Coarse-Grained o Due to the fact that services are business functions, not block of code, it is critical that they remain broad in terms of the contract they define. o The more coarse the service is, the more business value it brings. o Coarse services reduce complexity, by reducing the number of steps required, hence the number of remote operations to be sent across the wire.• Asynchronous o Not required for services, but increases scalability. o Achieved with an Enterprise Service Bus (ESB)
  10. 10. SOA LayersPhoto :
  11. 11. SOA : The role of ESB• A software architecture model used for designing and implementing the interaction and communication between services in SOA.• Strictly asynchronous message oriented design for communication and interaction• Performs o Message routing o Mediation o Transformation o Queuing and staging o ....
  12. 12. SOA : References1.2. Resources•••••