watitis2012: the service oriented enterprise (soe) [cpbell]

”The Cloud”What is a Service?

Building the Services Oriented Enterprise (SOE)

The Service Oriented Enterprise (SOE)

Colin Bell

University of Waterloo, IST Information Security Services

December 4, 2012

Colin Bell The Service Oriented Enterprise (SOE)



Table of contents

1 ”The Cloud”Types of Cloud ServicesDeployment of CloudsWhy Cloud?

2 What is a Service?DefinitionsPractical DefinitionGraphical Representation

3 Building the Services Oriented Enterprise (SOE)Service Management w/ ITILEnterprise Architecture (EA)

Zachman Framework for Enterprise Architecture

Service-Oriented Architectures (SOA)




Types of Cloud ServicesDeployment of CloudsWhy Cloud?

Definition: Cloud Computing

Cloud computing is the use of computing resources(hardware and software) that are delivered as a serviceover a network (typically the Internet). The name comesfrom the use of a cloud-shaped symbol as an abstractionfor the complex infrastructure it contains in systemdiagrams. Cloud computing entrusts remote services witha user’s data, software and computation.

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


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




Image: Cloud ComputingSource: http://upload.wikimedia.org/wikipedia/commons/b/b5/Cloud_computing.svg


http://upload.wikimedia.org/wikipedia/commons/b/b5/Cloud_computing.svg




Types of Cloud Services

Software as a Service (SaaS)

Platform as a Service (PaaS)

Infrastructure as a Service (IaaS)





SaaS - Software (Application) as a Service

Software (Application) as a Service (SaaS):

providers install and operate application software,very little flexibility, you get what is provided, and;users do not worry about the underlying platform orinfrastructure.

Examples:

GMail / Google AppsHotmail / Microsoft Office 365Salesforce





PaaS - Platform as a Service

Platform as a Service (PaaS):

provides users with an infrastructure pre-configured with asuite of tools,often users are locked into a particular development suite,database, and Web server, and;users can build and run software in a controlled environment.

Examples:

Google App EngineEngine YardWindows Azure Compute





IaaS - Platform as a Service

Infrastructure as a Service (IaaS):

low-level access to basic computing components,can choose own OS, software stack, and configuration settings,and;clients are given their own virtual networks and data centre.

Examples:

Amazon AWSRackspace CloudJoyent





Economies of Scale Benefits

SaaS >PaaS >IaaSWhy?

Less Complexity + Fewer Features=⇒ Increased Specialization (decreasing per-unit cost)=⇒ Increased benefits from Economies of Scale





Deployment of Clouds

Public Cloud Infrastructure that is owned by a corporation whosells their services to the general public.

Community Cloud Infrastructure that is shared amongstlike-entities. Municipalities, Governments, non-ProfitOrganizations, and Non-Governmental Organizationsoften share these services.

Private Cloud Infrastructure that is operated solely for a singleentity.

Hybrid Cloud A composition of two or more clouds that areseparate at the lowest Infrastructure levels whileallowing interconnection at higher levels.





Value Generation (Impact++) vs. Cost

By increasing the number of customers and improvingspecialization, the cost of production (of services) can bedriven down.

Economies of scale is kicking in.

When someone else can provide service for less, do weconsider the Opportunity Cost?

Is maintaining the status quo a good idea?

What ’higher value’ things could we be doing to make theorganization more productive?





1994: Wentworth Research Program

Source: George Cox, Time to Reshape the IS Department? Wentworth Research Program (now part of Gartner

EXP, Stamford, CT), June 1994.




DefinitionsPractical DefinitionGraphical Representation

What is a Service?

Basic Definition Inputs + Functionality = Output

Formal Definition See: Journal of Software, July 2006 >AliakseiYanchuk, Alexander Ivanyukovich, Maurizio Marchese”Towards a Mathematical Foundation forService-Oriented Applications Design”





What is a Service?

Practical Definition ...

Inputs = (effort, data, contract, connection)Functionality (unknown to user)Output = (results)





What is a Service?




