6Reinventing Oracle Systems in a Cloudy World (Sangam20, December 2020)

6Reinventing
Oracle Systems
in a Cloudy
World
Sangam 20, December 2020
Lucas Jellema, CTO & Architect AMIS | Conclusion

Publiek
Once upon a time
A Dutch Company
Their on premises
data center (in
Germany)
high incident rate
not modern
legacy
business critical
custom software
end of scale
little expertise left
on applications and tech stack
fragile
no tests, no specs, no docs
expensive: high TCO
high technical debt
no evolution
monolith
unattractive technology stack
for young talent
unsupported
inflexiblesecurity-challenged
business  IT gap
old

Publiek
Cloud Promises
Latest and Greatest
Rapid Innovation
Pay for use only (no CAPEX)
Low TCO
Super Secure
Fully managed
Limitless scalability
Automation
Fine grained cost control
The Moon

Publiek
Once upon a time is … about now
• They have 25+ years Oracle technology stack and staff expertise
• 100s custom applications (Forms, Reports, APEX, Pro*C, PL/SQL, ODI, SOA Suite)
• dozens of production databases = business critical
• outsourced most of Ops and much of Dev
• flirts with iPaaS, low code, microservices, mobile devices
• Unhappy with IT
• slow, restricting, expensive, old, fragile, not innovative,
customer facing (customer frustrating)
• they associate Oracle with their current IT state of affairs
• They have embarked on a cloud transformation:
• Azure is their preferred IaaS and PaaS cloud
• they expect a hybrid and multi-cloud landscape
with several SaaS offerings, on premises systems and 3rd party PaaS

Publiek
Cloud

Publiek
IaaS
IaaS
Latest infrastructure
Automation: Programmable /
Infrastructure as code
Dynamically Scalable
Secure
Distributed (fail over locally
and regionally)
Pay for use
Rapid take-off

Publiek
IaaS
PaaS
PaaS
Fully Managed services
Instant ramp-up
Highly Available
Always Latest and greatest
platform functionality
Dynamically scalable
Serverless
Enterprise grade services for
start ups (pay per use)
Monitoring, logging,
automation, security, audit,
events, … out of the box

Publiek
IaaS
PaaS
SaaS
SaaS (COTC)
Fully Managed
Fully Functional
Good Practices
Configuration & Data Load,
Implementation
Integration (SaaS
Enablement)

Publiek
IaaS
PaaS
SaaS
Cloud
Multi Cloud
Public Cloud on Premises
Vendor Lock-in
Network Latency
Data Egress cost
Physical location of cloud
data center (& laws)
Strategic relation cloud
vendor

Publiek
Cloud gives pause
• Rethink
• Reset
• Reject
• Reflect
• Reconsider
• Respect
• Rearchitect
• Remember
• Remind
• Renovate
• Refresh
• Revitalize

Publiek
6R
IaaS
PaaS
SaaS

Publiek
6R - Retire
IaaS
PaaS
SaaS
Decommission – either
instead of or following
a migration to the
cloud

Publiek
6R – Retain (and Refurbish)
IaaS
PaaS
SaaS
Not (yet) to cloud. Latency or special
hardware could be a consideration;
also: application life cycle state.
Make sure to do | consider
technical upgrade on prem (of hardware,
OS, platform, libraries, tools)

Publiek
6R – Rehost (and Refurbish) aka Lift & Shift
or: Move and Improve
IaaS
PaaS
SaaS
Run systems as-is on cloud
based, automated
infrastructure; no changes in
platform (except upgrade) and
application

Publiek
6R – Replatform (aka “Lift, Tinker and Shift”)
IaaS
PaaS
SaaS
Leverage (more) cloud capabilities
without substantially changing the
code and architecture of applications
– but with some optimizations and
changes in configuration. For
example: fully managed services
(“autonomous”)

Publiek
6R – Refactor & Rearchitect
IaaS
PaaS
SaaSFundamental changes to
architecture, code base, data model
and technology stack in order to
benefit from cloud to the fullest
(managed services and cloud native)

Publiek
6R – Repurchase (aka Drop & Shop)
IaaS
PaaS
SaaS
Replace an application (bespoke or
COTS) with a SaaS offering (COTC)
– typically including data migration,
(re)implementation, integration and
custom complements to provide
features lacking in SaaS

