mitre cloud soa

8/2/2019 Mitre Cloud SOA

1/20

SERVICE-ORIENTED ARCHITECTURE (SOA) SERIES

Systems Engineering at MITRE

Cloud Computingand SOA

Geoffrey Raines

proved for Public Release; Distribution Unlimited

se # 09-0743


2/20


3/20


4/20

iiService-Oriented Architecture

soware components as an integration technology.Te need to support broader and more consistentintegration o systems will continue. Te growingtrend by leadership teams to consider I capabili-ties as a commodity will continue to put downwardpressure on I budgets; consequently, system inte-gration and data exchange activities will have to getmore streamlined and e cient across a portolio o

disparate systems. SOA inspired componentizationeforts, where soware leverages other network-based soware using standards-based interaces, area response to this pressure. Similarly, consideringplatorm and storage services as a scalable commod-ity will push organizations to use these less expen-sive service oferings, since the trend toward SOAand cloud computing has many o the same drivers,such as enterprise portolio cost reduction.

How can the DoD leverage cloud computing?Mission assurance considerations such as security

and survivability will make the use o wholly com-mercial cloud oferings a challenge in the near term.However, the DoD can begin to work with industryto create cloud capabilities resident on DoDs ownsensitive and classied networks as private clouds,enjoying many o the benets o cloud computingsuch as more rapid and dynamic resource provision-ing, but probably not resulting in the same econo-mies o scale.

Te DoD should initiate a cloud pilot efort toexercise cloud technologies on real-world DoD

networks. Tis engineering efort would examinethe commercial cloud computing marketplaceand the cloud computing stack rom hardware to

applications, and compare it to the needs o selectkey DoD programs. Te efort would apply com-mercial approaches and technologies cooperativelywith industry, and exercise these oferings in a real-istic sensitive or classied environment, recogniz-ing clouds inherent dependence on the underlyingnetwork. Te value o the pilot to the programs andthe DoD would be assessed.

DoD cloud computing considerations include:

Economies o scale: Cloud computing, due toinherent cost advantages when implemented ona large scale, will continue to impact the com-mercial marketplace regarding how commercialI inrastructure is acquired, maintained, anddynamically scaled. Te DoD can apply thesecommercial concepts on DoD internal networksto create private cloud oferings.

Key obstacles: Robust networks and trusted

security are two o the biggest obstacles that theDoD should ocus on in order to take advantageo cloud economics.

Enables services ocus: Because cloud comput-ing abstracts away the details o the inrastruc-tures hardware and soware, turning the lowerlevels into a utility whose implementation detailsare no longer visible to the user, cloud comput-ing will advance the ocus o DoD investmentstoward the composable services and sowarecapabilities that sit on top o the clouds com-modities. As a result, more high-value end-user

capability can be acquired in the long term bytaking advantage o cloud and SOA concepts.

For more inormation on SOA, see http://www.mitre.org/soa.
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


5/20

Table of Contents

Defining Cloud Computing 1

Defining SOA 5

Comparing Cloud Computing and SOA 7

Can SOA Be Skipped for Cloud Computing? 8

How Can the DoD Take Advantage of Cloud Computing? 9

References 12
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


6/20


7/20

Cloud Computing and SOA1

Cloud Computing and SOA Geoffrey Raines

THE BIG PICTURE: Cloud computing describes a broad movement toward the use of wide area net-

works, such as the Internet, to enable interaction between information technology service providers and

consumers. Cloud computing has a number of benefi ts and risks that should be examined by any senior

leadership team considering the realignment of its enterprise computing IT portfolio. SOA and cloud com-

puting are complementary activities, and both will play important roles in IT planning.

Defining Cloud Computing

While cloud computing is currently a term withouta single consensus meaning in the marketplace,it describes a broad movement toward the use owide area networks, such as the Internet, to enableinteraction between I service providers o manytypes and consumers. Service providers are expand-ing their available oferings to include the entiretraditional I stack, rom hardware and platormsto application components, soware services, andwhole applications, as shown in Figure 1. Te com-mon thread in cloud computing oferings across all

levels o the stack is the consumer/provider relation-ship and a dependence on the network to connect

the two parties.

Te commercial cloud marketplace ofers a widerange o cloud services that vary in complexity andvalue. Figure 1 organizes this marketplace into ageneral set o service categories layered in a notionalstack, with oundational oferings toward the bot-tom and more complex oferings toward the top.For example, the Cloud Storage in the gure candescribe the ability to saely store a le in the cloud,while Cloud Applications reers to executing more

Figure 1. Cloud Computing Represented as a Stack of Service Offering Categories 1

Cloud ClientsPresentation Layer

