How To Write A Soa Blog Post

Transcription

1 SOA-Governance: Order vs. Chaos? Stefan Tilkov innoq Deutschland Copyright (c) 2008 innoq 1

2 Technologie-Beratung Fokus auf Architekturen für Individualsoftware und Systemintegration Seit 1998 in CH, Seit 1999 in D ca. 50 Mitarbeiter MDA seit 2002 Web Services und SOA seit 2003 Entwicklung in Java/J2EE, Java EE, Ruby on Rails innoq 2

3 Stefan Tilkov Geschäftsführer & Principal Consultant, innoq Deutschland GmbH Herausgeber (m. G. Starke) SOA-Expertenwissen, dpunkt Fachl. Leiter SOA-Lehrgang Euroforum Chefredakteur InfoQ SOA Community 3

4 governance 4

5 governance noun the action or manner of governing : a more responsive system of governance will be required. archaic sway; control : what, shall King Henry be a pupil still, under the surly Gloucester's governance? ORIGIN Middle English : from Old French, from governer (see govern ). 5

6 The act of affecting government and monitoring (through policy) the long-term strategy and direction of an organization. In general, governance comprises the traditions, institutions and processes that determine how power is exercised, how citizens are given a voice, and how decisions are made on issues of public concern. 6

7 In the context of SOA, governance defines the model to ensure optimal reuse of services and enforcement of corporate policies (eg, business design, technical design, and application security). 7

8 SOA Governance is the process, model and organization that ensures compliance to the service-oriented architecture as defined for the company. 8

9 Starting points 9

10 Starting points Top-down Strategic Expensive In advance 9

11 Starting points Top-down Strategic Expensive In advance Bottom-up Technical Expensive After the fact 9

12 Starting points Top-down Strategic Expensive In advance Bottom-up Technical Expensive After the fact YAGNI 9

13 Starting points Top-down Strategic Expensive In advance Bottom-up Technical Expensive After the fact YAGNI JABOWS 9

14 Starting points Top-down Strategic Expensive In advance Bottom-up Technical Expensive After the fact YAGNI JABOWS (You ain t gonna need it) 9

15 Starting points Top-down Strategic Expensive In advance Bottom-up Technical Expensive After the fact YAGNI (You ain t gonna need it) JABOWS (Just a bunch of web services) 9

16 3 Goals: 10

17 1. Architectural Control 11

18 2. Subsidiarity Principle 12

19 3. Knowledge 13

20 new tasks new roles 14

21 Roles 15

22 Roles 15

23 Existing Organization Corporate Quality & Processes CEO Corporate Strategy CIO VP LoB 1 VP LoB 2 CFO Development Operations 16

24 Existing Organization Corporate Quality & Processes CEO Corporate Strategy SOA Domain Architect CIO VP LoB 1 VP LoB 2 CFO Development Operations 16

25 Existing Organization Corporate Quality & Processes CEO Corporate Strategy SOA Domain Architect SOA Platform Architect CIO VP LoB 1 VP LoB 2 CFO Development Operations 16

26 Existing Organization Corporate Quality & Processes CEO Corporate Strategy SOA Domain Architect SOA Platform Architect CIO VP LoB 1 VP LoB 2 Business Service Owner CFO Development Operations 16

27 Existing Organization Corporate Quality & Processes CEO Corporate Strategy SOA Domain Architect SOA Platform Architect CIO VP LoB 1 VP LoB 2 Business Service Owner CFO Development Operations Technical Service Owner 16

28 Existing Organization SOA Governance Board Corporate Quality & Processes CEO Corporate Strategy SOA Domain Architect SOA Platform Architect CIO VP LoB 1 VP LoB 2 Business Service Owner CFO Development Operations Technical Service Owner 16

29 Roles & Lifecycle 17

30 Governance Structure 18

31 Governance Structure 18

32 Governance Structure 18

33 Governance Structure 18

34 Governance Structure 18

35 Governance Structure 18

36 Standards & Products 19

37 Inquiry find_binding find_business find_relatedbusinesses find_service find_tmodel get_bindingdetail get_businessdetail get_operationalinfo get_servicedetail get_tmodeldetail UDDI Publication save_binding save_business save_service save_tmodel delete_binding delete_business delete_publisherassertions delete_service delete_tmodel add_publisherassertions set_publisherassertions get_assertionstatusreport get_publisherassertions get_registeredinfo 420-page specification Finding and maintaining (meta-)model objects 20

38 News about UDDI 21

39 Registry vs. Repository Registry metadata references (runtime focus) Repository metadata data (governance focus) 22

40 Registry vs. Repository Registry metadata references (runtime focus) Repository metadata data (governance focus) UDDI 22

41 Registry vs. Repository Registry metadata references (runtime focus) Repository metadata data (governance focus) UDDI? 22

42 The Vendor Landscape? Acquisition OEM License 23

43 Reg/Rep Products Vendor(s) HP Mercury Systinet Software AG Fujitsu Infravio webmethods BEA Flashline IBM Product Systinet 2 CentraSite/X-Registry AquaLogic Registry Repository (ALER) registry_repository/ WebSphere Service Registry and Repository (WSRR) 24

44 UDDI (contd.) UDDI could be greatly simplified by using plain HTTP It would no longer be protocol-independent - but who cares? Atom (Syndication Format & Protocol) are a great match Approach taken in Mule Galaxy, WSO2 Registry, HP Systinet 2 See: 25

45 Sad Truths about Reg/Rep Solutions You will have more than one repository You will have more than one kind of metadata Products are too focused on web servicesbased SOA only Extensibility is key requirement and key problem 26

46 Governance & Modeling 27

47 What is a repository? It holds data It holds metadata Anything structured should be storable It should support many processes and tasks It should be open and decoupled It should support arbitrary queries 28

48 In other words 29

49 Who builds the model? Your vendor 30

50 Who builds the model? Your vendor vs. 30

51 Who builds the model? Your vendor vs. You 30

52 Modeling and SOA Governance Model Repository SOA Governance Repository Runtime Registry 31

53 Modeling and SOA Governance Interface Descriptions Datatypes/Schemas SOA Governance Repository Model Repository Runtime Registry 31

54 Modeling and SOA Governance Interface Descriptions Datatypes/Schemas SOA Governance Repository Model Repository Service Status Schemas Runtime Registry 31

55 Modeling and SOA Governance Interface Descriptions Datatypes/Schemas SOA Governance Repository Model Repository Service Status Schemas Usage Information Response Times Throughput Runtime Registry 31

56 Modeling and SOA Governance Interface Descriptions Datatypes/Schemas SOA Governance Repository Model Repository Stability Info Critical Areas Service Status Schemas Usage Information Response Times Throughput Runtime Registry 31

57 Key Connections UML Interfaces WSDL porttype WSDL service UML Classes XML Schema Types Physical Endpoint Governance Development Runtime 32

58 Meta Integration Examples 1. Transform UML to WSDL/XSD 2. Import WSDL/XSD to UML 3. Use UML to model (proprietary) repository structure 4. Transform (proprietary) enterprise model to vendor repository structure 5. Merge UML and XSD modeling 33

59 Summary Develop a consistent process across modeling and governance tasks Don t try to do everything at once start small Accept your responsibility for defining your own model and process 34