Publiek
6R
IaaS
PaaS
SaaS
Retire
Retain & Refurbish
Repurchase
Refactor
Replatform
Rehost
IaaS
PaaS
SaaS

Publiek
Considerations when deciding on 6R and migration plan
• Business Roadmap
• Staff (knowledge, experience, ambitions, state of mind)
• Licenses & Support
• Load on systems (patterns & peaks – and flatlines)
• Technical state (of hardware, infrastructure, technical components)
• Accounting and finance - TCO, depreciation, IT budgeting, cost allocation
• Innovation (two-pace)
• Network Latency (embedded software, real time equipment control, IoT Edge)
• Security and Regulations & Legislation – what is mandatory and restricted
• Strategic: AWS = Amazon == Retail; AliBaba = China, <many> == US
• Architecture Roadmap and Principles
• Offer (of the day)
• Migration
• cost, effort, time, requirements, impact
• dependencies (access, latency), clustering

Publiek
High level comparison of R-implementation
Effort Risk Agility
(non-functional
& functional)
TCO
reduction
Retire low low zero very high
Retain low medium low low
Rehost medium medium medium medium
Replatform high high medium high
Refactor very high very high very high very high
Repurchase high very high high high

Publiek
Pharmaceutical

Publiek
6Remember
• 6R is about applications
• and data, platform components, technical building blocks, tools
(development, test, CI/CD, monitoring, operations), procedures and staff
• Reorganization of applications and components should be considered
• consolidation and splitting off (preferably prior to migration)
• You will not migrate everything at once
• cater for hybrid environments (multi cloud and on prem)
and a prolonged transition period
• The way IT services are charged to the business
and costs are allocated can play an important role
• cloud makes fine grained cost allocation a possibility
(usage based); ideally matched by fine grained
generated value monitoring
Leave behind!

Publiek
Applications and Technology Components [no longer] in use
Applications
Technology Platform
Oracle Database
Applications
Features
pages,
reports, jobs,
service, API
Data – hot |
lukewarm |
cold; GDPR/
PII status Java EE
JMS, JSP/JSF,
EJB, JPA, JTA,
JAX-WS
Oracle
WebLogic
Oracle
SOA Suite
Windows 7
RHEL 5.x
Oracle
Forms
Oracle
APEX
Mendix
.NET
Oracle
Reports
Docker
Components
modules,
libraries,
packages,
tables
MySQL
ODI

Publiek
Ce ci

Publiek
Ce ci
Ceci n’est pas

Publiek
Oracle Database
• Is much more than just a relational store of data
and SQL query engine
• Application Platform
• PL/SQL
• Stored Java
• MLE (multi language engine)
• Embedded PL/SQL Gateway, ORDS
• APEX
• Oracle Database features
• Audit
• Virtual Private Database
• Edition Based Redefinition
• Flashback
• Spatial and Graph
• Advanced Analytics and Machine Learning
• …

Publiek
6R with Oracle Database
IaaS
PaaS
SaaS
IaaS
IaaS
PaaS

Publiek
Retire Oracle Database
IaaS
PaaS
SaaS

Publiek
Retain (and Refurbish) Oracle Database
IaaS
PaaS
SaaS
Clean Out unused, Upgrade (to 19c LTS),
(De) Consolidate, Polish to make Shine
(leverage now free Advanced Analytics,
Spatial, Graph), Data Life Cycle
Management

Publiek
Rehost Oracle Database
IaaS
PaaS
SaaS
Run Oracle Database on IaaS
(Bare Metal, VM, Kubernetes);
benefit from (large, flexible)
scale and managed infra.
Refurbish (upgrade to 19c, …)

Publiek
Replatform Oracle Database
IaaS
PaaS
SaaS
PaaS
Same architecture,
same code and
database design –
different RDBMS
PaaS
Same architecture,
same code and
database design –
different RDBMS
Same architecture,
same code and
database design –
different RDBMS Same Database
platform –
now fully managed
Same Database
platform –
now fully managed,
serverless

Publiek
Refactor (Rearchitect) Oracle Database
IaaS
PaaS
SaaS
Substantially rethink the design and solution
- redesign data model, leverage PDBs,
introduce non-relational data, apply
architecture concepts (microservices, event
sourcing, CQRS), introduce additional data
stores (NoSQL, lake, blockchain, ..)

