Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

SOA Governance

4,055 views

Published on

Sumedha Rubasinghe - WSO2 Product Manager for the WSO2 Governance Registry product at the SOA Workshop in Colombo, Sri Lanka (September 17, 2009) presents about the need for governance in an enterprise SOA.

Published in: Technology, Education

SOA Governance

  1. 1. SOA Governance Sumedha Rubasinghe (sumedha@wso2.com)
  2. 2. 2 Agenda  What & Why?  When & How?  WSO2 Governance Registry  Important Concepts  Best Practises  Patterns in SOA Governance
  3. 3. 3 Hi...Chanaka here. I am an Architect.
  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. 13 What a mess ..... :-( How can I make this better?
  14. 14. 14 Solution  SOA Governance can solve this problem  Governance applied to 4 phases – Architectural Governance – Design time Governance – Operational Governance – Organisational/Political Governance
  15. 15. 15 Ok.. show me how..
  16. 16. 16 Architectural Governance
  17. 17. 17 Design Time Governance
  18. 18. 18 Design Time Governance
  19. 19. 19 Design Time Governance
  20. 20. 20 Design Time Governance
  21. 21. 21 Design Time Governance
  22. 22. 22 Design Time Governance
  23. 23. 23 Design Time Governance
  24. 24. 24 hmm....ok.. now we have services in production. What's next?
  25. 25. 25 Operational Governance
  26. 26. 26 Operational Governance
  27. 27. 27 Operational Governance
  28. 28. 28 Operational Governance
  29. 29. 29 Operational Governance
  30. 30. 30 Operational Governance
  31. 31. 31 Operational Governance
  32. 32. 32 Operational Governance
  33. 33. 33 Operational Governance
  34. 34. 34 My organisation follows an adhoc methodology...
  35. 35. 35 Organisational/Political Governance
  36. 36. 36 Show me how the scenario changes after following all these..
  37. 37. 37 SOA Governance applied...
  38. 38. 38 Hmm.. looks lot cleaner.. How to identify if I have Problems in my SOA Governance framework?
  39. 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
  40. 40. 40 Quality of execution  Good one – Well scoped, recognisable business benefits – Sharing of services & data types – Ability to recognise issues early
  41. 41. 41 Looks like Registry/Repository is a key concept..
  42. 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 – jaxb-mappings.xml
  43. 43. 43 So.. what does WSO2 has to offer in this space?
  44. 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)
  45. 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 – 100% integrated to all other products – Local and remote access
  46. 46. 46 WSO2 Governance Registry
  47. 47. 47
  48. 48. 48 WSO2 Governance Registry
  49. 49. 49 Looks like service is a key component in SOA...
  50. 50. 50 Service in SOA  Heart of SOA  Life cycle – Designed – Developed – QA passed – In Production  Metadata – WSDL – Schema – Policy  Publish & Discovery
  51. 51. 51 Service in SOA
  52. 52. 52 If I am evaluating a SOA Governance Product, what are the keys features/core concepts to look for?
  53. 53. 53 Core Concepts  Versioning
  54. 54. 54 Core Concepts  Publish & Discovery
  55. 55. 55 Core Concepts  Associations & Dependencies – Relationship between resources
  56. 56. 56 Core Concepts  Federation R1 R2 R
  57. 57. 57 Core Concepts  Control (Permissions)
  58. 58. 58 Core Concepts  Control (Life cycles)
  59. 59. 59 Core Concepts  Control (Life cycles)
  60. 60. 60 Core Concepts  Control – Validations (Built-in: WS-I, WSDL) – Check lists
  61. 61. 61
  62. 62. 62 Core Concepts  Monitoring (Notifications)
  63. 63. 63 Core Concepts  Monitoring (Dashboard)
  64. 64. 64 Important Concepts  Monitoring (Dashboard)
  65. 65. 65 Core Concepts  Auditing
  66. 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)
  67. 67. 67 I want to introduce SOA Governance to my organisation. Give me some best practises..
  68. 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
  69. 69. 69 If I use WSO2 Governance Registry, what are the recommended deployment Architectures? ..
  70. 70. 70 Deployment Architecture 1
  71. 71. 71 Deployment Architecture 2
  72. 72. 72 Are there patterns associated with SOA Governance?
  73. 73. 73 Patterns – Compatible Change • Problem - Changing an already-published service contract can impact and invalidate existing consumer programs.
  74. 74. 74 Patterns – Compatible Change
  75. 75. 75 Patterns – Compatible Change
  76. 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.
  77. 77. 77 Pattern – Version Identification
  78. 78. 78 Pattern – Version Identification
  79. 79. 79 Pattern – Proxy Capability  Problem - How can a service subject to decomposition continue to support consumers affected by the decomposition?
  80. 80. 80 Pattern – Proxy Capability
  81. 81. 81 Pattern – Proxy Capability
  82. 82. 82 Pattern – Distributed Capability  Problem - How can a service preserve its functional context while also fulfilling special capability processing requirements?
  83. 83. 83 Pattern – Distributed Capability
  84. 84. 84 Pattern – Distributed Capability
  85. 85. 85 Pattern – Termination Notification  Problem - How can the scheduled expiry of a service contract be communicated to consumer programs?
  86. 86. 86 Pattern – Termination Notification
  87. 87. 87 Pattern – Termination Notification
  88. 88. 88 How do I get started?
  89. 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
  90. 90. 90 Help... I messed it up
  91. 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 – Custom Development – Production Support
  92. 92. 92 Summary
  93. 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)
  94. 94. 94 Thank you

×