Example: browsers, mobile devices

Cloud ApplicationsSoftware as a Service

Example: Google docs or calendar

Cloud ServicesComponents as a Service

Example: SOA via Web Service standards

Cloud PlatformPlatform as a Service

Example: web server, app server

Cloud StorageStorage as a Service

Note: formerly utility computing

Cloud InfrastructureDistributed Multi-site Physical Infrastructure

Note: enabled by server virtualization
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


8/20

2Service-Oriented Architecture

complex network-accessiblesoware applications. Tenext paragraphs exploreseveral o the key layers inthe cloud computing stack,rom the bottom up.

Cloud InrastructureAt

the bottom o the cloudstack, Cloud Inrastructureprovides the distributedmulti-site physical compo-nents to support cloud com-puting, such as storage andprocessing resources. Tislayer allows the inrastruc-ture provider to abstractaway details such as whichexact hardware an applica-tion is using and which data

center the application is run-ning in. Advances in servervirtualization technologieshave made this layer o thestack much more e cientover the past several years,

allowing a higher utilization o processing resourcesthan previously practical. Virtual machine conceptshave also enabled a useul separation o underly-ing hardware implementation details rom the viewo developers, and the ability to more rapidly scaleserver resources in response to changing demand.

Cloud StorageStorage as a serviceBuildingupon the Cloud Inrastructure, this layer o thecloud stack is ocused on the incremental rentingo storage on the Internet, ormerly called UtilityComputing. Many oferings in this area are alsoenabled by underlying advances in server virtualiza-tion. Network-based large-scale storage on demandis an example o this layer o cloud computing. Someoferings go urther and ofer platorms or serviceproviders, including storage, security, identity man-agement, and other unctions. A good example o

this type o ofering is the Amazon Simple StorageService (Amazon S3). Amazon S3 provides storageor the Internet, designed to make web-scale com-puting easier or application developers. Amazon S3provides a Web Service interace that can be used tostore and retrieve data, at any time, rom anywhereon the Web. S3 gives developers access to scalable

and reliable data storage or a ee.3 S3 is decentral-ized in its implementation, ault tolerant, and builtrom a set o highly granular and simple serviceinteraces.

Cloud PlatormPlatorm as a servicePlatorm oferings provide an inrastructure ordeveloping and operating web-based soware

applications. Examples include acilities or appli-cation design, application development, testing,deployment, and hosting, as well as applicationservices such as teamcollaboration, security,application versioning,and application instru-mentation.4 Developerteams requently worktogether through theirbrowsers to lever-age the virtual cloud

platorm. Virtualservers running in thecloud can include webservers, applicationsservers, and database engines. For some ofer-ings, application programming interaces (APIs)are provided to pre-dened network-based unc-tions. ProgrammableWeb.com lists over 600 APIson the Internet in 2008, with Google Maps, Flickr,Amazon, and Youube capturing the greatest mar-ket share o calls.5 Platorm oferings are generallyassumed to be a part o a multi-tenant architecture

in which many unrelated organizations may besupported by the same platorm inrastructure.Platorms can scale by adding processing and stor-age resources to dynamically support growth in theoperational demands or a particular customersweb application. An example o a platorm oferingis Force.com, which began as a soware applica-tion provider supporting SalesForce.com. APIs anddevelopment tools to support the SalesForce appli-cation became more general platorm tools or anycustomer ofering Internet-based soware.

Cloud ServicesComponents as a serviceTislayer o the cloud computing stack includes thedenition o soware components, run in a dis-tributed ashion, across the commercial Internet.Tis denition is most like SOA, which is discussedbelow, with dened service interaces as a basis orsystem-to-system integration.

The computing

stack, from the

applications

we write, to the

platforms webuild upon, to

the operating

systems we

use, are now

moving from a

product- to a

service-based

economy. Simon Wardley2
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


9/20


Cloud ApplicationsSofware as a service(SaaS)Tis denition relies on the cloud oraccess to what would traditionally be local desktopsoware.6 For example, Adobes Photoshop, a pro-gram to manipulate images, was distributed to endusers on disks or many years. oday, you still caninstall a version o Photoshop rom an installationdisk, or you can go to a completely online version o

an analogous application, entitled Express.7 In theonline Express, you can upload your images intoa hosted le area and work on the images with thesame lters and capabilities that were ound in thetraditional soware version. Express is an exampleo SaaS, though this is not the only orm SaaS cantake. For example, Google provides web applica-tions, such as Gmail, Google Calendar, alk, Docs,and Sites, with unctionality similar to traditionalo ce suites.

One advantage o this approach is that the applica-

