Federated SOA
•Download as PPTX, PDF•
0 likes•517 views
Presentation of Federated SOA Implementation
Recommended
Recommended
More Related Content
Similar to Federated SOA
Similar to Federated SOA (20)
Recently uploaded
Recently uploaded (20)
Federated SOA
- 1. FEDERATED SOA Self Governance of Shared Services
- 2. OPEN GROUP SOA BEST PRACTICES • Well-Defined Service Contract • Define Services with Appropriate Granularity • Loosely-Coupled Services • Design Services for Stateless • Ensure Services have Appropriate Security Enforcement Standards • Adopt SOA Ontology/Vocabulary Standard
- 3. SN SPECIFIC SOA ISSUES • Governance • Distributed teams = distributed entity responsibilities • Data migrations = V1 to V2 to V3 • Separating Business from Application concerns (BSOA vs. USOA) • We can tackle most of these issues through a federated SOA solution
- 4. GARTNER’S 7 STEPS TO SUCCESS 1. Determine whether to adopt a reactive or proactive approach 2. Appoint the federated SOA leadership team 3. Design the SOA domains topology 4. Establish the Organizational Model 5. Draft federal governance processes 6. Establish inter-domain interoperability standards 7. Set out key performance indicators
- 5. SN.DOMAIN • New Federated SOA project for shared entities – separate from V2 • SN.Domain solution has multiple projects corresponding to apps • Currently: Claims, LRS, and LPT • DLL’s from Domain projects will be distributed via proget • Services will be hosted in V2 apps by adding DLLs via proget
Editor's Notes
- Well-Defined Service Contract Describes point of integration through loose coupling (example: WSDL) Service Broker Define Services with Appropriate Granularity Granular to be useable to build business apps/functionality SN Services will be built around entities Loosely-Coupled Services “Black box” to service consumers – loose coupling Design Services for Stateless A service call is a transaction – any state must be maintained by clients Ensure Services have Appropriate Security Enforcement Standards Adopt SOA Ontology/Vocabulary Standard
- 1. Proactive approach – New V3 Architecture and V2 dev teams already provide clear business delineations 2. Black Ops Team is fulfilling that role at the moment. 3. We have started defining the domain topology using LPT, LRS, and Claims as initial entities 4. Three models to choose from: Virtual – Team’s work independently and meet periodically to coordinate organization under guidance of Black Ops Team Heirarchal – Black Ops Team is in charge of maintaining domain, including standards, governance and technology Mediator – Black Ops operates as mediator between between independent teams 5. TBD 6. Lucas will go into detail about technical and interoperability standards – i.e. how domain services are hosted in V3 apps. 7. TBD