WSO2 SOA Governance

1,643 views
1,476 views

Published on

Published in: Technology, Education
1 Comment
1 Like
Statistics
Notes
No Downloads
Views
Total views
1,643
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
173
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide

WSO2 SOA Governance

  1. 1. Santa Clara SOA Governance
  2. 2. Agenda  What & Why?  When & How?  WSO2 Governance Registry  Important Concepts  Best Practises  Patterns in SOA Governance 2
  3. 3. Hi...Chanaka here. I am an Architect. 3
  4. 4. 4
  5. 5. 5
  6. 6. 6
  7. 7. 7
  8. 8. 8
  9. 9. 9
  10. 10. 10
  11. 11. 11
  12. 12. 12
  13. 13. What a mess ..... :-( How can I make this better? 13
  14. 14. Solution  SOA Governance can solve this problem  Governance applied to 4 phases – Architectural Governance – Design time Governance – Operational Governance – Organisational/Political Governance 14
  15. 15. Ok.. show me how.. 15
  16. 16. Architectural Governance 16
  17. 17. Design Time Governance 17
  18. 18. Design Time Governance 18
  19. 19. Design Time Governance 19
  20. 20. Design Time Governance 20
  21. 21. Design Time Governance 21
  22. 22. Design Time Governance 22
  23. 23. Design Time Governance 23
  24. 24. hmm....ok.. now we have services in production. What's next? 24
  25. 25. Operational Governance 25
  26. 26. Operational Governance 26
  27. 27. Operational Governance 27
  28. 28. Operational Governance 28
  29. 29. Operational Governance 29
  30. 30. Operational Governance 30
  31. 31. Operational Governance 31
  32. 32. Operational Governance 32
  33. 33. Operational Governance 33
  34. 34. My organisation follows an adhoc methodology... 34
  35. 35. Organisational/Political Governance 35
  36. 36. Show me how the scenario changes after following all these.. 36
  37. 37. SOA Governance applied... 37
  38. 38. Hmm.. looks lot cleaner.. How to identify if I have Problems in my SOA Governance framework? 38
  39. 39. Quality of execution  Bad one – No planning and coordination of service projects – Single-use services and point-to-point connections – Change Management issues 39
  40. 40. Quality of execution  Good one – Well scoped, recognisable business benefits – Sharing of services & data types – Ability to recognise issues early 40
  41. 41. Looks like Registry/Repository is a key concept.. 41
  42. 42. Registry/Repository  Service configurations – wsdl  Server configurations – jboss.xml – server.xml  Deployable artifacts – jar,aar,ear,war,etc..  Meta data related to implementations – hibernate-config.xml 42 – jaxb-mappings.xml
  43. 43. So.. what does WSO2 has to offer in this space? 43
  44. 44. WSO2 Governance Registry  Lightweight registry & repository  Governance framework for building customer specific governance features  Open Source - Apache License, Version 2.0  Commercial support available (if needed) 44
  45. 45. WSO2 Governance Registry  Features – Simple, lightweight registry with 100% RESTful interface powered by Atom and AtomPub – Hierarchical authentication and authorization support – Dependency management, Lifecycles and dashboard – Highly extensible via media type specific handles and more – Social features including tagging and rating of all resources 45
  46. 46. WSO2 Governance Registry 46
  47. 47. 47
  48. 48. WSO2 Governance Registry 48
  49. 49. Looks like service is a key component in SOA... 49
  50. 50. Service in SOA  Heart of SOA  Life cycle – Designed – Developed – QA passed – In Production  Metadata – WSDL – Schema 50 – Policy
  51. 51. Service in SOA 51
  52. 52. If I am evaluating a SOA Governance Product, what are the keys features/core concepts to look for? 52
  53. 53. Core Concepts  Versioning 53
  54. 54. Core Concepts  Publish & Discovery 54
  55. 55. Core Concepts  Associations & Dependencies – Relationship between resources 55
  56. 56. Core Concepts  Federation R1 R2 R 56
  57. 57. Core Concepts  Control (Permissions) 57
  58. 58. Core Concepts  Control (Life cycles) 58
  59. 59. Core Concepts  Control (Life cycles) 59
  60. 60. Core Concepts  Control – Validations (Built-in: WS-I, WSDL) – Check lists 60
  61. 61. 61
  62. 62. Core Concepts  Monitoring (Notifications) 62
  63. 63. Core Concepts  Monitoring (Dashboard) 63
  64. 64. Important Concepts  Monitoring (Dashboard) 64
  65. 65. Core Concepts  Auditing 65
  66. 66. Core Concepts  Extensibility – Most important of all.. – Governance cannot be bought, you need to customise it.. – BAM (Business Activity Monitoring) – BI (Business Intelligence) gathering – CEP (Complex Event Processing) 66
  67. 67. I want to introduce SOA Governance to my organisation. Give me some best practises.. 67
  68. 68. Best Practises  Establish early  Organisational acceptance for Governance  Communicate relentlessly  Automate  Govern the entire service lifecycle  Anticipate mixed technologies  Monitory,access & report business value  Consider cross organisational boundaries 68
  69. 69. If I use WSO2 Governance Registry, what are the recommended deployment Architectures? .. 69
  70. 70. Deployment Architecture 1 70
  71. 71. Deployment Architecture 2 71
  72. 72. Are there patterns associated with SOA Governance? 72
  73. 73. Patterns – Compatible Change • Problem - Changing an already-published service contract can impact and invalidate existing consumer programs. 73
  74. 74. Patterns – Compatible Change 74
  75. 75. Patterns – Compatible Change 75
  76. 76. Pattern – Version Identification  Problem - When an already-published service contract is changed, unaware consumers will miss the opportunity to leverage the change or may be negatively impacted by the change. 76
  77. 77. Pattern – Version Identification 77
  78. 78. Pattern – Version Identification 78
  79. 79. Pattern – Proxy Capability  Problem - How can a service subject to decomposition continue to support consumers affected by the decomposition? 79
  80. 80. Pattern – Proxy Capability 80
  81. 81. Pattern – Proxy Capability 81
  82. 82. Pattern – Distributed Capability  Problem - How can a service preserve its functional context while also fulfilling special capability processing requirements? 82
  83. 83. Pattern – Distributed Capability 83
  84. 84. Pattern – Distributed Capability 84
  85. 85. Pattern – Termination Notification  Problem - How can the scheduled expiry of a service contract be communicated to consumer programs? 85
  86. 86. Pattern – Termination Notification 86
  87. 87. Pattern – Termination Notification 87
  88. 88. How do I get started? 88
  89. 89. Getting started with WSO2 Governance Registry  Download binary distribution from – http://wso2.org/downloads/governance-registry  Latest is v3.0.0  Unzip  Run bin/wso2server.sh (on Unix) or bin/wso2server.bat (on Windows)  Management console – https://localhost:9443/carbon – admin/admin 89
  90. 90. Help... I messed it up 90
  91. 91. How to get help?  Oxygen Tank for Web Service Developers – wso2.org  Online forum – http://wso2.org/forum/351  Mailing List – carbon-user@wso2.org  Commercial Support (if required) – Training – Consultancy 91
  92. 92. Summary 92
  93. 93. References  http://soa.sys-con.com/node/175376/print (SOA Governance Best Practices – Architectural, Organizational, and SDLC Implications)  http://www.informit.com/articles/printerfriendly.aspx?p (SOA Design Patterns: Service Governance Patterns) 93
  94. 94. Thank you 94

×