Enterprise Soa Concept


Published on

Simple concept of SOA

1 Like
  • Be the first to comment

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

No notes for slide

Enterprise Soa Concept

  1. 1. Chapter 4. Service Oriented Architecture “ Enterprise SOA Service Oriented Architecture Best Practice” 2006-05-17 Byungwook Cho K.
  2. 2. What is software architecture? <ul><li>“ An architecture is the set of significant decisions about organization of a software system” – Booch, Rumbaugh, Jacobson </li></ul><ul><li>“ The software architecture of program or computing system is the structure or structure of system, which comprise software elements, the externally visible properties of those elements, and relationships among them” – Brass, Clements, and Kazman </li></ul>
  3. 3. What is SOA? <ul><li>&quot;A SOA is software architecture that is based on the key concepts of application frontend,service,service repository, and service bus. A service consists of contract (WSDL), interface and implementation &quot; </li></ul>
  4. 4. Elements of SOA <ul><li>SOA is based on four key abstraction </li></ul><ul><ul><li>Application frontend </li></ul></ul><ul><ul><li>Service </li></ul></ul><ul><ul><li>Service Repository </li></ul></ul><ul><ul><li>Service Bus </li></ul></ul>
  5. 5. Life cycle of elements in SOA <ul><li>The estimated lifecycles of data,services, application frontends , and technologies are different </li></ul>
  6. 6. Application front end <ul><li>Application frontend is </li></ul><ul><ul><li>Active player of an SOA </li></ul></ul><ul><ul><li>Service consumer </li></ul></ul><ul><ul><li>Initiate and control all activity of enterprise system </li></ul></ul>
  7. 7. Service <ul><li>Service is component of distinctive functional meaning that typically encapsulate a high-level business concept </li></ul><ul><li>Consists of </li></ul><ul><ul><li>Contract </li></ul></ul><ul><ul><ul><li>purpose, functionality, constraint, usage of service </li></ul></ul></ul><ul><ul><li>Interface </li></ul></ul><ul><ul><ul><li>Physical implementation of interface </li></ul></ul></ul><ul><ul><li>Implementation </li></ul></ul><ul><ul><ul><li>programs, configuration data ,database </li></ul></ul></ul><ul><ul><ul><li>Business logic , Data </li></ul></ul></ul>NOTE : The types of service [ from Service Oriented Architecture - Thomas Erl] Business Service vs Technical Service (utility Service, application service) Process service, Task centric service, Entity centric business service, utility application service. Hybrid application service.
  8. 8. Service <ul><li>Conceptual structure of service </li></ul>NOTE: Every service is an entity of distinctive functional meaning that typically encapsulates a high-level business entity. Services impose a strong vertical slicing of application that defines the coarse-grained structure of the whole system.
  9. 9. Service repository <ul><li>Service repository is “provides facilities to discover services and acquire all information to user the service “ </li></ul><ul><li>Service repository is indispensable in long term </li></ul><ul><li>It contains </li></ul><ul><ul><li>In addition to service contract : location,provider,contact ,usage fee,technical constraints,security issues and availble service level </li></ul></ul><ul><ul><li>SVC Info,ACL,SLA,Transactional properties of SVC & operation (CRUD) </li></ul></ul><ul><ul><li>In cross enterprise : security,user registration, service subscription,billing and versioning </li></ul></ul>
  10. 10. Service repository <ul><li>Binding Type </li></ul><ul><ul><li>Development time binding </li></ul></ul><ul><ul><li>Runtime binding </li></ul></ul><ul><ul><ul><li>By name </li></ul></ul></ul><ul><ul><ul><li>By properties </li></ul></ul></ul><ul><ul><ul><li>By reflection  method 를 가지고 오지만 , function 에 call 방식을 미리 알 수 없다 . Meta data 로 call 에 필요한 argument 들을 가지고 오고 , 거기에 argument 에 필요한 내용을 mapping 한다 . </li></ul></ul></ul><ul><ul><ul><li>* It can be replaced by ESB routing feature </li></ul></ul></ul>
  11. 11. Service bus <ul><li>A service bus connects all participants of an SOA services and application frontend </li></ul><ul><li>Characteristics of service bus </li></ul><ul><ul><li>Connectivity </li></ul></ul><ul><ul><li>Heterogeneity of technology </li></ul></ul><ul><ul><li>Heterogeneity of communication concept (MEP) </li></ul></ul><ul><ul><li>Technical service : logging,auditing,security,transformation,transaction </li></ul></ul>