Presentation on theme: "Paving the Bare Spots Towards an Enterprise-wide Defense Service Bus (DSB) Brad Cox, Ph.D. Binary Group firstname.lastname@example.org 31 Oct, 2006 Services Service."— Presentation transcript:
1 Paving the Bare SpotsTowards an Enterprise-wide Defense Service Bus (DSB)Brad Cox, Ph.D. Binary Group 31 Oct, 2006ServicesService Bus
2 The little man who wasn't there Last night I saw upon the stairA little man who wasn't thereHe wasn't there again todayOh, how I wish he'd go awayHarold Adamson Bernie Hanighen
3 Service-oriented Architecture (SOA) is not just about servicesEnterprise ServicesDefense Service Bus (DSB)Services are the bricks. The service bus is the mortar. The medium through which services interoperate
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/ABACNo asynchronous messaging interoperabilityNo 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 gapsUse external standard bodies and open source development groups as the model.OASIS (WS-Standards, …)Apache Software Foundation (Apache, Axis, …)
8 How to keep students off the grass? Paving the Bare SpotsHow to keep students off the grass?Punish the transgressorsKeep off the grass signsInteroperability policy directivesOr simply pave the bare spotsMake the desired behavior the easy oneProvide an enterprise DSB all projects can use.
9 Paving the Bare SpotsStandards 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 SpaceA 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 projectsWork is based on working prototypes contributed by the members (no design by powerpoint). Meritocracy.Actual membership determined by the foundation
11 Consensus Process Consensus Process Working Prototypes DOD Internal Standards (KIPs) Reference Implementations Compliance Tests
Your consent to our cookies if you continue to use this website.