Publiek
Repurchase (Oracle Database)
IaaS
PaaS
SaaS
Replace an application using an
Oracle Database with a SaaS offering
(that includes its own datat store);
data needs to be migrated into the
SaaS platform, integration and custom
applications are likely needed to fully
enable the SaaS.

Publiek
Multicloud
IaaS
PaaS
SaaS
IaaS
IaaS
PaaS
Public cloud on
private premises
PaaS

Publiek
6Reinventing Oracle Database
IaaS
PaaS
SaaS
PaaS
IaaS
IaaS

Publiek
Cloud Transformation – Architecture Guidelines
• Managed PaaS over IaaS
• and FaaS over CaaS over VM over Bare Metal
• N/N-1 – only latest [long term] supported version
• Standard Building Blocks for Platform Components
• Pay per use, only use what and when is required
• scale down and switch off whenever possible
• Automation and Infrastructure as Code (no hands touch infra)
• provisioning & deployment, monitoring & notification
• Data Compliance (such as GDPR)
• Fine Grained Cost Allocation
• Appropriate availability and disaster recovery
• multi region for mission critical, at least multi availability “unit”
• Each Bare Metal Server | VM | Container | Function has a single purpose

Publiek
Decision Tree
• 21c

Publiek
Rehost
Replatform
application
PL/SQL
logic?
Migrate relational
DBaaS Azure
Up
grade
to
19c
Azure DBaaS
relational (SQL
Database PostgreSQL)
Oracle Database
on Azure IaaS
Oracle
Autonomous
On Prem Oracle
Database
Azure DBaaS
non relational
(CosmosDB, Redis)
Migrate managed
DBaaS Azure
Rela-
tional
data-
usage ?
Refactor
application Azure Managed
PaaS
Oracle
specific
DB-
features
?
PL/SQL
too
complex
?
Replatform logic
Migrate to
PostgreSQL
SaaS
Modify
App/DB logic
Modify
App/
PLSQL
Modify
DB
Logic
Reconstruct
Application
Satsfies
conditions
for
OCI Auto-
nomous
OCI auto-
nomous
provides
bonus value
Repurchase
Retain Retire
application
repurchase
retire
Applicatons
independnt
Oracle?
version ==
19c?
Upgrade
Possible?
Forms,
APEX,
COTS
AQ, EBR,
Flashback,
XMLDB, Text,
HTTP, Application
Context, VPD,
Stored Java, …
Consolidation of
multiple databases;
Split up of database
into multiple
Preparation
for automated
migration of
PL/SQL
because of cost, risk,
duration, fitness for
automated migration
Do the applications
access the database over
JDBC/ODBC and SQL?
Or through stored
procedure calls or with
REST API calls?
No applications
that are not 19c
ready / or use DB
features
deprecated in 19c?
No direct access to OS,
file system, network; no
dbms_pipe, stored java,
no log miner, WM,
sharding, …
Added value autonomous from much
lower ops costs and admin effort (< 10%
DBA) & dependence on specialist; also
more and earlier features; however
higher cloud-usage-cost, introduction of
OCI and the connect OCI  Azure
Consolidation of
multiple databases;
into mulitple
Consolidation of
multiple databases;
into multiple
Consolidation of
multiple databases;
into multiple

Publiek
Oracle Database
• Explore the starting point
• Which release (11gR2, 12cR1, 12cR2)
• Which edition (XE, SE2, EE)
• Options?
• Advanced Analytics, Graph and Spatial
• Partitioning, Compression, In Memory, Multitenant, Database Vault,
Advanced Security, Label Security, Real Application Testing, Data
Masking and Subsetting
• RAC, Active Data Guard
• Hardware?
• ODA, Exadata, “regular”
• Interactions from within Database with the environment: OS, File System,
Network, other databases (links, gateways)

Publiek
Using any of these?
• utl_file
• utl_http, utl_tcp, utl_smtp
• database link
• dbms_epg
• dbms_scheduler, dbms_job
• external procedure
• external table
• stored Java
• DIRECTORY
• LONG and LONG RAW

Publiek
ReplicationETL