tion can be continuously updated by the applicationprovider without issuing and shipping new instal-lation disks. Each time the user logs in to the site,the user will get the latest version o the applica-tion. Te application provider is also ofering avery scalable web application using a multi-tieredweb architecture, implemented on a considerableinrastructure. Disadvantages include the completedependence on the underlying network to accessthe application. When the network is down, theuser cannot do any work with the network-basedapplication. In contrast, the desktop version o thesoware does not require network connectivity orproductive work.

Sofware as a Service (SaaS) is a model o sofwaredeployment where an application is hosted as aservice provided to customers across the Internet.By eliminating the need to install and run theapplication on the customers own computer,SaaS alleviates the customers burden o sofwaremaintenance, ongoing operation, and support.Conversely, customers relinquish control oversofware versions or changing requirements; more-

over, costs to use the service become a continuousexpense, rather than a single expense at time o

purchase.Wikipedia (SaaS)8

With SaaS a signicant amount o the processingoccurs in the Internet cloud, in remote data cen-ters, and not on the local desktop. Te local desktopbecomes primarily a presentation layer device in this

scenario. By using many online soware applica-tions, the user is distributing processing on theirbehal across CPUs scattered in the cloud by so-ware service oferors. For example, Wikipedia states,[Cloud computing] is a style o computing in whichI-related capabilities are provided as a service,allowing users to access technology-enabled servicesrom the Internet (in the cloud) without knowledge

o, expertise with, or control over the technologyinrastructure that supports them. 9

Cloud ClientsAnother application-related unc-tion o cloud computing ocuses on the distribu-tion o business and personal data across serverson the Internet. For example, an individual mayhave personal data in Facebook, digital photos inFlickr, banking data in bank servers, insurancedata in insurance company servers, and on and on,all available in distributed servers and data centersaround the world. In composite, these users are

using the cloud to hold and maintain data onmany aspects o daily lie. Tis distribution o dataacross the Internet rather than in local desktop orlocal area network repositories resonates with endusers because it oen equates directly to the useo presentation layer Cloud Applications in CloudClients such as a browser, the top o the cloud stack.Forrester Research states, Consumers are drivingthis new battle, with the huge volume o serversneeded to dish up search, pictures, audio, and video,in addition to web email. Tis giant capacity createsa massive platorm or leading consumer-ocused

companies such as Amazon, Facebook, Google, andMicroso, which then look or ways to add incre-mental volume by servicing the needs o institutionsas well. 10

Figure 2 depicts a sampling o current commer-cial vendors with cloud computing oferings. Teoferings all into the same general groupings as thecloud I stack described earlier, with oundationalservices on the le and more complex serviceson the right. Please note that this marketplace isdynamic and continues to grow rapidly.

Considerations with cloud computingCloudcomputing brings with it a number o key benetsand risks that should be examined by any seniorleadership team considering a realignment o itsenterprise computing I portolio.

Outsourcing to cloud providers: Commercialcloud computing efectively outsources portions
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


10/20


o the I stack, ranging rom hardware throughapplications, to cloud providers. Cloud com-puting allows a consumer to benet by incre-mentally leveraging a more signicant capitalinvestment made by a provider. Te consumersalso benet signicantly by being able to dynam-ically scale their demand o the cloud services.

As ed Schadler states, Te service providerpricing model o cloud computing is particularlyvaluable when economic uncertainty limits thecapital and I resources available to rms. 12

Dependence on the network: Cloud computing isundamentally dependent on the network to con-nect the oferor with the consumer. For those whohave redundant network connections with robustbandwidth this will not be an issue, but or thosewho dont, serious consideration should be givenconcerning singular dependence on network-based oferings, and how business continues when

the network is unavailable or unreliable. Dependence on specifc cloud providers (lock-

in): Vendor lock-in is a risk with the currentmaturity o cloud computing. Vendor neutralityis oen best achieved by utilizing industry oropen standards, but these standards are cur-rently evolving or several layers o the stack.Developing applications to leverage one cloud

providers oferings can lead to lock-in with onevendors solution and limited or no competition.

Contracts and service-level agreements (SLAs):Cloud oferings are dened with a discrete inter-ace and perormance expectation. Tis agree-ment can be captured in an SLA between theprovider and consumer, and this document can

be made a part o the contractual relationshipbetween the two.

IA: Commercial cloud providers will have secu-rity solutions that meet the needs, risk proles,and cost models o their commercial custom-ers. Tese security solutions will not always beappropriate or Federal needs. Part o the beneto cloud computing as a consumer is being ableto abstract away the details o how a platormor service is provided. Federal consumers mayoen need a clear understanding o (and needto speciy the characteristics o) what is occur-

ring inside the black box o a cloud ofering toensure secure operations.