Service Management w/ ITILEnterprise Architecture (EA)Service-Oriented Architectures (SOA)

What is a Services Oriented Enterprise?

Based on OASIS SOA Reference Model 1.0:

A Services Oriented Enterprise (SOE) is anorganization whose business and IT are converged basedon the enterprise business service model to gain businessgoals in the most efficient way in the given market.

https://www.oasis-open.org/committees/soa-rm/





Information Technology Infrastructure Library (ITIL)

Service Strategy provides guidance on clarification andprioritization of service-provider investments inservices.

Service Design provides good-practice guidance on the design ofIT services, processes, and other aspects of theservice management effort.

Service Transition relates to the delivery of services required by abusiness into live/operational use, and oftenencompasses the ”project” side of IT rather than.

Quotes From: http://en.wikipedia.org/wiki/Information_

Technology_Infrastructure_Library


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





Information Technology Infrastructure Library (ITIL)

Service Operation aims to provide leading practice for achievingthe delivery of agreed levels of services both toend-users and the customers (where ”customers”refer to those individuals who pay for the service andnegotiate the Service Level Agreements (SLAs).

Continual Service Improvement aims to align and realign ITservices to changing business needs by identifyingand implementing improvements to the IT servicesthat support the business processes.

Quotes From: http://en.wikipedia.org/wiki/Information_

Technology_Infrastructure_Library







Enterprise Architecture (EA)

Gartner:Enterprise architecture (EA) is a discipline for

proactively and holistically leading enterprise responses todisruptive forces by identifying and analyzing theexecution of change toward desired business vision andoutcomes. EA delivers value by presenting business andIT leaders with signature-ready recommendations foradjusting policies and projects to achieve target businessoutcomes that capitalize on relevant business disruptions.EA is used to steer decision making toward the evolutionof the future state architecture.

Source: http://www.gartner.com/it-glossary/

enterprise-architecture-ea/


http://www.gartner.com/it-glossary/enterprise-architecture-ea/

http://www.gartner.com/it-glossary/enterprise-architecture-ea/




Enterprise Architecture (EA)

Human readable:Enterprise architecture (EA) is a discipline for

taking a structured approach to studying, documenting,designing, planning, and facilitating change within anorganization. The goal of EA is to allow an enterprise tobetter identify high-value opportunities and help iteffectively capitalize on them.






Zachman Columns:

”What” Things + Data

”How” Processes

”Where” Network

”Who” People

”When” Events + Times

”Why” Strategies +Motivations

Zachman Rows:

”Contextual” Planner /Enterprise View

”Conceptual” Owner / BusinessView

”Logical” Designer /Architect View

”Physical” Builder / EngineerView

”Detailed” Sub-contractor /Technician View

”Functional” Operator View






Why How What Who Where When

Contextual

(Enterprise) Goal List Process List Material List Organizational Unit & Role List

Geographical Locations List Event List

Conceptual(Business)

Goal Relationship Process Model

Entity Relationship

Model

Organizational Unit & Role Relationship

ModelLocations Model Event Model

Logical(Architect) Rules Diagram Process

DiagramData Model

DiagramRole

Relationship Diagram

Locations Diagram Event Diagram

Physical(Engineer)

Rules Speci cation

Process Function

Speci cationData Entity Role

Speci cationLocation

Speci cationEvent

Speci cation

Detailed(Technician) Rules Details Process Details Data Details Role Details Location Details Event Details





Service-Oriented Architectures (SOA)

In software engineering, a service-orientedarchitecture (SOA) is a set of principles andmethodologies for designing and developing software inthe form of interoperable services. These services arewell-defined business functionalities that are built assoftware components (discrete pieces of code and/ordata structures) that can be reused for differentpurposes. SOA design principles are used during thephases of systems development and integration.”

Source: http://en.wikipedia.org/wiki/Service-oriented architecture





SOA Principles: Quick + Dirty

loosely couple at all costs

never require a particular operating system or technology

keep services unassociated until runtime

do not allow any embedded links between services

only communicate over documented channels

only communicate through documented interfaces

to build on top of other services (compose) at quality and tospec, SLA underpinning contracts (UCs) are required





SOA Principles: Thomas Erl View

From: http://www.soaposters.com/

Standardized Service Contract Services within the same serviceinventory are in compliance with the same contractdesign standards.

Service Loose Coupling Service contracts impose low consumercoupling requirements and are themselves decoupledfrom their surrounding environment.

Service Abstraction Service contracts only contain essentialinformation and information about services is limitedto what is published in service contracts.







Service Reusability Services contain and express agnostic logic andcan be positioned as reusable enterprise resources.

Service Autonomy Services exercise a high level of control overtheir underlying runtime execution environment.

Service Statelessness Services minimize resource consumption bydeferring the management of state information whennecessary.







Service Discoverability Services are supplemented withcommunicative meta data by which they can beeffectively discovered and interpreted.

Service Composability Services are effective compositionparticipants, regardless of the size and complexity ofthe composition.





Why SOA? Ask Stevey!

Case: Amazon vs. GoogleSteve Yegge’s ”Stevey’s Google Platforms Rant”

Engineer at Google released a rant on Google+ around Oct2011.

A user error with Google+ led to a Google employee posting arant against Google.

He had worked at Amazon before Google and ranted aboutwhere Google was failing.






In 2002, Jeff Bezos (founder + CEO of Amazon) issued amandate.

1 All teams will henceforth expose their data and functionalitythrough service interfaces.

2 Teams must communicate with each other through theseinterfaces

3 There will be no other form of interprocess communicationallowed: no direct linking, no direct reads of another team’sdata store, no shared-memory model, no back-doorswhatsoever. The only communication allowed is via serviceinterface calls over the network.






1 It doesn’t matter what technology they use. HTTP, Corba,Pubsub, custom protocols – doesn’t matter. Bezos doesn’tcare.

2 All service interfaces, without exception, must be designedfrom the ground up to be externalizable. That is to say, theteam must plan and design to be able to expose the interfaceto developers in the outside world. No exceptions.






Lessons from a massive undertaking of building SOA at Amazon:

pager escalation can get hard. need metrics and reporting

every single one of your peer teams becomes a potentialdenial of service

monitoring and QA are the same thing in SOAs

a universal service registration mechanism is a powerful thingto have

follow-on benefits are compelling






Steve then explains... as hard as SOA was, it was the RightThing to do.

He goes on to stress that Amazon’s abilities as a provider ofInfrastructure and a Platform far outstrip Google because ofone ultimate thing:

Accessibility!

If someone should be able to access something and cannot getit through a Service, it represents a HUGE roadblock to theOrganization’s success.






Moral of the story:There is evidence that an organization is able to thrive in theirmarket after adopting an SOA mandate They were able to developmarketable value-add functionality following their adoption ofSOA. They accomplished this by imposing a requirement thateveryone always use ’Services.’ Amazon used a series of Legoblocks to combine functionality in a wide variety of ways.





Governance

From: ”IT Savvy: What Top Executives Must Know to Go from Pain to Gain” by Peter Weill and Jeanne W. Ross

We need to clarify Waterloo’s primary operating model.

Diversification Low standardization, low integration– involvesplatform of shared services that supportsautonomous business activities.

Coordination Low standardization, high integration– involvesbuilding a platform of shared data to supportintegrated management decisions or a single face tothe customer.

Replication High standardization, low integration– involvesbuilding a platform of standard technologies andbusiness processes to define a common brand.

Unification High standardization, high integration– involvesbuilding a platform of standardized technologies,business processes, and shared data to support globalend-to-end customer requirements.





Service Oriented Maturity Model

http://www.enterprise-architecture.info/EA Services-Oriented-Enterprise.htm





Looks crazy, but it’s just a series of blocks!

Image: http://collider.com





Injury Time / Q+A

Choreography of Services - the more mature we get, thebetter we dance.

Design

Design Top-Down - start from strategy / planning, work downto implementation.Design Bottom-Up - start from an existing implementation,decompose, and re-wrap it.

Service have Layers - Enterprise Service vs. Domain Servicevs. Application Service