Publiek
45
versi
on
==
19c
?
Upgr
ade
is
possi
ble?
Up
grad
e to
19c
Oracle
Database 19c
on Azure
IaaS
Oracle
Autonomous
Database
On Prem
Oracle
Database
SaaS
Modify
DB &
App
Logic
Satsfies
conditions
for
OCI Auto-
nomous
OCI auto-
nomous
provides
bonus value
Oracle
Database
< 19c
on Azure
IaaS
Upgrad
e to 19c
Optionally/preferably
upgrade to Oracle
Database 19c and move to
multitenant architecture
(with 1-3 custom PDBs)–
depends on roadmap
Looking at technical
limitations in
applications or
limitations in
business (budget,
planning)
Consolidation of
multiple databases;
into multiple
Consolidation of
multiple databases;
into multiple
Added value autonomous from much lower
ops costs and admin effort (< 10% DBA) &
dependence on specialist; also more and
earlier features; however higher cloud-usage-
cost, introduction of OCI and the connect OCI
 Azure
Upgrade to Oracle Database 19c
and move to multitenant
architecture (with 1-3 custom
PDBs)
Upgrade to Oracle
Database 19c and move
to multitenant architecture
(with a single custom PDB)
Repurchase
application
Retain /Retire
application

Publiek
6R Oracle SOA Suite
• The Dutch company also runs a
number of integration scenarios and
publishes WebServices & APIs
• It uses SOA Suite & OSB
• 11g and 12.1.3
• It has done some work
with Dell Boomi
• What is the 6R verdict on
its Oracle based integrations?

Publiek
6Reinventing SOA Suite
IaaS
PaaS
SaaS
PaaS
IaaS
IaaS
SOA Suite VM
image from
OCI Marketplace
on OCI Compute
SOA Suite installed
in VM or bare metal
or on AKS (just like
On Prem)
Oracle Integration Cloud
(with on-prem agent &
SOA Suite connector)
SOA Suite with
Kubernetes Operator on
OCI Kubernetes Engine
Azure Cloud Native
integration (functions, API
Management, connectors,
Logic Apps, Data Factory, …)
SOA Suite – upgrade to
12.2.1.4 (and 14.1.2);
with OIC adapter;
possibly run on K8S
OCI API
Gateway
OCI Cloud Native
(Functions, Streaming,
Events, …)
OCI Data Integration for
ETL style data pipelines
Oracle Integration Cloud
(with on-prem agent &
SOA Suite connector)
SOA Suite VM
image from
OCI Marketplace
on OCI Compute

Publiek
Conclusion
• 6R is triggered by the cloud
• but should be considered periodically at all times
• Decisions are made per application, data set and per technology component
• and per feature, per data object, per server and per technology instance
• Not deciding to make a move is also making a decision
• that requires arguments and justification
• The 6Roadmap will need continuous refinement
• Knowing the current situation is crucial for planning and decision making
• which technology component for which applications and which data sets used
for which business purposes – that will evolve in which way?
• what is the generated business value and therefore the justifiable TCO

Publiek
Conclusion
• Cloud is not an easy solution for the big problems
• it can quickly help with scale, security, focus on business value, automation,
innovation, TCO, and with starting the right discussions
• it does not add agility to existing business critical applications and teams
• and adopting the cloud is not a trivial operation
• Ce ci n’est pas un database (c’est bien plus qu’un database)
• A hybrid landscape (cloud – multicloud - on prem) is likely to exist for a fairly long time
• Secure, affordable network connections between cloud(s) and on prem
• Some form of data replication is to be expected
• Integration flows - streaming, event-based and batch ETL-style –
are required to tie the environments together
• There is no excuse for not starting your cloud journey right now
• except if you are already on your way – then have a safe journey!

Thank you
for your attention
I hope
this was
useful
lucas.jellema@amis.nl | technology.amis.nl | @lucasjellema | lucas-jellema

6Reinventing Oracle Systems in a Cloudy World (Sangam20, December 2020)

More Related Content

What's hot (20)

Similar to 6Reinventing Oracle Systems in a Cloudy World (Sangam20, December 2020) (20)

More from Lucas Jellema (20)

Recently uploaded (20)

6Reinventing Oracle Systems in a Cloudy World (Sangam20, December 2020)

Editor's Notes