Defining SOA

SOA builds on computer engineering approacheso the past to ofer an architectural approach orenterprise systems, oriented around the ofering o

Figure 2. Example Cloud Computing Vendors11
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


11/20


services on a network oconsumers. A ocus o thisservice-oriented approach ison the denition o serviceinteraces and predictableservice behaviors. A set oindustry standards, collec-tively labeled Web Service

standards in this paper,provide and implement thegeneral SOA concept andhave become the predomi-nant set o practical toolsused by enterprise engineersor current SOA projects.Some Web Service stan-dards have become oun-dational and more widelyadopted, while many arestill seeking broad industryor Government acceptance.

SOA, as implementedthrough the common WebServices standards, ofersFederal senior leadership

teams a path orward, given the diverse and com-plex I portolio that they have inherited, allowingor incremental and ocused improvement o theirI support systems. With thoughtul engineeringand an enterprise point o view, SOA ofers positivebenets such as:

Language-neutral integration: Te ounda-tional contemporary Web Services standards useeXtensible Markup Language, which is ocusedon the creation and consumption o delimitedtext. Regardless o the development languageused, these systems can ofer and invoke servicesthrough a common mechanism. Programminglanguage neutrality is a key diferentiator rompast integration approaches.

Component reuse: Given current Web Servicetechnology, once an organization has built a

soware component and ofered it as a service,the rest o the organization can then utilize thatservice. With proper service governance, empha-sizing topics such as service provider trust,service security, and reliability, Web Servicesofer the potential or aiding the more efectivemanagement o an enterprise portolio, allowinga capability to be built well once and then shared.

Multiple components can be combined to ofergreater capabilities in what is oen termedorchestration.

Organizational agility:SOA denes buildingblocks o soware capa-bility in terms o oferedservices that meet some

portion o the organi-zations requirements.Tese building blocks,once dened and reliably operated, can berecombined and integrated rapidly.

Leveraging existing systems: One common useo SOA is to dene elements or unctions o exist-ing application systems and make them availableto the enterprise in a standard agreed-upon way,leveraging the substantial investment alreadymade in existing applications. Te most compel-ling business case or SOA is oen made regard-ing leveraging this legacy investment, enablingintegration between new and old systemscomponents.

SOA and its implementing standards, such as theWeb Services standards, come to us at a particu-lar point in computing history. While several keyimprovements, such as language neutrality, difer-entiate todays Web Service technologies, there hasbeen a long history o integrating technologies withqualities analogous to Web Services, including aeld o study oen reerred to as enterprise applica-

tion integration (EAI).13

One o the key trends driving the adoption o WebServices is the increasing span o integration beingattempted in organizations today. Systems integra-tion is increasing both in complexity within organi-zations and across external organizations. We canexpect this trend to continue as we combine greaternumbers o data sources to provide higher valueinormation. Ronan Bradley writes, CIOs oen havedi culty in justiying the substantial costs associ-ated with integration but, nevertheless, in order to

deliver compelling solutions to customers or improveoperational e ciency, sooner or later an organizationis aced with an integration challenge. 14 Figure 3depicts a ew waypoints in the trend toward increas-ing systems integration complexity.

SOA attempts to streamline integration across sys-tems by providing components that are architectedand described in a consistent ashion.

After creating

islands of

automation

through

generationsof technology,

users and

business

managers are

demanding

that seamless

bridges be built

to join them. David Linthicum8
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


12/20


Considerations with SOALike cloud comput-ing, SOA brings with it a number o key benets andrisks, including:

Dependence on the network: SOA is undamen-tally dependent on the network to connect theservice provider with the consumer. For exam-ple, Web Service protocols ride on Internet pro-

tocols to invoke soware unctions distributedacross the network. Poorly perorming networkscan make a large impact on the availability oWeb Services to the consumer.

Provider costs: Creating a generic reusable so-ware component or a broad audience takes moreresources (20 percent to 100 percent more) thancreating a less generic point solution.15 Te costo reuse, thereore, shis to the service providers,which benets the consumers.

Enterprise standards: When many componentsare being simultaneously developed by indi-

vidual teams, it becomes critical or the interaceo a providers service to match up to the call oa consumer. Similarly, it helps everyone involvedi the interaces across services have somecommonality in structure and security accessmechanisms. Choosing and communicating acomprehensive set o enterprise standards is aresponsible approach to aid in enterprise SOAintegration.

Agility: When we discuss agility as it relatesto SOA, we are oen reerring to organizationalagility, or the ability to more rapidly adapt aFederal organizations tools to meet their currentrequirements. An organizations requirementso I might change over time or a number oreasons, including changes in the business ormission, changes in organizational reporting

