As presented by Scott Mattoon at Oracle Technology Network Architect Day in Phoenix, AZ on December 14, 2011.

1. <Insert Picture Here>
Making IT Simple
A Pragmatic Approach to Cloud Computing
Scott Mattoon
Principal Architect, Oracle Global Enterprise Architecture Program

2. A Pragmatic Approach to Cloud Computing
Abstract
• As organizations adopt cloud computing, they need to
define an approach that matches the combined
advantages of IT standardization, consolidation, and
self-service, with their specific business drivers. This
session outlines Oracle's Cloud Reference
Architecture and outlines fundamental considerations
to implement a cloud strategy. Methods are presented
for aligning critical architectural decisions and key
organizational transformations with cloud strategy, as
well as the important criteria to consider when
selecting cloud service providers and cloud enabling
technologies.
© 2011 Oracle Cloud Computing – Why you need Architecture 2

3. The following is intended to outline our general product
direction. It is intended for information purposes only, and
may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing
decisions. The development, release, and timing of any
features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.
© 2011 Oracle Cloud Computing – Why you need Architecture 3

4. Agenda
What are the key considerations in Cloud
architecture? Consider….
• What is your cloud ‘perspective’?
• What sort of architecture do you need?
• What is the focus of component architectures?
• What are the ‘Deployable Entities’?
• How to think about ‘refactoring’ the
organization?
© 2011 Oracle Cloud Computing – Why you need Architecture 4

5. Contrasting two approaches
This presentation emphasizes ‘integration’
- Virtualization Centric
• Has a potential of increasing
complexity over time
vs.
- Integration Centric
• Integration & architectural abstraction
offers higher performance and
greater ‘simplicity’
© 2011 Oracle Cloud Computing – Why you need Architecture 5

6. Before we get started….
What is your cloud ‘perspective’?
© 2011 Oracle Cloud Computing – Why you need Architecture 6

7. What’s your Cloud ‘Perspective’?
- Three differentiating criteria
- This perspective drives your decisions
Motivation Pure $ savings vs. Business Agility
Project
IT Dept. vs. Business
Control
Business
IT as Support vs. IT as a Business
Model
Is your cloud project ‘cutting costs’ or ‘driving business’?
© 2011 Oracle Cloud Computing – Why you need Architecture 7

8. How does ‘perspective’ affect approach?
Focus on the areas key to your initiative
Business agility
Consider the Oracle Cloud Maturity Model
• 8 domains (not all may be relevant to initiative)
• Multiple uses:
1. Framework for insight and discussion
2. Diagnostic for current environment Business
Architecture &
3. Planning tool / roadmap generator Strategy
4. Program longitudinal measurement tool
Information Organization
• Select key capabilities to focus on …
Infrastructure Governance
Operations Services
IT cost savings
© 2011 Oracle Cloud Computing – Why you need Architecture 8

9. Key Business / IT Transformations
Define your key transformations
Traditional Approach Cloud Approach
Systems and application The cloud ‘control plane’ is
management is specific to architected as a model centric
select systems & apps service
Operations developed IT will move to building up-
and performed by the IT front operational functions for
department a self-service model.
Architecture implemented Build infrastructure up-front,
up front (early binding) deploy later (late binding)
© 2011 Oracle Cloud Computing – Why you need Architecture 9

10. What sort of cloud architecture
do you need?
© 2011 Oracle Cloud Computing – Why you need Architecture 10

11. Why do I need an Architecture?
Focus on the key decisions
• “architecture encompasses the set of significant
decisions about the organization of a software system
including the selection of the structural elements and
their interfaces by which the system is composed;
behavior as specified in collaboration among those
elements; composition of these structural and behavioral
elements ……” (Krutchen, Booch, et.al.)
• “in the end, architecture boils down to whatever the
important stuff is.” (Martin Fowler)
• Architecture is key to avoiding Black Swans
© 2011 Oracle Cloud Computing – Why you need Architecture 11

12. Oracle Cloud Conceptual Architecture
Outline and group the basic elements
• Key elements
- Service model
- Management
infrastructrue
- Resources
- Roles –
Consumer,
Broker,
Auditor…
NIST conceptual architecture
© 2011 Oracle Cloud Computing – Why you need Architecture 12

13. Drill down for critical functional detail
e.g., cloud management
© 2011 Oracle Cloud Computing – Why you need Architecture 13

14. Map to technologies / products
Including standards and portability
© 2011 Oracle Cloud Computing – Why you need Architecture 14

15. Cloud Logical Architecture
Consider key relationships, abstractions…
© 2011 Oracle Cloud Computing – Why you need Architecture 15

