The document discusses various design patterns for service-oriented architecture (SOA). It introduces SOA design patterns and categorizes them into three types: service inventory design patterns, service composition design patterns, and service design patterns. Each category contains multiple chapters that describe common problems in SOA design and provide proven solutions in the form of design patterns. The document assigns sections to different people to summarize.

1. SOA Design Pattern 2011.04.07

5. Type of SOA pattern Service Inventory Design Patterns Service Composition Design Patterns Service Design Patterns

6. Work assignment Huu Hau : 6, 7, 8 Van Khanh: 9, 10, 17 Lan anh : 11, 12, 13 Vu Doan: 14, 15, 16 Doan Lap 18,19,20,21

7. Service Inventory Design Patterns

8. Chapter 6

9. Chapter 7

10. Chapter 8

11. Chapter 9 Inventory Implementation Patterns

19. Chapter 10 Inventory Governance Patterns

23. 3. Service Composition Design Patterns

24. Chapter 17 Capability Composition Patterns

28. Chapter 18 Service Messaging Patterns

30. State Messaging Problem: When services are required to maintain state information in memory between message exchanges with consumers, their scalability can be comprised, and they can become a performance burden on the surrounding infrastructure. Solution: Instead of retaining the state data in memory, its storage is temporarily delegated to messages

31. Chapter 19 Composition Implementation Patterns

32. Composition Autonomy Problem: Composition controller services naturally lose autonomy when delegating processing tasks to composed services, some of which may be shared across multiple compositions. Solution: All composition participants can be isolated to maximize the autonomy of the composition as a whole

33. Atomic Service Transaction Problem: When runtime activities that span multiple services fail, the parent business task is incomplete and actions performed and changes made up to that point may compromise the integrity of the underlying solution and architecture . Solution: Runtime service activities can be wrapped in a transaction with rollback feature that resets all actions and changes if the parent business task cannot be successfully completed

34. Chapter 20 Service Interaction Security Patterns

35. Data Confidentiality Problem: Within service compositions , data is often required to pass through one or more intermediaries. Point-to-point security protocols, such as those frequently used at the transport-layer, may allow messages containing sensitive information to be intercepted and viewed by such intermediaries Solution: The message contents are encrypted independently from the transport, ensuring that only intended recipients can access the protected data.

36. Data Format Transformation Problem: How can a service verify the credentials provided by a consumer? Solution: Service capabilities require that consumers provide credentials that can be authenticated against an identity store

37. Chapter 21 Transformation Patterns

38. Data Format Transformation Problem: How can services interact with programs that communicate with different data formats? Solution: Intermediary data format transformation logic needs to be introduced in order to dynamically translate one data format into another

39. Protocol Bridging Problem: How can a service exchange data with consumers that use different communication protocols? Solution: Bridging logic is introduced to enable communication between different communication protocols by dynamically converting one protocol to another at runtime

40. 4. Service Design Patterns

41. Chapter 11 Foundational Service Patterns

42. Functional Decomposition Problem: To solve a large, complex business problem a corresponding amount of solution logic needs to be created, resulting in a self-contained application with traditional governance and reusability constraints Solution: The large business problem can be broken down into a set of smaller, related problems, allowing the r equired solution logic to also be decomposed into a corresponding set of smaller, related solution logic units

43. Service Encapsulation Problem: Solution logic designed for a single application environment is typically limited in its potential to interoperate with or be leveraged by other parts of an enterprise Solution: Solution logic can be encapsulated by a service so that it is positioned as an enterprise resource capable of functioning beyond the boundary for which it is initially delivered

44. Chapter 12 Service Implementation Patterns

45. Service Façade Problem: The coupling of the core service logic to contracts and implementation resources can inhibit its evolution and negatively impact service consumers Solution: A service façade component is used to abstract a part of the service architecture with negative coupling potential

46. Service Façade Problem: The coupling of the core service logic to contracts and implementation resources can inhibit its evolution and negatively impact service consumers Solution: A service façade component is used to abstract a part of the service architecture with negative coupling potential

47. Redundant Implementation Problem: A service that is being actively reused introduces a potential single point of failure t hat may jeopardize the reliability of all compositions in which it participates if an unexpected error condition occurs Solution: Multiple implementations of services with high reuse potential or providing critical functionality can be deployed to guarantee high availability and increased reliability, even when unexpected exceptions or outages occur

48. Chapter 13 Service Security Patterns

49. Exception Shielding Problem: Unfiltered exception data output by a service may contain internal implementation details that can compromise the security of the service and its surrounding environment Solution: Potentially unsafe exception data is “sanitized” by replacing it with exception data that is safe by design before it is made available to consumers.Unsafe exception- related data is “sanitized,” a process by which this information is identified and replaced with exception information that is safe by design

50. Message screening Problem: An attacker can transmit messages with malicious or malformed content to a service, resulting in undesirable behavior Solution: The service is equipped or supplemented with special screening routines that assume that all input data is harmful until proven otherwise

51. Chapter 14

52. Chapter 15

53. Chapter 16

54. Thanks for your attentions!