requirements, changes in the law, new technolo-gies in the commercial marketplace, attemptsto combine diverse data sources to improve theorganizations operational picture, and manyother reasons. Te larger promise o an enter-prise SOA is that once a su cient quantityo legacy-wrapped components exist, and areaccessible on the internet protocol (IP) wide areanetwork (WAN), they can be reassembled morerapidly to solve new problems.

Comparing Cloud Computing and SOACloud computing and SOA have important over-lapping concerns and common considerations, asshown in Figure 4. Te most important overlapoccurs near the top o the cloud computing stack,in the area o Cloud Services, which are network-accessible application components and sowareservices, such as contemporary Web Services. (Seethe notional cloud stack in Figure 1.)

Figure 3. Integration is Increasing in Scope and Complexity.

Digitization Age Integration Age

NumberofSystemsInvolved

Span of Attempted Integration

Fewer

Many

Smaller Larger

1 Tier 2 Tier Multi-tiered

IPLAN

HUB

IP

IP

IP

Intel 8088Client/Server

Web Enabled

EAI withIntegration

Hub

EnterpriseSOA

CrossEnterprise

SOA
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


13/20


Both cloud computing and SOA share concepts oservice orientation.16 Services o many types areavailable on a common network or use by consum-ers. Cloud computing ocuses on turning aspectso the I computing stack into commodities17 that

can be purchased incrementally rom the cloud-based providers and can be considered a type ooutsourcing in many cases. For example, large-scaleonline storage can be procured and automaticallyallocated in terabyte units rom the cloud. Similarly,a platorm to operate web-based applications canbe rented rom redundant data centers in the cloud.However, cloud computing is currently a broaderterm than SOA and covers the entire stack romhardware through the presentation layer sowaresystems. SOA, though not restricted conceptuallyto soware, is oen implemented in practice ascomponents or soware services, as exemplied bythe Web Service standards used in many implemen-tations. Tese components can be tied together andexecuted on many platorms across the network toprovide a business unction.

Network dependenceBoth cloud computing andSOA count on a robust network to connect consum-ers and producers, and in that sense, both have thesame oundational structural weakness when thenetwork is not perorming or is unavailable. JohnNaughton elaborates on this concern when he writes

that with gigabit ethernet connections in local areanetworks, and increasingly ast broadband, networkperormance has improved to the point where cloudcomputing looks like a easible proposition .... I weare betting our utures on the network being thecomputer, we ought to be sure that it can stand thestrain. 18

Forms o outsourcingBoth concepts requireorms o contractual relationships and trust betweenservice providers and service consumers. Reuse oan SOA service by a group o other systems is inefect an outsourcing o that capability to another

organization. With cloud computing, the outsourc-ing is more overt and oen has a ully commercialavor. Storage, platorms, and servers are rentedrom commercial providers who have economies oscale in providing those commodities to a very largeaudience. Cloud computing allows the consumerorganization to leave the detailed I administrationissues to the service providers.

StandardsBoth cloud computing and SOAprovide an organization with an opportunity toselect common standards or network accessible

capabilities. SOA has a airly mature set o stan-dards with which to implement soware services,such as Representational State ranser (RES),SOAP,19 and Web Services Description Language(WSDL), among many others. Cloud computing isnot as mature, and many o the interaces ofered areunique to a particular vendor, thus raising the risko vendor lock-in. Simon Wardley writes, Te abil-ity to switch between providers overcomes the larg-est concerns o using such service providers, the lacko second sourcing options and the ear o vendorlock-in (and the subsequent weaknesses in strategic

control and lack o pricing competition). 20 Tis islikely to change over time as oferings at each layerin the stack become more homogenous. Wardleycontinues, Te computing stack, rom the applica-tions we write, to the platorms we build upon, tothe operating systems we use are now moving roma product- to a service-based economy. Te shitowards services will also lead to standardization

Figure 4. Overlapping Concepts for Cloud Computing and SOA Implementations
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


14/20


o lower orders o the computing stack to internetprovided components. 21

Summary: A dierence in emphasisWhile thereare important overlaps between cloud computingand SOA, they have a diferent emphasis, resultingrom their original ocus on diferent problem sets.SOA implementations are undamentally enterprise

integration technologies or exchanging inorma-tion between systems o systems. SOA ocuses onthe problem o making systems integration moree cient, and i systems integration as a trendcontinues to increase as described, e ciency in thistask will become increasingly important to Federalleadership teams. SOA implementation technolo-gies, such as the group o Web Service standards,allow a consumer soware application to invokeservices across a common network. Further, theyallow integration across a variety o developmentlanguages and platorms, providing a language-