16. Key abstractions – Making ‘IT’ Simple
Architecture concepts and Portability issues
APIs
Separation of roles Code deployment,
(e.g., Cloud Provider developer discovery and
vs Service application control
Developer)
Deployable Entities Images
(aka VDCs) include Application and data
Service Templates deployment
and Context (e.g.
‘Assemblies’)
Separation of Model
control plane Architectural models
‘cloud’ vs ‘pool’ may be external,
mgmt embedded, or internal
Logical ‘pools’
abstraction of
physical resources
Services
Data
Run time services
Access and formatting of may be absent or
data may differ significantly different
© 2011 Oracle Cloud Computing – Why you need Architecture 16

17. Hybrid Clouds – Which Kind?
Different ways to mix public and private
Lifecycle distribution It is common when ‘Hybrid’ is
Dev/test cloud - the Common one
Test mentioned to think of …
A
p • Simple Dev/test or
A p
p
p
s
A
• Complicated ‘Cloud scaling
s
Production p
p – also consider a functional
s
Development distribution hybrid architecture
Private Cloud Public Cloud
Workload distribution Functional distribution
‘Cloudbursting’ - the Hard one Public & private services - a Likely one
HR
H
R
Claims
Synchronization
Claims Processing
Claims
Processing
Processing’ CRM
Private Cloud Public Cloud
Private Cloud Public Cloud
© 2011 Oracle Cloud Computing – Why you need Architecture 17

18. XaaS Component Architecture
And the value of Integration
© 2011 Oracle Cloud Computing – Why you need Architecture 18

19. Component Architecture – DB consolidation
Standardization isn’t always the first step
Optimize
Automate
Consolidate Achieve new
Reduce the efficiency
Standardize
manual tasks
Reduce the
footprint
Define a
standard solution
© 2011 Oracle Cloud Computing – Why you need Architecture 19

20. Component Arch ex. – Database Cloud
Three alternatives to multi-tenancy
DW CRM ERP DW ERP CRM DW ERP CRM
Schema
Schema
Schema
Schema
Schema
DB
DB
DB
DB
DB
DB
DB
OS OS OS
Hypervisor Hypervisor OS OS OS OS
Server Operating System Database
Deploy in dedicated VMs Share server pool Share database instance
Server virtualization Real Application Clusters Real Application Clusters
Workload Type Server OS Database
Mission or Business Critical p
Standardized environment p p
Rapid provisioning (Dev / Test) p p
Mixed workload as-is consolidation p
© 2011 Oracle Cloud Computing – Why you need Architecture 20

21. Engineered Systems in the Cloud
PaaS services from Integrated HW/SW
Exadata / Exalogic
• Reference configuration
• Known sizing
• Order as ‘part number’
• Unified support
• Simplified deployment
• Run existing apps
• Enterprise scale
• High performance
© 2011 Oracle Cloud Computing – Why you need Architecture 21

22. Build from Scratch vs. Exadata
Commonwealth Bank of Australia
Build From Scratch Reference Oracle Exadata
with Components Configurations Database Machine
Testing and
Validation  Server Pool pre-configured
 Faster deployment
Installation and Testing and  Lower Risk
configuration Validation
Acquisition of
components Installation and
configuration
Testing and Validation
Pre-implementation
Acquisition of Configuration
System sizing
components Take delivery of Oracle
Database Machine
Weeks to Months Weeks to Months < 1 Week after Delivery
•DB deployment time reduced from 3 months to < 1 week
© 2011 Oracle Cloud Computing – Why you need Architecture 22

23. Absracting application architecture
What are Deployable Entities?
© 2011 Oracle Cloud Computing – Why you need Architecture 23

24. What will you ‘deploy’?
It’s more complex than a bunch of images
Deployable Entities
(aka VDCs) include Model Mgmt.
Service Templates Architectural models of
and Context (e.g. cloud applications may
‘Assemblies’) be external (deployment
code), embedded (e.g.
OVF) or internal
© 2011 Oracle Cloud Computing – Why you need Architecture 24

25. Oracle Cloud API ‘Service Catalogue’
Images plus architectural meta-data
• Repository of models
• Models contain
templates and
service contracts
- Payloads like virtual
server images
- Application metadata
such as configurations
and policies
© 2011 Oracle Cloud Computing – Why you need Architecture 25

26. Model / Service Management
Need to do both
• Model management supports • Service management controls
build-time functions in cloud the run-time aspects of the cloud
- Exposes resources to developers - Capacity management
- Stores developer’s models for - Service management
deployment
• Operator’s main point of contact
- Validates cloud models
for the cloud
• Developer’s main point of
• Provisions / monitors resource tier
interaction with the cloud
• Contains configuration
• Model management also
management repository which is
contains the solution catalogue,
the current state of all cloud vDCs
facilitating discovery, storage,
use and re-use of cloud
services
© 2011 Oracle Cloud Computing – Why you need Architecture 26

