1 / 17

What is a Composable Service?

What is a Composable Service?. 12 th Federal SOA for eGov Conference October 11, 2011 Presented by Dave Mayo ( dmayo@everware-cbdi.com ) Denzil Wasson (dwasson @everware-cbdi.com ) . Topics. State of SOA in Federal Government History of Federal Sharing Initiatives

walt
Download Presentation

What is a Composable Service?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. What is a Composable Service? 12th Federal SOA for eGov Conference October 11, 2011 Presented by Dave Mayo (dmayo@everware-cbdi.com) Denzil Wasson (dwasson@everware-cbdi.com )

  2. Topics • State of SOA in Federal Government • History of Federal Sharing Initiatives • Shared Services vs. SOA • Composable Services • Demo: Composable Services in Agile IT – Denzil Wasson • SOA • Model-Driven Development

  3. State of SOA in Federal Government • The Good • Guidance & direction from OMB & CIO Council – the pressure is building • Most agencies recognize the need for SOA as a best practice and are taking steps to adopt it • Business/mission side is getting more involved • Cloud computing is driving interest in SOA • Some successes in implementing SOA • The Bad • Many still consider SOA to be an integration technology • Some have tried and hit the wall – mostly because they did not consider all of the CSFs for SOA (Roadmap planning, Governance, SOA Maturity) • Many services sit in the registry and are not consumed due to poor service specs and lack of defined policies (governance) • SDLCs do not incorporate service discovery and consumption steps • Confusion between Shared Services and SOA

  4. Cloud-First 2010 Lines of Business Round 2 (Geo, BFE, ITI, ISS) 2006 E-Gov Initiatives Round 2 (DAIP, ITDS, IAD-Loans/Grants) 2008 Shared Services 2011 Lines of Business Initial 5 (HR, GM, FM, FHA,CM) 2004 E-Government Act 2002 Quicksilver 2001 Payroll Consolidation Completes 2009 E-Gov Initiatives Initial 25 2003 Clinger-Cohen 1996 GAO Report: Opportunities to Reduce Potential Duplication 2011 History of Federal Sharing Initiatives

  5. What is a Shared Service? OMBDefinition: Mission or support function that is provided by one business unit to multiple business units. Shared Service Producer Provider Consumers • Roles: Provider, Producer, Consumer • Sources: Internal or external to the agency (government or commercial).

  6. CIO Executive Board Survey – Shared Services • Survey of 50 large corporations • Only 40% of businesses able to capture the cost-saving benefits of shared services • Inadequate set of services or services hard to use • Lack of customer focus and service skills • No long-term plan to ensure continued cost savings (TCO) • Best organizations generated: • Strategic benefits (eg, agility) • Significant cost savings • Conclusion • “Best shared service organizations understand that service orientation and long-term strategy are the most critical components for success.” • In other words – Service Oriented Architecture!

  7. What is Service Oriented Architecture • “Service” – Independent unit of functionality that is accessed via a well-defined interface; consumer needs are met by provider capabilities • “Oriented” – Beyond a single service; covers a business domain & includes governance, management, and administration of the services in the domain • “Architecture” – Critical factor in managing complexity; ensures that all components work together and boundaries are clearly defined • SOA Principles • Loose coupling • Service abstraction • Statelessness • Discoverability • Interoperability • Autonomy • Standard service contract • Composability It’s Not SOA, if there is no ARCHITECTURE!

  8. Shared Services vs. SOA Shared Service, but not SOA Shared Service Shared Service with SOA Silos, Unstructured code, Point-to-point Shared Service Layered Service Model

  9. Benefits of Services • Business Agility • Time to Market – Speed! • Customer responsiveness • IT flexibility Service Oriented Architecture • Reuse • Cost savings • Consistency • Collaboration & interoperability • Skills transfer Shared Services SOA is an Architecture; Shared Services is a collection of services (eg, JBOWS)

  10. Composable Services • Shared services must be architected for consumption • Well defined interface; well encapsulated; highly independent • Discoverable (catalog) – good description/specification • Standards for integration, interoperability, semantics, security • Functional boundaries determined by architecture • Solution architecture & requirements must consider available services • Product Line Approach (SEI) • A software product line (SPL) is a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way. • Product Line Benefits: • Reduction of code size; higher quality code. • Uniform look and feel. • Common technological platform and code style. • Easier reuse, maintenance and integration • Shorter development schedules • Lower development and upgrade costs • Lower total ownership costs • Support for an incremental development model • Shared technology costs • Best-in-class COTS/government off-the-shelf (GOTS) components • Continuous technology insertion

  11. Summary • Composable Services are Shared Services that are designed and architected to work together • In a manner similar to a Software Product Line approach • Adhere to the SOA principles

  12. Composability Demo: Service Oriented Application Modernization Combines: SOA, Model-Driven Development & Agile Methods MDA Agile Methods (SCRUM) SOA SOAM

  13. Themes for Demo • Services are the composable building blocks • Services provide important architectural articulation points • MDD makes it visible, manageable and productive • Agile is a good fit • Defined scope • Contract driven • Early value

  14. Business process (snippet) login Pick an application Review an application (options) Submit an application Review pricing Pay

  15. SOA (snippet) Examiner portal Applicant portal solution AD = Application Drafting AS = Application Submission AR = Application Review PM = Profile Management D.App = Draft Application App = Application process AD AS AR core App D.App PM underlying Rules Persistence Payments Security (auth/auth) utility Fees Inbox Payment processor AWS Simple DB

  16. TechnicalArchitecture (overview) presentation integration application data OTS Components JSF web applicant portal Service POJO Service implementations POJO channel delegates Service Endpoints JSF web examiner portal ServiceMix ESB Cloud Services tomcat servicemix Jvm / Amazon (AWS) Amazon (AWS)

  17. Specialists in Service Oriented Application Modernization Dave Mayo dmayo@everware-cbdi.com (703) 564-0263 Denzil Wasson dwasson@everware-cbdi.com www.everware-cbdi.com

More Related