neutral soware layer. A key benet o enterpriseSOA eforts is the ability to make system-to-systeminteraces consistent in the enterprise architecture,thus saving resources on uture integration andhopeully improving the speed at which integrationcan occuror organizational agility. Te empha-sis o cloud computing is to leverage the networkto outsource I unctions across the entire stack.While this can include soware services as in anSOA, it goes much urther. Cloud computing allowsthe marketplace to ofer many I unctions as com-modities, thus lowering the cost to consumers when

compared to operating them internally. John Foleydescribes cloud computing as on-demand accessto virtualized I resources that are housed outsideo your own data center, shared by others, simpleto use, paid or via subscription, and accessed overthe Web. 22 Tereore, while the two concepts sharemany common characteristics, they are not synony-mous and can be pursued either independently or asconcurrent activities.

Can SOA Be Skipped for Cloud Computing?SOA and cloud computing are complementaryactivities, and both will play important roles in Iplanning or senior leadership teams or years tocome. Cloud computing and SOA can be pursuedindependently, or concurrently, where cloud com-putings platorm and storage service oferings canprovide a value-added underpinning or SOA eforts.

Requirements unique to Federal organizations willdetermine the depth to which they can employwholly commercial solutions, commercial-of-the-shel products used to implement SOA serviceportolios or cloud service providers on the publicInternet. Regardless, the network-based conceptsinherent in each will shape thinking about the archi-tecture and economies o scale o large enterprise I

solutions, even when the Government nds it needsto create its own versions or policy, privacy, topol-ogy, or security reasons.

Enterprise application integration continuesCloud computing does not replace SOA, or the useo distributed soware components, as an integra-tion technology. Te need to support broader andmore consistent integrationo systems will continue.Te trend by leadershipteams to consider I capa-

bilities as a commodity willcontinue to put downwardpressure on I budgets and,consequently, integrationand data exchange will haveto get more streamlined ande cient, across a portolioo disparate systems. SOA-inspired componentizationeforts, where sowareleverages other network-based soware, are a

response to this pressure.

Cloud computing and SOAare not synonymous, though they share many char-acteristics. Solving one does not complete the other.For example, consistently integrating your sowaresystems as distributed components or services(SOA) will not inherently virtualize your hardware,or outsource your presentation layer to a third-party provider (cloud computing). Accomplishingsuccessul outsourcing o commodity I unc-tions (cloud computing) does not integrate systems

custom to your business, or aggregate data into asingle display mash-up (SOA). While SOA andcloud computing share many o the same concerns,considering all the layers o the I support stack willrequire coordinating multiple dependent eforts.

In summary, both cloud computing and SOA cansupport good engineering practices by enablingundamental concepts such as abstraction, loose

Cloud

computing doesnot replace

SOA, or the use

of distributed

software

components, as

an integration

technology.
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


15/20


coupling, and encapsulation. Both approachesrely on the denition o clear and unambiguousinteraces, predictable perormance and behavior,interace standards selection, and clear separationso unctionality. Finally, cloud computing and SOAcan be pursued independently, or concurrently ascomplementary activities.

How Can the DoD Take Advantage of CloudComputing?

Te cloud computing capabilities discussed herehave many potential benets or DoD and Federalagencies, and while it will be tempting to imme-diately use public Internet-based commercialresources, the existing commercial marketplaceservice providers will present a challenge or themajority o the DoD or the ollowing reasons:

Inormation assurance: Part o the benet ocloud computing as a consumer is being able toabstract onesel away rom the details o howa platorm or service is provided. Tis abstrac-tion can include not knowing where ones datais actually being kept, including how many datacenters are involved and which national bordersthese data centers all in. Security consider-ations go beyond the actual location o the data.Commercial cloud providers will have securitysolutions that meet the needs and cost mod-els o their commercial customers, and these

approaches can be insu cient or direct con-nection to classied DoD networks according tocurrent policies.

Survivability: While commercial rms andthe DoD share many similar general businesscontinuity concerns, there comes a point wherecommercial and Government requirements orsurvivability diverge. Te DoD will require acomprehensive understanding o the redundancyo cloud inrastructure that will go beyond thedue diligence o most commercial rms. Eitherdriven by policy or law, the DoD will need tospeciy architecture details usually within theoferors purview, and not specied by the typicalcommercial consumer.

Chaining o outsourcing: Many o the cloudproviders outsource inrastructure layers beneaththe service they are providing. For example,a service provider may use a platorm rom

another commercial organization. While theimmediate provider may endeavor to meet DoDrequirements, the outsourced provider may not.

Given that contemporary, wholly commercialinstances o cloud providers may not currently meetall o DoDs mission-critical needs, it is also possibleor DoD to take benecial cloud concepts and apply