27. Oracle Virtual Assembly Builder
Automating deployment of ‘assemblies’
config1
config2
Assembly =
Appliances
(VM Templates +
Dev/Test configuration
Environment Metadata) +
relationships & start
order Metadata Production
Environments
• Package up complex structure from dev/test and reconstitute in production
• Minimize setup time and risk of hard-to-debug configuration errors
• Easily replicate in production with minor variations
• Each instance has well-contained configuration parameters for flexibility
© 2011 Oracle Cloud Computing – Why you need Architecture 27

28. Admin/Archtiecture as a Service
‘Refactoring’ Dev / Ops Roles
© 2011 Oracle Cloud Computing – Why you need Architecture 28

29. ‘Enterprise’ Private Clouds are Different
SaaS
Saa
• Consider the 5 NIST essential characteristics
I
N
T
R PaaS
Paa
- On-demand self-service, Resource pooling, A Rapid
N
elasticity, Measured service, Broad network access E
T IaaS
Iaa
• But are ‘private’ clouds different from ‘public’ clouds…
- E.g., On-demand self service
• Public developer cloud – unrestricted resources provisioned in
minutes, but with no controls or corporate governance
• Enterprise private cloud – need provisioning controls, standards
enforcement, prioritization, approvals, etc.
- I.e., Enterprise cloud faster to deploy than traditional IT, but probably
slower that public cloud
• How ‘SELF’ is self-service really?
- What roles are involved in managing, deploying and consuming
the Cloud?
© 2011 Oracle Cloud Computing – Why you need Architecture 29

30. Identify Roles and Interactions
Cloud implies changes in IT roles
Models Service
DevOps
App Owner Developer
Monitors & Creates Services Packages &
User Approves Services Deploys Services
uses
service Monitor/manages cloud
Cloud Operator
creates resources
Cloud Builder
© 2011 Oracle Cloud Computing – Why you need Architecture 30

31. Cloud Roles / Actors
Each role category has possible sub-roles
Category Actor DMTF Roles
Cloud Service Operator Service Operations Mgr
Provider
Builder Service Business Mgr
Service Transition Mgr
Cloud Service Service Developer
Developer Service Developer
Deployer / DevOps
Cloud Service Consumer Business Mgr
Consumer Application Owner
Consumer Service Admin
User Service User
© 2011 Oracle Cloud Computing – Why you need Architecture 31

32. Build time vs run time perspectives
Need to separate development / operations horizons
BUILD
Process Modeling, Simulation
TIME
and Documentation Service
Developer
Application
Owner
Service Identification &
Discovery
End
Users
Service
Deployer
RUN
TIME Cloud Monitoring and
Metrics
Cloud Deployment Engineering
Cloud Builder
Operator
© 2011 Oracle Cloud Computing – Why you need Architecture 32

33. Example of Build vs Run Time
Oracle Virtual Assembly Builder roles
1. Set Up Cloud 2. Build App RUN TIME
Build app using App 3. Use App
shared Developer
components
IT
Set up Cloud Set up self-
Platform service portal Dept Use app App Users
Set up
shared
App
components Deploy using
self service
4. Manage App
BUILD Shared Components Self-Service Interface
TIME Integration / Security &
BPM Portal App Owner
SOA Identity
Manage
Application Server System
Oracle Cloud Platform Manager
Adjust
Capacity
Database Review
Charge-back
Operating System,Virtualization,Server,Storage
© 2011 Oracle Cloud Computing – Why you need Architecture 33

34. So how do I get there?
Use architecture to keep IT simple
© 2011 Oracle Cloud Computing – Why you need Architecture 34

35. Focused Implementation Vs. Wide Diffusion
Most companies have multiple projects underway or anticipated
• Strategic – Complete migration for a given architecture/application,
often focusing on revenue enhancement
• Tactical – Wide deployment of a limited technology (e.g. virtualization),
often focusing on cost reduction
© 2011 Oracle Cloud Computing – Why you need Architecture 35

36. Cloud Computing Roadmap
How Will Your Cloud Be Introduced?
• Cloud computing efforts range from small
‘experiment’ projects to major strategic initiatives.
• Most companies have multiple initiatives.
• It doesn’t have to get more complicated
- Before you start (not just after you finish)…. Architecture
- Make things more simple through higher levels of integration and
abstraction
- Consider Oracle VM Templates, OVAB Assemblies, Engineered
Systems, Oracle Public Cloud
Strategy, Architecture, Transformations,
Measurement, Readiness, Roadmap
© 2011 Oracle Cloud Computing – Why you need Architecture 36

