Why does Oracle want to be a cloud provider? And how is it going about it? What are the challenges facing Oracle along that path? Where does it currently stand with its Public Cloud service offerings - and what lies around the corner? How can organizations get started with the Oracle Public Cloud? What architectural considerations come into play?
2. 2
Overview
• Demo of some PaaS Cloud Services
• The Public Cloud from Oracle’s perspective
– ‘so you want to become a cloud provider?’
• Current Status of Oracle PaaS Portfolio
– What is out there, what is in preview and what is planned
– Two cloud product “flavors”:
on premises product offered from the cloud and pure cloud products
• Near future roadmap
• Why and how to get started in Oracle Public Cloud
• Discussion
3. 3
Oracle needs to go to the cloud
• Why?
– Hype
– Customers
– Competition
– Analysts
– Opportunities
• Foundation under Oracle Corporation:
– License vs. Subscription
4. 4
Vision 2025
• 80% of production application will be in
the cloud (today 25%)
• Two Suite Providers will have 80% of the SaaS market
– “Who will be the other one?”
• 100% of Dev/Test will be in the public cloud
– 30-40% of IT spending
• Virtually all enterprise data will be stored in the clouds
– Some % in Private Clouds
• Enterprise Clouds will be the most secure IT environments
– Web scale security
– State of the art Encryption
– Latest [security] patch always applied
– Physical security at near-military level
6. 6
IaaS
• Lot of action – much demand for Storage and Compute
• Fairly easy to get started – need iron, network and power
However:
• Low margin
• Need high volume
• Requires web scale (or cloud scale) operations
– Automated, 24/7, around the globe
• Hard to differentiate vs. competition
• Strong Front Runners: Amazon (AWS), Azure, Google, Verizon,…
8. 8
SaaS
• High business value == high margin
• Differentiate on functionality
• Many niches to compete in (by industry, region, company size,…)
• Fairly small volume can do to make a profit
• You need a business application – tried and tested
– Could be homegrown, used for on premises => redesigned for Cloud
– Or acquired, running as a SaaS application from the beginning
9. 9
SaaS – further requirements
• Customize
• Extend
• Integrate
• Also: we need a Platform to run the SaaS application
– It would be nice if that same platform is used for customization, extension and
integration
– Ideally using the same technology used for the base SaaS application – so we can
leverage generic components and facilities (SSO, styling, deployment, monitoring,
management, logging, …)
11. 11
PaaS – Platform as a Service
• Platform ==
• Not business specific; does not provide functionality directly to business users;
used by developers & administrators to (create &) run SaaS and custom
software components on
• Typical platform components:
– Database for persistent data storage and retrieval (relational and NoSQL)
– Application container (server) to run standard application types (Java EE, …)
– Integration facilities to create connections and exchange data between applications
– Identity and Access Management
• Note: sometimes hard to differentiate between SaaS and PaaS
– Dropbox and Oracle DCS
– Wordpress, DatumPrikker, Oracle Sites CS
– Facebook, Yammer, Oracle Social Network
12. 12
Oracle and PaaS
• Oracle has a platform on which its SaaS can run
• Given the industry move from on premises to cloud
– And from long term licenses and support fees to ‘pay as you go’
• Would offering the Oracle Platform as public PaaS not make perfect
sense? Or: even be a requirement for survival?
– And in the process as private PaaS as well?
• What would it take to offer the Oracle Platform successfully as PaaS?
– And is that achievable by Oracle Coporation?
13. 13
What would it take to offer the Oracle
Platform successfully as PaaS?
• Criteria used for evaluating PaaS services include
– security,
– scalability,
– performance and availability,
– richness of functionality,
– adherence to standards and openness,
– ability to integrate (with),
– required and available skills,
– maturity (How proven is the technology [on the cloud]? Who is also using it?),
– ability to run existing applications
– the Total Cost of Ownership [compared to the on premises alternatives and to other
PaaS providers], including ease of administration
• Also: compare Oracle PaaS to Oracle Platform running on 3rd party IaaS
– E.g. Oracle Database on Azure and Oracle Fusion Middleware on AWS
14. 14
Competition
may not always be competition
• 9 out 10 biggest SaaS vendors
– Run on the Oracle Platform
– Not WorkDay (ERP, HCM)
• Custom database
• Custom development tools & programming language
• Running Oracle Database, WebLogic Server and other Platform products
on 3rd party IaaS/PaaS Public Clouds is an option
– That brings in license revenues to Oracle (same as on premises)
– Examples: AWS, Azure
15. 15
TCO on Public PaaS Cloud
Pay per Use on
Oracle PaaS
IaaS
Platform
Software
(license)
Operating Costs
for Cloud
provider
Pay per Use on
3rd party
16. Pay per Use on
Oracle PaaS
16
Oracle has some room for
manoeuvring with platform license
Pay per Use on
Oracle PaaS
IaaS
Platform Software
(license)
Operating Costs
for Cloud
provider
22. 22
Some observations around
cloud == on premises
• Release cycles for Public PaaS and on premises are not synchronized
– For example: WLS (12.2.1 and 12.2.2)
• Configuration is not the same on premises as in the cloud
– Though similar, the deployment process is not exactly the same; some new ‘cloud
skills’ are required
• Some Oracle PaaS Services are not available as on premises product
– Note: Oracle [Public] Cloud Machine
• Some Cloud Vendors provide local development environments that
emulate the cloud run time
• ≈ != =
23. 23
Security
• Oracle is pushing the message that security will become a driver to go to
the cloud
– Not one for staying out of it!
• Motivation
– Cloud scale security is way more secure than your own security could ever be
– Always-on security at every level (and for data in transit and data in rest)
• Physical data center and staff, network, CPU, database, …
– Data is encrypted in rest – and we do not have the key
• So even when subpoenaed, we cannot hand over your data
24. 24
Internal challenges Oracle
needs to address
• Continuous Availability
– Uptime, fail-over, SLAs, zero-down-time patching and application deployment, …
• Density and enough IaaS capacity
– Get more PaaS out of IaaS
• Automated IT Operations
– Ease and speed of provisioning [and patching, upgrading, scaling, …]
• Pricing models
– what do you charge for, how [and when] do you compensate Sales staff
– BYO, elastic scale, what can you charge Support fees for?
• Billing
• Properly integrate all services
– Common user experience, one implementation of each function, SSO, single agent,
shared architecture vision
• Communication with users of cloud service
– Pro-active, consistent, clear
• DevOps
25. 25
Opportunities
• Market potential
– Small and Midsize Business
– Non-Oracle shops
– “Enterprise App Store”
• Citizen Developer or LoB user
– The heavy Excel or Access user, Survey Monkey or Google Forms, Tableau, …
• Agile Product Development
– High release frequency – quick, small, often
– Insight in feature usage (see the dogs in action)
– Insight in optimal implementation – for example through A/B testing
– Bridge the gap between product development teams: better integrate, less overlap,
reuse common facilities
26. 26
IaaS
• To run a Platform you need Infrastructure: Compute, Storage, Network
• If you want to be a PaaS provider – you need IaaS
– Your own or someone else’s
• Criteria to select an IaaS provider
– Price, Scale/Elasticity, Security, Image
• Oracle cannot afford to depend on third party IaaS
– Besides: it want to offer a complete cloud portfolio
• It needs to set up IaaS
– And offer it as Public IaaS to not drive customers away
• However: it cannot differentiate on IaaS
– Or even make money with IaaS [for now]
• Oracle offers the exact same stack in the cloud
as is available to customers on premises
– That means it implements its IaaS with Exalogic & Exadata,
Oracle Enterprise Linux and OVM.
– Perhaps at some point M7 powered SuperCluster as well?
27. 27
Premium IaaS
• To differentiate – and make some profit with IaaS – Oracle offers a
number of premium IaaS services
– Exadata as a compute unit – the most powerful compute unit to be had as IaaS
– Dedicated Compute – instead of sharing hardware with potentially noisily
neighbors, the compute nodes run on hardware used only for a single tenant
– Direct Connect – ultrafast (low latency, high capacity) network connections
between Oracle Public Cloud and on premises environment, leveraging the
Equinix Cloud Exchange
– Hierarchical Storage Manager
• More is suggested around Software Defined Networking and Security
28. 28
The story Oracle wants to push:
The whole stack hangs together
• You want your infrastructure provider
to run a public cloud
– To allow relevant and enough investment
and evolution
• Do you want IaaS provider
who does not run PaaS?
– Running a platform helps you understand needs
from infrastructure
• Or PaaS provider not running SaaS
– SaaS requirements help (im)prove PaaS
• And of course a SaaS vendor must have an open PaaS
– for customizing/extending/complementing/integrating
• Ideally, custom built software (or 3rd party software) can run on PaaS as
easily as in premises
– And can be moved from one PaaS vendor to the next
30. 30
As an aside: on premises is alive
and kicking too [and benefits]
• Oracle Hardware and Software powers
the cloud
and is being optimized for that purpose
– You benefit on premises
with your private cloud
• Multitenancy support
– Density – usage of physical resources
(consolidation)
– Isolation
– Ease of admin (provisioning, patch, backup,…), Single Pane of Glass
• Availability (KSplice Hot Patching, DB RAC, WLS Continuous Availability,
Stretch Active-Active)
• Portability (PDB, Partition, Docker support)
• Dynamic Scalability (In Memory, M7, Database Sharding)
• Performance (reduced latency) DirectConnect, In Memory
• User Experience – Alta, Oracle JET
31. 31
Overview
• Demo of some PaaS Cloud Services
• The Public Cloud from Oracle’s perspective
– ‘so you want to become a cloud provider?’
• Current Status of Oracle PaaS Portfolio
– What is out there, what is in preview and what is planned
– Two cloud product “flavors”:
on premises product offered from the cloud and pure cloud products
• Near future roadmap
• Why and how to get started in Oracle Public Cloud
• Discussion
34. 34
Cloud History at OOW
You need a grid
Nah, you don’t need a
cloud
What about just a cute
little private cloud?
Are you sure you wouldn’t
prefer an engineered
system?
Today, we
announce the
Oracle PubliC
Cloud
A previewof the
beta of the
prototypeis almost
…
Nimbus, Cirrus, Stratus, Incus, Pannus,…
anycloudunder the sun. And yes that
takes a while!
The boss is off sailing. I’m
hereto launchsome new
cloud services
2013
37. 37
20152014
We are almost there – and
some cloud services are
reallylive…
Come,let me show you how
to take a PDB from premise
into the cloud
And: Lift Off!
40. Bring Oracle’s leading
Infrastructure, Technology,
Business Applications, and
Information to customers and
partners anywhere in the
World through the Oracle
Cloud
Oracle Cloud: Mission
43. 43
Two categories of PaaS
Services are defined
• On Premises product offered from the cloud [as is]
– Easy provisioning (click-click install on secure compute and storage);
– IaaS is managed; Platform components are managed by customer
– Largely the same experience for administrators and entirely the same experience for
developers
– Lift and Shift of workloads is possible
– Examples: DBaaS, SOA CS, JCS, Data Visualization, API Catalog, MFT, BigData
• Cloud only product – developed for and offered from the cloud
– (sometimes based on a pre-existing on premises product; that association is bound
to fade over time – ICS OSB, PCS BPM, DCS WC Content))
– Examples: MCS, ICS, PCS, DCS, IoT CS, ABCS, BICS, Sites CS, BigData
Preparation, Developer CS, OSN, Messaging, Management CS, Idm CS
• Third category: On Premises Platform Product provisioned on JCS and
DBaaS
– You install and manage yourself
– Example: BPM Suite, WebCenter Portal
44. NoSQL
44
Status PaaS offerings
DBaaS
Management
CS
Idm CS
DCS
PCSOSN
Database
Backup
BigData
Dev CSACC
JCS
ABCS
ICS
MFT
SOA CS
MCS
API
Catalog
API
Manager
Data Viz
BI CS
IoT CS
BigData
Preparation
BigData
Discovery
Sites
CS
Messaging
JCS-SX
DBSchema
aaS
45. 45
Noteworthy
• Enterprise Manager 13c – A single pane of glass
• ICS Agent – bridge the gap from on-premises to the cloud
• Idm CS – brings its own cloud on premises exchange (federation)
• Management Cloud – again, agents
• Oracle Cloud Marketplace
• Oracle Cloud Machine
46. 46
Enterprise Manager 13C
Single pane of glass
- Gold agent
- 24 x 365 , always on
- Brownouts
- Event compression – grouping of
events
- Compliance mgmt, e.g. Orachk
integration
54. Overall Public PaaS Cloud
release roadmap
IaaS
PaaS
SaaS
Database
Developer
Java
Document
Elastic
Compute
Storage
Mobile
Cloud
Process
Social
Network
SOA CS
NoSQL
ApplicationBuilder
2014 2015 2016
Cloud MarketPlace
ERP Cloud
HCM Cloud
Sales Cloud
Messaging
ICS
TransportCX Cloud
MAX
ExaData
RAC
Application
Container
Management
Sites IoT
SCM Cloud
Container
(Docker)
NetworkStorage
- Archive
API
Catalog
Data
Visualization
BigData
Preparation
Java SE
Node.js
GoldenGate
BigData
Discovery
DaaS
Paas
4Saas
Marketing Customer
Intelligence
Sales
Database
Backup
IdM CS
API Mgt
Platform
JCS
12.2.1
BigData
MFT
may
55. 55
Pricing/Billing
• Metered and Unmetered
– Metered: Hourly or Monthly fee – stop and start, scale, flexible price
– Unmetered: fixed SKUs – standard product configurations, charged whether used or
not
• Minimum contract period (3 year for SaaS, 1 year for PaaS?)
• Minimum service shape
– No free tier (except for 30 day trial and except perhaps for DBSchema-aaS)
• Negotiate Discounts
• Bring your own license?
• Cloud Fee Calculator is not currently offered by Oracle!
• TCO Calculator – to compare Public PaaS to On Premises is sorely
missed
• Price is not at this point a positive discriminator for Oracle Public PaaS
56. 56
Case: How to convince a
customer to use SOA CS?
• Real world challenge for REAL partner Opitz: how to convince a
customer to use SOA CS instead of SOA Suite on AWS EC2
• What are considerations?
– Required skills
– Administration effort
– Functionality
– Non-functionality (performance, scalability, availability)
– TCO
– Maturity, References, Proof
• What was the conclusion presented to the customer?
SOA CS
DBaaS
EC2
SOA Suite &
WebLogicEC2
Oracle
Database
57. audience
IoT CS
PCS
Our
webapp
Real “Things”
(Pis, Arduino’s,
…)
Collect and analyze
audience input;
forward findings to
REST service
Run human workflow
based on suggested
artist; approve/reject,
add image and
description; forward to
REST service
The Valencia Demo
58. audience
IoT CS
PCS
DCS
ICS
Our
webapp
OSN?
Real “Things”
(Pis, Arduino’s,
…)
Collect and analyze
audience input;
forward findings to
REST service
Run human workflow
based on suggested
artist; approve/reject,
add image and
description; forward to
REST service
59. audience
IoT CS
PCS
DCS
ICS SOA CS
DBaaS
Our
webapp
Storage
CS
OSN?
Real “Things”
(Pis, Arduino’s,
…)
Collect and analyze
audience input;
forward findings to
REST service
Run human workflow
based on suggested
artist; approve/reject,
add image and
description; forward to
REST service
Expose REST API [for PC
to invoke] to register a
proposed artist and a
supporting image; recor
artist details persistently
[with some enrichment]
60. audience
IoT CS
PCS
DCS
ICS SOA CS
DBaaS
Our
webapp
MCS
Storage
CS
OSN?
Real “Things”
(Pis, Arduino’s,
…)
Collect and analyze
audience input;
forward findings to
REST service
Run human workflow
based on suggested
artist; approve/reject,
add image and
description; forward to
REST service
Publish REST APIs that
expose data on proposed
artists including the selected
image
(could be from MCS, ICS, JCS,
ABCS or SOA CS)
Expose REST API [for PC
to invoke] to register a
proposed artist and a
supporting image; recor
artist details persistently
[with some enrichment]
61. audience
Some script
(SoapUI,
Postman)
IoT CS
PCS
DCS
ICS SOA CS
DBaaS
Our
webapp
MCS
JET on
AppContainer CS (or
JCS)
ABCS
Storage
CS
OSN?
Real “Things”
(Pis, Arduino’s,
…)
Collect and analyze
audience input;
forward findings to
REST service
Run human workflow
based on suggested
artist; approve/reject,
add image and
description; forward to
REST service
Expose User Interface that
contains the proposed artist
with some enrichment,
based on REST APIs
(exposed from MCS, ICS, JCS,
ABCS or SOA CS)
Publish REST APIs that
expose data on proposed
artists including the selected
image
(could be from MCS, ICS, JCS,
ABCS or SOA CS)
Expose REST API [for PC
to invoke] to register a
proposed artist and a
supporting image; recor
artist details persistently
[with some enrichment]
64. 64
Heel veel meer Cloud nieuws
• Donderdag en vrijdag 2 en 3 juni – Vliegveld Valkenburg
• 120 sessies, 8 zalen, 1 keynote & 1 feestavond; 80 sprekers uit 5 continenten
• Speciaal aandacht voor Idm Cloud, Management Cloud, Application Builder
Cloud, Java Cloud, Container Cloud, API Platform CS
65. 65
Overview
• Demo of some PaaS Cloud Services
• The Public Cloud from Oracle’s perspective
– ‘so you want to become a cloud provider?’
• Current Status of Oracle PaaS Portfolio
– What is out there, what is in preview and what is planned
– Two cloud product “flavors”:
on premises product offered from the cloud and pure cloud products
• Near future roadmap
• Why and how to get started in Oracle Public Cloud
• Discussion
66. 66
Systems on the Edge—Your Stepping
Stones into Oracle Public PaaS Cloud
• Promises of the Cloud
• Edge Systems
– What are they – attributes
– Common Challenges
– How can cloud help address these challenges
• Use cases and
mapping to Oracle Public Cloud Services
• How to get going with edge systems in the public cloud
– And pick the low hanging cloud fruit
67. 67
Cloud Benefits –
from the customer’s perspective
• Ease and Comfort
• Cost effective
• Flexibility – quick, agile
• Quality
• Security
• Any time, Any place
68. 68
Why is the cloud hot?
• Web Scale for the rest of us
– Availability, Scalability, Security, …
• No specific expertise or even effort for consuming services
– No need to acquire skills, build up experience and hire special resources
• No physical facilities – room, cooling, cleaning,
physical security, power
• No/Low initial investment (low entry level)
• Pay per use (no gain, no pain) (CAPEX => OPEX)
• Flexible up and down scaling (capacity on demand)
• Quick Ramp-Up, Rapid Start
• Enterprise functionality for small businesses
– Out of reach in the on premises world
• Accessibility from anywhere
• Global market place
• Lifting the burden from your shoulders
SaaS
PaaS
IaaS
70. 70
TCO
• Time based
subscription
– Cost based
on actual
usage
• Initial set up
• Some admin?
• Purchase of
software and
hardware
• Capital lock
• Physical space
and Energy
• Initial set up
• Administration
– Skills
– Operations
• Gap between
acquired and
used resources
• Wait time
incurred costs
• …
71. 71
Cloud adoption in
bottom-up steps
IaaS/PaaS
Self study
PoC
Training
Load Test
Func Test
Peak, Failover
Peripheral Applications
Backup
BI
Edge Systems
Core Systems & Secure Data
[Distributed] Development
BPO
72. 72
Edge Systems
• What are edge systems?
– Systems accessed by parties (people
or systems) from outside the enterprise
• Typical characteristics
– Visible to business partners & the general public
– Interactions initiated externally – large numbers of
unknown individuals/devices/systems
• External entities accessing systems
– Uses data only indirectly (does not store data)
• Except application specific data and perhaps for caching reasons
Enterprise
DMZ
Enterprise
Database
ERP
ESB
Core
Business
Application
Enterprise
Documents
X
Z
Y
Q
API
Gateway
73. 73
Edge Systems
• Typical Challenges
– High availability requirements
– Scalability/volume/peaks
• License consequences
– Latency
– Security: potentially large numbers of fairly
unknown parties accessing the enterprise realm
– Provisioning environments and network
configuration (timely)
Enterprise
DMZ
Document
Exchange
Website
& Portal
CX
B2B API
3rd Party
Workflow
IoT data
drop-off
Mobile
APIs
API
Gateway
Enterprise
Database
ERP
ESB
Core
Business
Application
Enterprise
Documents
X
Z
Y
Q
74. 74
Edge Systems
moving towards the cloud
Enterprise
DMZ
Document
Exchange
Website
& Portal
CX
B2B API
3rd Party
Workflow
IoT data
drop-off
Mobile
APIs
API
Gateway
Enterprise
Database
ERP
ESB
Core
Business
Application
Enterprise
Documents
75. 75
Edge Systems
moving towards the cloud
Enterprise
DMZ
API
Gateway
Enterprise
Database
ERP
ESB
Core
Business
Application
Enterprise
Documents
Document
Exchange
Website
& Portal
CX
B2B API
3rd Party
Workflow
IoT data
drop-off
Mobile
APIs
76. 76
Edge Systems moving towards the
Oracle Public Cloud
Enterprise
DMZ
API
Gateway
Enterprise
Database
ERP
ESB
Core
Business
Application
Enterprise
Documents
DCS
Sites &
JCS &
Portal
CX
ICS &
SOA CS
PCS
IoT,
Node.JS
MCS
77. 77
How cloud addresses
challenges for edge systems
• High availability requirements
– Web Scale operations
– Multi-site (region)
• Scalability/volume/peaks
– Dynamic, rapid, on-demand upscaling/downscaling
– Pay per use, no upfront investment, No High Watermark licensing
• Latency
– Multi Data Center topology, Distributed Content Delivery
• Security: potentially large numbers of fairly unknown parties accessing the
enterprise realm
– Relocation of the DMZ to the cloud
– The only interaction with the enterprise realm is by well-known cloud based systems
– not by many third parties
– Web Scale security measures
• Provisioning environments and network configuration
– Out of the box, click-next-finish, minutes to completion
78. 78
Edge on Cloud <=> On Premises
integration challenges
• Bridge to connect cloud and enterprise
– Two way (cloud enterprise)
– Synchronous & Asynchronous (event push)
– Secure
– Approach: SSH or even VPN channel, API Gateway in DMZ, local agent on
premises, leverage message cloud (aysnchronous push and pull)
• Data Cache (refresh) & Data Replication
• Identity Management – replication of identities & roles
• UI Integration
– “mash up” and deeplink navigation
– Session sharing and Single Sign On
– consolidated search and menu
– style & web content synchronization
• Software Delivery
– (no more challenging than on site)
Enterprise
DMZ
80. 80
Case:
Monthly Reporting obligation
• Financial institution is faced with the requirement
to monthly report events and status to a
dozen stakeholders such as government agencies
– Each stakeholder receives a customized report
• The challenge: how to deliver the report
– Given functional and non-functional requirements
• Options
– On paper
– Email attachment
– (S)FTP server
– Read only secure web site
– …
• Requirements
– Electronic, On line
– Archive/history
– Searchable
– Multi-format
Enterprise
Enterprise
Database
Core
Business
Application
Enterprise
Documents
Report
Generator
sftp
web
site
email
paper
mail
IAM
81. 81
Case:
Monthly Reporting obligation
Business Partners,
Government Agencies and
other stakeholders
Document
Cloud
Service
Enterprise
Enterprise
Database
Core
Business
Application
Enterprise
Documents
Report
Generatorupload through APIIdentity Cloud
Service
Doc History & Archive
Search
Mobile Access
Secure
Access Audit trail
Social integration
Format conversion
83. 83
Case:
Mobile App for veterinarians
Enterprise
Service
Bus
SOA
Composite
3rd party
case mgt
Mobile Veterinarian
Enterprise
Database
Core
Business
Application
Enterprise
Documents
B2B Partners
3rd party
ERP
Portal
SOAP2
REST
SOAP REST
XML JSON
Some Concerns:
• Volume
• Security
• API unfriendliness
• Development &
maintenance effort
• Monitoring &
Analytics
84. 84
Case:
Mobile App for veterinarians
Enterprise
Service
Bus
SOA
Composite
3rd party
case mgt
Mobile Veterinarian
Enterprise
Database
Core
Business
Application
Enterprise
Documents
3rd party
ERP
Portal
Mobile
ICS |
SOA CS
B2B Partners
API
con
nect
push
anal
ytics
user
mgt
86. Customer
Customer
86
Case:
ISV scale down and scale out
• Developing an application for long term project budget management
– Especially for local and regional governments
• Implemented on premises
– Done by technical implementation consultants that go on site with customer
– Challenging to get servers, network, database => long implementation times
• Objective:
– Offer the product to smaller
organizations
(increase reach)
– Offer the product in the
global market place
• Requirement:
– Very rapid implementation
- (turn key == enter URL)
without on site consultancy
– Global accessibility
– Flexible capacity
ISV
IDE
ISV
Developers
Customer
WLS
Database
WLS
Database
End users
87. 87
Case:
ISV scale down and scale out
Enterprise
IDE
ISV
Developers
Database
Java
Optionally use the User Experience
Rapid Development Kit to achieve
Simplified UI based on ADF & Alta
Developer
CS
Social
Document
PCS
MCS
Management
CS
Analytics
ABCS
88. 88
Case: lift and shift application
or replace custom or 3rd party
COTS with SaaS
89. 89
Case: lift and shift application or replace
custom or 3rd party COTS with SaaS
Interface
Internal UI
Applications
Portal
Web
Applications
External
Web
Services
Mobile
Web Sites &
Content
Multi
Channel
3rd
party
App
• Replace custom or COTS application
on premises with SaaS offering
– More functionality, less effort,
easier admin & maintenance,
work anytime any place
– Note: SaaS == Silo as a Service
• Move custom or COTS
application from on premises
to PaaS
– Easier admin & maintenance, better
scaling (up and down), work anytime
any place
• Challenges
– Existing integrations – both API
– UI Mash-up
– Single Sign On (and IAM)
– Data replication & governance
90. 90
Case: lift and shift application or replace
custom or 3rd party COTS with SaaS
Enterprise
IAM
API
Gateway
VPN
Service
Bus
Portal
Enterprise
Users
Enterprise
Database
Core
Business
Application
Enterprise
Documents
Java for SaaS
UI mash up
SSO
Integration
CS
IdM CS
91. 91
Case: lift and shift application or replace
custom or 3rd party COTS with SaaS
SOA
Message
Enterprise
IAM
API
Gateway
VPN
Service
Bus
Portal
Enterprise
Users
Enterprise
Database
Core
Business
Application
Enterprise
DocumentsDatabase
Java
Java for SaaS
UI mash up
SSO
Data Replication
Event Pub/Sub
Integration
CS
IdM CS
93. 93
Case:
the ultimate digital user experience
• Pension Fund with high ambitions
– Themes: Digital, self service, 24/7, paperless, STP , Google fast and Apple friendly
– User benefits: higher quality and faster (even pro active) response, great experience
– Business benefits: cost reduction, competitive position, new services, agile: quick time
to market
• Portal and Customer Experience are crucial in this strategy
– Multiple user groups (employees, employers, financial consultants, …
– Multiple brands
– Both public (web site) and personal (authenticated portal)
– Strong integration with back end enterprise systems
– Easy web content management (dialogs, documents, FAQ/knowledge, events& news)
– End to end “interaction & process analytics”
– Security and compliancy regulations
– Multi-channel strategy: portal and B2B are main channels – but not the only ones
(telephone, chat, social, email and for now paper based mail); perhaps mobile as well
• Traditionally, most applications are custom built with Oracle technology and
deployed on-premises
94. 94
Case:
the ultimate digital user experience
WebCenter
Portal
Service
Cloud
Mobile
Document
Cloud
Service
SOA CS
Message CS
Enterprise
IAM
API
Gateway
VPN
Service
Bus
SOA
Composite
BAM
Cloud
Events
BPM
Various
End User Groups
Enterprise
Database
Core
Business
Application
Enterprise
Documents
CRM
B2B Partners
95. 95
The first step in the Case of
the ultimate digital user experience
Service Cloud
Enterprise
IAM
VPN
Service
Bus
SOA
Composite
BAM
BPM
Various
End User Groups
Enterprise
Database
Core
Business
Application
Enterprise
Documents
CRM
B2B Partners
WebCenter
Portal
WebCenter
Content
Service
Bus
Multi-Channel
• Telephone
• Chat
• Email
• Portal
Call Center
App
97. 97
Case: IoT
• Collect physical measurements and
signals from the real world in real time
– Security Sensors, Traffic Flow Signals,
Biomedical Measurements, Weather Conditions,
Earth-Movement-Registration, Logistics Recordings,
• Gather, Filter, Analyze, Process signals to
data, information and findings
• Challenges:
– Availability – real time, 24/7, quick reaction required (sometimes, but very quick)
– Accessibility (from many different locations, many outside enterprise reach)
– Volume (and real time peak capacity)
– Latency (local data drop-off points and decentralized initial processing)
• Conditions
– Limited (initial) enrichment
– Eventual hand-over of findings to enterprise infrastructure and systems
99. 99
How to get going
with an Edge System on the cloud
• Implement the bridge between (API calls, navigate/deeplink, UI mash up)
– the various cloud services
– the final cloud services and the on-premises systems
– Also: network configuration to support the bridge
• Arrange for user friendly URLs – for end user User Interface systems
• Implement Identity & Access Management for internal and external users
– Integrate with on-premises IAM systems (replicate to cloud?)
– Single Sign On across cloud and from on premises to cloud
• Set up Cloud Ops – Operations for the cloud based systems & flows
– Oracle Management Cloud
100. 100
Summary
• Do not ask: how to get to the cloud
• Starting point is why?
Cloud fulfills a business need or provides a
business opportunity
– That is the driver and the business case justification
• Edge systems have common requirements, challenges and opportunities
– Many of which are dealt with by cloud based solutions
– The business case is quickly defined – using speed, capacity, flexibility, availability,
security, functionality and TCO
• Typical edge systems use cases include:
– B2B, Portal, Mobility, Silo-as-a-service (lift and shift)
• Other low hanging cloud fruit
– Development automation, Back up, Long term archive, Monitoring (real time analytics
on log files and operational metrics), BI and Tactical Analytics
• An initial investment is required: time, effort, frustration, learning curve
– Opportunity to be an early adopter and reap benefits quickly
101. 101
Overview
• Demo of some PaaS Cloud Services
• The Public Cloud from Oracle’s perspective
– ‘so you want to become a cloud provider?’
• Current Status of Oracle PaaS Portfolio
– What is out there, what is in preview and what is planned
– Two cloud product “flavors”:
on premises product offered from the cloud and pure cloud products
• Near future roadmap
• Why and how to get started in Oracle Public Cloud
• Discussion