them internally on their own sensitive or classiednetworks. However, establishing a cloud comput-ing inrastructure is not a small undertaking, as itrequires that analogous instances o the commercialcapabilities be established on the internal networkso the DoD. Cloud oferings are undamentallynetwork-based oferings and thereore must be pres-ent on the same network-addressable space as theDoD consumers. For example, or a cloud oferingto be available on NIPRnet, it must be addressablethrough CP/IP in the network address space o theNIPRnet. In this sense, each network address space

is an island and will need its own cloud capabilities.

Te approach o providing DoD-homed cloudservices can be considered individually at each layerin the cloud stack. For example, DoD could decideto leverage economies o scale by ofering highlyvirtualized servers and secure storage on a grandscale. Individual DoD programs that require thesesurvivable multi-data-centered cloud I resourcescould choose to use thesestandard cloud platormsinstead o dening and

procuring custom serversolutions and operatingthem in separate data cen-ters with additional conti-nuity o operations solu-tions. Examples o potentialDoD cloud oferings canbe ound in each layer othe stack, ranging rominrastructure and stor-age to platorms, services,and soware as a service.

Just as in the commercialmarketplace, the key tointroducing these oferingsto DoD programs is under-standing how they addvalue to senior leadershipteams controlling DoD Iportolios.

Examples of

potential DoD

cloud offerings

can be found

in each layer of

the cloud stack,

ranging from

infrastructure

and storageto platforms,

services, and

software as

a service.
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


16/20


Introducing cloud computing to DoDA potentialprocess or establishing a cloud computing inrastruc-ture in DoD includes the ollowing broad steps:

Determine DoDs initial cloud oerings: Tisis an engineering efort that would examine thecloud computing commercial marketplace, thecloud computing stack, and compare them to

the needs o select DoD programs. Te require-ments o the DoD I programs and the oferingsin the marketplace are both moving targets,and this adds a challenge to the analysis, ascloud computing is evolving rapidly. Still, thisanalysis would provide a valuable comparison todetermine the scope o the application o cloudcomputing or real DoD programs. Part o thisanalysis would be to assess the applicability ocloud computing to areas o the DoD wherenetwork characteristics may hamper receivingull benet rom contemporary network-based

cloud oferings. Similarly, solutions with overlap-ping combinations o locally accessible oferingsand WAN-accessible cloud oferings should beconsidered.Te cloud computing engineering analysisshould make a special efort to determine whereindustry or open standards can be used ineach layer in the cloud stack. For example, theDistributed Management ask Force, whosemembers include Dell, EMC, Hewlett-Packard,IBM, Intel, Microso, Sun, and VMware, hasbeen working on a standard or virtual servers,known as Open Virtualization Format (OVF), aspart o its work to enable management interop-erability among multi-vendor systems, tools,and solutions.23 OVF creates a standard way topackage and distribute virtual machines.24 Tis isan example o an upcoming open standard thatwould be important in the Cloud Inrastructurelayer. One goal or the use o standards like thisis to avoid vendor lock-in in the cloud oferings.

Choose pilots or each layer o the stack: In thisstep, the DoD would select key cloud oferings to

pilot on its internal networks. Te concept is toapply commercial approaches and technologiescooperatively with industry and exercise theseoferings in a realistic sensitive or classied envi-ronment, recognizing clouds inherent depen-dence on the underlying network. Te DoD hasearly cloud eforts already underway, such asDISAs Rapid Access Computing Environment

initiative, which provides Platorm as a Serviceunctions.25 From the point o view o an inte-grated master schedule, it would be helpul toorganize oferings lower in the stack, such asplatorm computing oferings or storage utilitycomputing, to be available rst, so that higherlevels o the stack, such as services, could makelater use o them.

Te pilots should rely on the active participa-tion o industry. Cloud computing initiativesin industry are likely to be years ahead o theGovernment or the near term, and DoD wouldbenet rom an open dialogue on commercialarchitectures and approaches as cloud comput-ing evolves.

Analyze the value o the cloud pilots: In thisstep the initial results o DoD-ocused cloudcomputing as demonstrated by the pilots onDoD networks would be examined. Lessonslearned in the pilots would be analyzed, anddeterminations o the value o the cloud oferingsto DoD I leadership teams rankly assessed.echnical and programmatic risks with cloudtechnologies would also be reexamined.

Determine i pilots should be made opera-tional: Here the cloud oferings would be consid-ered or broader implementation across a greaterrange o programs. Since the network is essen-tial to the cloud, a network analysis would beconsidered or a wider range o cloud customers.A cost/benet analysis would be perormed to