37. Using Public Cloud Computing
Oracle Public Cloud
Look for:
Fusion Fusion Fusion Fusion
 Pure-opex model CRM HCM Talent ERP
 Enterprise grade multi-tenancy
 Integrated development environment
Database WebLogic WebCenter
 Transparent architecture and control Service Service Connect
Service
 10X+ productivity
 Install applications (not just images)
 Unambiguous data persistence Security &
Identity
Integration
Service
 Predictable … Service
 performance, elasticity, price
© 2011 Oracle Cloud Computing – Why you need Architecture 37

38. Using Public Cloud Computing
Oracle Public Cloud
Look for:
Fusion Fusion Fusion Fusion
 Pure-opex model CRM HCM Talent ERP
 Enterprise grade multi-tenancy
 Integrated development environment
Database WebLogic WebCenter
 Transparent architecture and control Service Service Connect
Service
 10X+ productivity
 Install applications (not just images)
 Unambiguous data persistence Security &
Identity
Integration
Service
 Predictable … Service
 performance, elasticity, price
© 2011 Oracle Cloud Computing – Why you need Architecture 38

39. Implementing Private Cloud Computing
Oracle Consulting Cloud Services
• Lifecycle services approach to deliver business solutions
• Unparalleled product skills across the entire Oracle portfolio
• Extensive architecture and system knowledge
© 2011 Oracle Cloud Computing – Why you need Architecture 39

40. For More Information….
oracle.com/cloud
© 2011 Oracle Cloud Computing – Why you need Architecture 40

41. © 2011 Oracle Cloud Computing – Why you need Architecture 41

42. © 2011 Oracle Cloud Computing – Why you need Architecture 42
© 2009 Oracle 42

43. Oracle Consulting
Transforming Your Business Using Oracle Solutions
Deliver on Oracle’s commitment to
ensure you maximize business value
• Lifecycle services approach to deliver
business solutions WHY ORACLE CONSULTING
• Unparalleled product skills across the Leading Expertise: Oracle’s own experts
entire Oracle portfolio providing thought leadership for every
Oracle solution
• Extensive architecture and system Broad Coverage: “End-to-end” lifecycle
knowledge services across the entire Oracle product
footprint
• Deep industry understanding, focus, Global Scale: 20,000 Oracle
and alignment experts in 145 countries, serving
over 20 million users
• Close working relationship with global Flexible Delivery: Onsite, offsite,
system integrators and offshore, along with innovative
solutions such as Advisory and Architecture
• Leading global service delivery model Services
• Industry leader in certified consultants
© 2011 Oracle Cloud Computing – Why you need Architecture 43

44. Oracle Public PaaS
Architecture and Key Product Mapping
cloud.oracle.com SaaS
Self-Service Sign Up,
Lifecycle Management Oracle Fusion SaaS
Oracle Applications ISV and Custom Applications
Oracle Public PaaS
Database Service
Oracle Database Oracle Service
Java WebLogic Enterprise WebCenter
Oracle Social Service
Shared Enabling & Management Infrastructure
Secure File HTTP Routing Notifications Secure Backup Integration Usage &
Virus Scan Transfer White List Gateway Billing
Identity Data Configuration Management
Management Load Virtual Service Assemblies System
Oracle Data Provisioning
Oracle Identity Integration
Oracle Enterprise
Access
Management Data Oracle Virtual Manager
Application Management
Management Synch Assembly Builder
Oracle Tenant
Real Time
GoldenGate Management Quality & Lifecycle
Directory Metadata Metadata Metadata
Events Management
Shared System Infrastructure
Database Tier
Oracle Exadata Middle Tier
Oracle ExaLogic
© 2011 Oracle Cloud Computing – Why you need Architecture 44

45. Using Public Cloud Computing
Oracle Public Cloud
Look for:
 Pure-opex model
 Enterprise grade multi-tenancy
 Integrated development environment
 Transparent architecture and control
 10X+ productivity
 Install applications (not just images)
 Unambiguous data persistence
 Predictable …
 performance, elasticity, price
© 2011 Oracle Cloud Computing – Why you need Architecture 45

46. cloud.oracle.com
Self-
Self-service Sign Up, Lifecycle
Management
SaaS
Oracle ISV and Custom
Applications Applications
Oracle Public PaaS
Database Service WebLogic Service WebCenter Connect Service
Shared Enabling & Management Infrastructure
Virtual Service Assemblies, Shared Provisioning, Integration, Security & Identity Services, Operational Tools
Integration, Services,
Shared System Infrastructure
Database Tier Middle Tier
© 2011 Oracle Cloud Computing – Why you need Architecture 46