1 / 11

Building an Enterprise-wide Defense Service Bus for Enhanced Interoperability

This document explores the concept of an Enterprise-wide Defense Service Bus (DSB) to facilitate service-oriented architecture (SOA) within the Department of Defense (DoD). It discusses the importance of interoperability among various military branches and agencies, the necessity of mature standards, and the approach to developing a DSB that allows for seamless communication while encapsulating necessary security and standard compliance. Key recommendations include using external standards where available and ensuring that all projects can utilize a common DSB as an independent enterprise resource.

jeslyn
Download Presentation

Building an Enterprise-wide Defense Service Bus for Enhanced Interoperability

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. Paving the Bare Spots • Towards an Enterprise-wide Defense Service Bus (DSB) Brad Cox, Ph.D.Binary Groupbcox@binarygroup.com31 Oct, 2006 Services Service Bus

  2. The little man who wasn't there • Last night I saw upon the stair • A little man who wasn't there • He wasn't there again today • Oh, how I wish he'd go away • Harold AdamsonBernie Hanighen

  3. Service-oriented Architecture (SOA) is not just about services Enterprise Services Defense Service Bus(DSB) Services are the bricks. The service bus is the mortar.The medium through which services interoperate

  4. Interoperability • Other Agencies? • States? • Allies? MCEITS(Marines) ForceNet(Navy) DCGS, EITS(Air Force) CASPORT(NSA) NCES(DISA) FCS(ARMY)

  5. Of course, you don’t really need a service bus • Ensure that every developer fully understands the relevant standards and security policies. • Test every interaction to ensure it implements them correctly.

  6. You could even do without a DOD bus standard • Use only mature industry standards. • IP/TCP + border security (NIPRNET, SIPRNET) • +SSL +SOAP/REST +WSDL +UDDI +… • Do without features for which no mature standards exist… • No end to end message-level security. • No RBAC/ABAC • No asynchronous messaging interoperability • No real-time messaging. Best-effort only. • No intermittently connected enclaves

  7. A Better Approach • Use external standards when they exist. • Define internal DOD standards to fill essential requirements gaps • Use external standard bodies and open source development groups as the model. • OASIS (WS-Standards, …) • Apache Software Foundation (Apache, Axis, …)

  8. Paving the Bare Spots How to keep students off the grass? • Punish the transgressors • Keep off the grass signs • Interoperability policy directives • Or simply pave the bare spots • Make the desired behavior the easy one • Provide an enterprise DSB all projects can use.

  9. Paving the Bare Spots • Standards are necessary, not sufficient. You also need a working implementation (DSB) that projects can use. • Don’t require every service developer to understand and interpret standards correctly. Encapsulate them in the service bus. • Don’t expect each service to understand security and interoperability issues and implement them correctly. Encapsulate them in the service bus. • Deploy the bus independently of the services that use it. In enterprise space, not project space.

  10. Enterprise Space • A digital space within which an enterprise infrastructure is owned, designed, developed and deployed, independently of the projects that use it. • Web site and collaboration tools (Subversion, Bugzilla, etc) • Governed by a foundation similar to Apache Software Foundation (ASF). Accepts long-term ownership responsibility. • Staffed by volunteers from interested projects • Work is based on working prototypes contributed by the members (no design by powerpoint). Meritocracy. • Actual membership determined by the foundation

  11. Consensus Process WorkingPrototypes ConsensusProcess DOD Internal Standards (KIPs)Reference ImplementationsCompliance Tests

More Related