determine i the expansion o the cloud oferingwas advantageous.

AcquisitionAcquisition activities will be centralto piloting and possibly expanding the use o cloudtechnology. Te DoD will have to make some keytrade-of decisions regarding how the cloud servicesare procured. For example, will the DoD procurethe oferings as turnkey solutions where the vendorprovides all aspects o the ofering as a managedservice provider with dened SLAs, or will the DoDown and operate the inrastructure with labor and

expertise provided by vendors, more in the orm o asystem integrators subject matter experts? Will theDoD or the vendor capitalize and own the inra-structure? Will this efort be separately unded orunded by programs that will leverage the cloud?Tese types o strategic decisions will be part o anoverall acquisition strategy or the DoD that mustbalance costs, program risks, and long-term goals.
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


17/20


References

1 Adapted rom Sam Johnston, axonomy: Te 6 Layer Cloud Computing Stack,http://samj.net/2008/09/taxonomy-6-layer-cloud-computing-stack.htmland Frank E. Gillett, Future View: Te New ech Ecosystem o Cloud, Cloud Services, and Cloud Computing,Vendor Strategy Proessionals, Forrester Research

2 Simon Wardley, Cloud Recap Te Cloud odayhttp://blog.gardeviance.org/2008/10/cloud-recap.html

3 Amazon.com, Amazon Simple Storage Service (Amazon S3)http://aws.amazon.com/s3/

4 Wikipedia, Platorm as a servicehttp://en.wikipedia.org/wiki/Platorm_as_a_service

5 John Musser, 600 Web APIshttp://blog.programmableweb.com/2008/01/14/600-web-apis/

6 Robert P. Desisto et al., utorial or Understanding the Relationship Between Cloud Computing and SaaShttp://www.gartner.com/DisplayDocument?re=g_search&id=640707

7 Adobe Photoshop Expresshttps://www.photoshop.com/express/landing.html

8 Wikipedia, Soware as a servicehttp://en.wikipedia.org/wiki/Soware_as_a_Service

9 Wikipedia, Cloud computing

http://en.wikipedia.org/wiki/Cloud_computing

10 Frank E. Gillett, Future View: Te New ech Ecosystems o Cloud, Cloud Services, and Cloud Computing,Vendor Strategy Proessionals, Forrester Research

11 Neal Leavitt, Yankee Group, Is Cloud Computing Really Ready or Prime ime, IEEE Computer Society, January 2009

12 ed Schadler, Forrester Research, alking to Your CFO about Cloud Computing

13 David Linthicum, Enterprise Application Integration

http://saari.oreilly.com/0201615835 12 November 199914 GDS InoCentre, Roman Bradley, Agile Inrastructures

http://gdsinternational.com/inocentre/artsum.asp?mag=184&iss=150&art=25901&lang=en 28 March 2008

15 Jefery Poulin, Te ROI o SOA Relative to raditional Component Reuse, Logic Library, 2006

16 Kevin Jackson, Cloud Computing Related echnologies and their Use in the Public Sector to Support Net-centric Operationhttp://kevinljackson.blogspot.com/2008/09/6-layers-o-cloud-computing-stack.html

17 Bernard Lunn, Te New Stack: SaaS, Cloud Computing, Core echnologyhttp://www.readwriteweb.com/archives/new_technology_stack.php

18 John Naughton, Holes in the net make cloud computing pie in the skyhttp://www.guardian.co.uk/technology/2008/mar/02/security.internetphonesbroadband

19 Note that SOAP is no longer considered an acronym. For more inormation, seehttp://www.w3.org/R/2003/REC-soap12-part0-20030624/#L1153

20 Simon Wardley, Cloud Recap Te Cloud odayhttp://blog.gardeviance.org/2008/10/cloud-recap.html

21 Simon Wardley, Te Key to Cloud Computing: Componentizationhttp://xml.sys-con.com/node/773522
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


18/20

22 John Foley, A Denition o Cloud Computing,

http://www.inormationweek.com/cloud-computing/blog archives/2008/09/a_denition_o.html

23 Distributed Management ask Force, Inc., DMF Member Listhttp://www.dmt.org/about/list

24 VWware, Inc., Open Virtualization Formathttp://www.vmware.com/appliances/learn/ov.html

25 Joseph Brygider, DISA Corporate Communications, DISAS RACE to the Clouds

http://www.disa.mil/news/stories/cloud_computing.html

http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


19/20

MITREwww.mitre.org

2009 Te MIRE CorporationAll Rights Reserved

Approved or Public ReleaseDistribution UnlimitedCase Number: 09-0743

Document Number: MR090026
http://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soahttp://www.mitre.org/soa


20/20

mitre cloud soa

Documents