►
Description
How do you move on-premises enterprise applications to a Software as a Service model? Using Kubernetes and Java Application Server Operators, Intris NV, an end-user, moved to the cloud without any overhead of re-design and re-development. In this session we will discuss options considered for migration and show how Intris is making use of Kubernetes, Kubernetes Operators and Prometheus.
Re-developing applications can be a costly endeavor both in time and skills. This session will be useful for software vendors looking to improve agility and cost-savings while leveraging existing skills and knowledge.
A
Like
to
thank
everyone,
who's
joining
us
today,
welcome
to
today's
CN
CF,
webinar
small
is
not
always
beautiful.
Moving
to
enterprise
applications
to
the
cloud
I'm
Geoffrey,
Sica
I'm,
a
senior
software
engineer
at
Red
Hat
and
a
cloud
native
ambassador
I'll
be
moderating
today's
webinar.
We
would
like
to
welcome
our
presenters,
Paul
Jenkins
product
manager
at
Oracle,
cloud
infrastructure,
cloud
native
services
and
24
tenten
co-founder
and
CTO
interests
a
few
housekeeping
items
before
we
get
started
during
the
webinar.
You
are
not
able
to
talk
as
an
attendee.
A
There
is
a
QA
box
at
the
bottom
of
your
screen.
Please
feel
for
you
to
drop
your
questions
in
there
and
we'll
get
to
as
many
as
we
can.
At
the
end.
This
is
an
official
webinar
of
the
CNC
F
and,
as
such,
it
is
subject
to
the
CNC
f
code
of
conduct.
Please
do
not
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct.
Basically,
please
be
respectful
to
everyone
all
of
the
participants,
presenters
and
peers.
A
B
You
Jeff
thank
you
for
everyone
and
for
joining
and
we'll
get
right
into
things
and
just
introduce
myself.
As
said,
my
name
is
Paul
Jenkins
I'm,
a
product
manager
in
Oracle
cloud
infrastructure,
working
on
a
developer
and
services,
part
of
the
organization,
and
that
is
I.
Look
after
kind
of
customer
contact.
B
B
Cd,
tooling,
that
I
worked
with
back
in
the
day
and
Magadan
today
when
I
first
started
programming,
then-
and
this
was
coding
sheet-
was
home
and
we
created
the
program
code
that
got
sent
off
to
a
agency
where
the
code
was
transferred
into
punch
cards,
those
punch
cards
within
loaded
into
this
hopper
and
they
were
upgraded
and
into
a
machine.
It
was
almost
exactly
the
same.
Is
that
one
and
then
we
were
able
to
start
and
compiling
in
running
programs,
and
we
went
we're
at
the
height
of
tech.
B
So
that's
kind
of
where,
where
I
started
and
I
think
safe
to
say
that
things
have
moved
on
a
little
bit
since
then.
So
what
what's
what's
really
happened
is:
is
that
the
wave
it's
the
process
of
development?
The
way
applications
are
designed
the
way
they're
deployed
and
what
they
run
on
has
changed
quite
a
lot
from
back.
B
So,
while
we've
come,
could
kind
of
a
long
way
from
the
top
left-hand
corner
in
the
in
the
18th
banks,
the
bottom
right
hand
corner
of
today
and
the
basic.
What
we're
trying
to
do
is
still
trying
to
deliver
business
funny
to
our
organizations.
The
fact
that
we're
using
different
techniques
and
technologies,
this
kind
of
doesn't
change
the
Hulk
whole.
B
I've
seen
lots
of
organizations
and
wanting
to
to
make
this
and
transition
and
there's
always
a
big
desire
for
this
and
to
make
a
really
big
change.
You
know
I
think
we've
all
seen
the
Dilbert
cartoon
stripper,
which
the
answer
to
everything
is
keeping
air.
These
people
aren't
quite
that,
but
these
are
absolutely
questions
that
you
know
when
we've
been
given
and
asked
to
go
and
talk
to
a
customer
and
say:
okay,
tell
me
how
I
want
to
go
completely
service.
How
do
we
do
DevOps?
B
We
get
that
question
so
often
what
about
serve
micro
services?
How
we
do
G
starts
a
live
song.
These
are
all
kind
of
big
desires,
but
it's
kind
of
symptomatic
of
organizations
wanting
to
make
that
that
meeting
to
the
cloud
which
many
are
kind
of
still
struggling
with
and
from
from
the
enterprise
space.
B
There's
a
lot
of
technical
debt
in
in
enterprise
systems,
and
it's
the
diversity
and
the
complexity
of
the
entire
stack
of
having
lots
of
different
hardware,
that's
being
used
through
different
programming
languages,
ways
of
integrating
and
accessing
between
systems.
That's
not
such
an
easy
thing
to
to
address
than
it
needs
to
need
some,
some
thinking
about
how
we're
going
to
address
that
diversity
and
the
complexity
of
the
stack
required
to
move
an
application
from
on-premises
into
the
cloud.
B
Piece
layering,
not
all
systems,
need
constant
change,
so
what
I'm
referring
to
here
is
there
was
a
few
years
ago,
gardner
came
out
with
this
concept
of
paste,
layered
applications
and
saying
that
vacations
changed
at
different
speeds,
depending
on
where
they
sit
in
the
sort
of
business
chain.
So
the
concept
is
there
doubt
that
that
the
bottom
is
you've
got
systems
above
record.
B
These
are
the
systems
that
you
just
have
to
have
in
order
to
be
running
a
business,
to
be
legal
or
to
be
compliant
and
just
to
function
above
that
there's
a
layer
of
system
what
the
core
systems
of
differentiation-
and
these
are
systems
and
processes
that
you
do
as
an
organization
that
differentiates
you
from
competition.
So
it
may
be
the
way
that
you
handle
customer
complaints
the
way
you're
going
through
customers.
Those
kind
of
unique
value
and
value
adds
that
you
as
an
organization
producing
it,
but
the
top
layer
is
the
insistence
of
innovation.
B
B
All
the
things
that
I'm
talking
about
when
we
talk
about
north
all
systems
need
constant
change.
I
was
not
longer.
I
was
speaking
to
a
city
over
an
insurance
company,
and
he
was
saying
that
you
know
they've
got
this
sort
of
digital
platform,
digital
transformation,
going
on
they're,
creating
mobile
applications
and
starting
to
look
at
and
to
deploy
micro
services
what
they
need,
they
still
need
and
to
make
their
delivery
cycle
a
lot
shorter,
so
they're
on
a
four
week
cycle.
B
They
were
trying
to
get
down
to
a
three
week
change
cycle
and
he
was
complaining
that
you
know
the
real
problem
is:
is
that
I
cannot
change
all
my
systems?
Quick
enough
that
the
the
policy
management
system
was
an
application
system
that
was
brought
in
from
commercial
supplier
and
they
can't
change
it
quick
enough
to
get
into
there
their
three
big
focal
when
we
actually
talked
a
little
bit
more
about
whether
that
system?
B
Why
would
that
system
need
me
to
change
so
much
and
after
we
had
a
talking,
he's
thought
about
it,
a
bit
he
said.
Well,
the
reality
is
that
every
term
we
do
do
make
a
change
to
that
system.
It
takes
months
to
roll
out
that
changes
and
educate
all
the
users
on
the
new
features
and
functions
of
that
so
well,
actually,
I
don't
want
it
to
change,
and
that
kind
of
bit
of
an
epiphany
moment
for
him
and
and
that's
when
it
comes
to
those
sorts
of
systems.
B
What
you
really
want
to
do
in
order
to
get
the
that
the
value
of
of
moving
everything
to
the
cloud
is
to
be
able
to
lift
and
shift
their
application
environment
from
an
on-premise
environment
to
to
the
plan,
you
don't
necessarily
need
to
change
it
and
to
get
the
value
out
of
moving
to
the
cloud.
The
other
reality
is
its
skills
or
that
have
you
know,
enterprise,
Java
applications
and
enterprise.
B
This
Java
servers
have
got
a
certain
skill
set
that
is
very
much
focused
around
the
development
of
those
applications
not
necessary
much
around
the
operation
of
those
those
systems.
So
there's
a
there's,
a
gap
in
what
the
organization
has
in
can
do
and
what
it
needs
to
be
able
to
do
if
they're,
making
that
transition.
B
That's
part
of
their
problem
is
that
they
have
Java
programmers
in
their
organization
at
a
great
Java
programmers.
But
all
they
want
to
do
is
be
Java
programmers.
They
don't
want
to
start
looking
at.
You
know
the
operational
side
and
working
in
different
two
structures
etc,
and
the
other
thing
that's
struck
them
was
when
I
took
them
just
on
a
quick
tour
through
the
office.
We
happened
to
get
a.
B
There
was
one
of
the
teams,
but
it
was
working
on
functions
at
the
time
were
having
a
big
huddle
around
trying
to
address
a
problem
that
you
know
there
was
half
a
dozen
staff
around
a
desk
and
looking
at
screens
and
discussion,
and
they
said.
Oh,
this
is
entirely
different
from
our
organization.
Our
developers
have
all
sat
down
in
their
cubicles
and
it's
all
silent
and
you
know
they're
just
working
on
what
they
do
and
checking
over
the
wall.
B
B
A
journey
that
seems
to
be
becoming
a
pattern
and
a
model
for
for
this
threat.
People
take
their
existing
applications
and
well
now
we
can
start
see
if
we
can
run
them
in
containers
and
doctor
being
a
very
popular
one
in
the
commercial
enterprise
space
and
then
start
realizing
that.
Well,
if
we've
got
the
more
of
these
things
that
we
did,
we
have
the
the
more
that
we
need
to
be
able
to
manage
them,
and
then
we
start
looking
at
keeping
eTI's
as
they
as
the
end
point
and
which
is
great.
B
But
and
when
we
talk
about
the
skill
sets
differentiated,
different
differences
that
we
mentioned
just
now,
then
they
need
they
need
help
in
moving
design
java
enterprise
applications
into
and
into
cuba
nettings.
So
what
we?
What
we
have
is
what
we
see
is
that
the
trends
are
moving
to
cloud
naturally
and
Humanities
is
preferred
deployment
platform
for
enterprise
durable
applications
is
something
that
we
see
in
something
we're
helping
customers
with
me,
something
that
we
are
supporting
and
working
to
try
and
simplify
the
deployment
of
those
application
on
to
keep
in
essence.
Why
is
that?
B
Because
a
they
can,
they
can
migrate
their
existing
applications.
Then
we've
got
an
environment
which
customers
can
then
use
as
a
path
to
get
to
micro
services,
to
things
like
hello,
Don,
sto,
etc.
To
be
able
to
do
that
and
start
to
then
have
an
environment
that
maybe
they
can
start
to
migrate
their
applications.
B
So
to
that
end,
what
what
we've
done
is
that
we've
released
kubernetes
operator
for
web
logic
that
basically
helps
our
customers
be
able
to
lift
and
migrate
their
application,
their
enterprise
applications
and
to
the
claim
now
what
that,
what
that
means
is
that
it
enables
these
organizations
to
make
use
of
their
existing
skills.
So
me,
as
a
Enterprise
Java
developer,
don't
necessarily
have
to
throw
that
out
the
window.
You
start
to
learn
something
new
from
day
one.
B
It
allows
us
to
focus
on
and
creating
and
managing
the
applications
that
we'll
use
to,
rather
than
having
to
worry
everything
about
running
and
operating
accumulated
cluster,
so
that
also
the
operator.
Then
it
understands
the
application
server
cluster.
It
depends
about
domains,
it
understands
how
to
scale
the
cluster
and
what
it
also
does.
It
makes
use
of
Keeper
Nexus
to
to
automate
the
life
cycle
of
the
operations
of
that
application
server,
and
it
also
allows
people
to
start
transition
into
modern
tool.
Change
that
that
we
looked
at.
B
So
what
we've
done
is
fully
open
sources.
We've
released
the
WebLogic
humanities
operator
that
basically
manage
the
lifecycle
operations
from
a
cuba,
Nettie's
point
of
view
that
understands
starting
stopping
an
application,
server
environment
to
automate
the
configuration
of
environment
and
supports
standards
and
humanities,
things
like
site
cards
and
custom
resources,
all
that
sort
of
thing,
so
it
can.
It
can
really
understand,
and
both
the
cuban
Etten
side,
the
things
and
operates.
Weblogic
say
it's
super
sourced
in
and
fully
supported
on
github.
B
C
So
we're
interests
and
we
are
an
independent
software
vendor
and
we
have
created
a
Java
EE
application
for
the
logistic
service
providers.
For
those
of
you
who
don't
know
what
that
is,
there's
forwarding
companies,
shipping
agents
warehouse
that
kind
of
stuff.
We
have
a
little
over
three
hundred
customers
and
the
interesting
part
is
that
they
ranged
from
two
users
to
the
largest
one
as
a
little
over
450
users.
So
it's
a
challenge
as
far
as
deployment
is
concerned.
C
We
are
also
having
an
embedded
software
license
with
Oracle,
and
this
is
important
to
know
why,
because
that
means
that
we
have
to
actually
install
all
the
Oracle
products
separately
for
each
customer.
So
we
cannot
actually
use
a
real
sauce
if
you
like.
We
also
are
using
agile
scrum
for
development
and
we
have
a
new
release
every
six
weeks
it
used
to
be
four
weeks,
but
I'll
come
to
that
problem
later
on.
We
are
not
the
biggest
company
we
have
as
a
development
team.
C
We
have
12
application
developers
and
we
have
another
team
of
four
that
do
mainly
integrations
by
integrations
I
mean
setting
up
PDI
and
spry
service.
Best
of
that
kind
of
thing,
because
in
logistics
there
is
a
lot
of
application,
integration
going
on
between
suppliers,
official
instances
and
so
on.
I've
tried
to
it's.
Maybe
a
bit
small
but
I've
tried
to
without
the
way
with
application
is
set
up
on
the
rep
logic,
and
that
means
that
we
have
actually
two
domains.
C
C
Whether
has
the
application
data,
of
course,
but
also
used
for
the
matter,
and
then
we
have
some
other
open-source
tools
used
like
Open,
Office
mail,
server
stuff,
like
that
that's
running
on
a
separate
server.
So
that's
the
application
and
a
small
introduction
and
now
I'll
demonstrate
my
voice
controlled,
slides
next
slide.
Please
both
wait.
C
So
what
are
the
challenges
we
run
and
run
into?
First
of
all,
is
we
focus,
as
Paul
mentioned
earlier,
more
on
application
development
and
really
less
on
deployment
and
operating
and
all
the
stuff
involved?
Now,
one
of
the
things
we
ran
into
frequently
is
that
there
is
a
mix
of
environments
to
deploy
our
application
on.
It's
usually
the
customer
that
decides
what
kind
of
infrastructure
he
has.
We
do
give
him
like
the
minimum
requirements
we
need.
C
They
don't
always
follow
our
and
Phi's
on
that
and
there's
a
they
can
be
both
on-premise
and
in
the
cloud
when
we
started
out
it
was
mostly
on-premise
all
exclusively
on
friends.
It's
only
in
the
last
two
three
years
that
we
actually
see
our
customers
being
interested
in
moving
to
the
cloud
before
that
logistics,
everybody
wanted
his
own
service,
his
data,
his
security,
that's
locally
changed
a
lot.
The
other
thing
we
noticed
is
that
the
performance
is
various
extremely
on
the
different
environments.
C
Even
though
we
have
the
same
Oracle
stack,
we
have
the
same
application
same
database.
We
still
noticed
that
with
some
customers
we
have
very
good
performance
and
way
of
the
customers
were
actually
very
bad
performance.
Well,
he's
always
discussion
and
a
lot
of
work
and
finding
out
what
exactly
was
the
cause
of.
It
was
the
case
with
setting
up
the
system
itself.
The
well
known
error,
please
do
not
use
a
virus
scan
on
your
database.
C
Foliage
deployments
was
also
a
problem
in
the
sense
that
we
did
have
scripts
who
are
as
most
as
much
as
possible
automated
deployment
because
of
the
variants
on
those
different
pictures.
Those
could
not
always
be
used
as
a
solution.
We
we
set
up
standard
cloud
environment.
We
had.
We
could
offer
our
customers
and
standards
environment
in
portal
clouds
that
already
I
changed
a
lot
in
the
sense
that
it
was
a
uniform
environment.
So
the
leaders
were
the
same.
C
We
have
the
same
CPU,
same
memories,
same
disk
storage
so,
and
that
gave
us
exactly
what
we
wanted,
namely
a
good,
predictable
performance.
The
other
thing
is
that
we
were
able
to
actually
standardize
all
the
deployments
now,
so
that
was
already
a
list
of
a
big
burden
on
our
deployment
team
which,
by
the
way,
is
only
about
four
people.
So
we
not
that
we
didn't
have
a
big
team
there.
C
C
Ok,
that
already
gave
us
an
answer
to
a
lot
of
anger
and
worries
about
having
a
performance
issue.
Now
we
faced
with
something
else,
and
that
is,
as
I
said,
we
have
a
new
release.
Every
six
weeks
it
took
us
eight
weeks
to
have
all
the
customers
to
have
the
new
release
deploy
to
all
the
customers,
and
that
is
something
that
we
really
set
out
to
do
is
that
we
really
want
all
our
customers
to
have
the
same
release.
C
C
The
new
release
ended
in
different
pots,
so
that
means
that
there
is
no
longer
and
downtime
required
at
a
customer
site,
which
is
a
great
benefit
because
part
of
the
problem
Wyatt
he
eight
weeks
to
install
every
customer
was
that
not
all
customers.
Well,
as
I
said,
none
of
the
customers
wanted
in
down
time
outside
of
the
office
hours,
so
we
will
always
limit
it
to
weekends
and
nights
so
also
benefit
for
my
deployment.
C
C
Fortunately,
there
we
could
make
use
of
the
Oracle
feature
called
addition
based
redefinition
that
man
that
could
practically
use
the
same
mind
the
same
way
of
working
in
the
sense
that
it
could
already
prepare
a
different
schema
in
the
database
and
by
putting
in
another
another
parameter
in
our
connect.
We
could
make
that
we'll
have
a
new
release
actually
make
use
of
the
new
schema.
C
What
also
benefits
is
a
better
use
of
the
resources
when
we
offer
the
cloud
environment,
as
I
mentioned
before
the
smallest
unit
we
could
offer.
Our
customer
is
one
compute
instance
for
those
customers
who
only
have
two
users.
That
is
a
bit
of
an
overkill.
So
by
using
humanities,
we
were
able
to
share
those
computer
resources
and
offer
our
smaller
customers
better
solution
and
also
I
think
already
mentioned.
It
also
was
the
fact
that
it
is
scalable.
C
So
that
means
that
if
we
see
that
some
of
the
manage
servers
have
a
bigger
workload
and
expected,
we
can
easy
scale
of
the
number
of
manage
servers,
for
instance,
for
the
key
services
and
the
nice
thing
about
this-
is
that
can
also
be
automated,
so
you
can
actually
go
in
measure.
The
command
of
memory
or
CPU.
Certain
port
is
using
managed
server
in
this
case
is
using,
and
if
you
see
that
it's
a
hundred
percent,
which
sometimes
happens
when
big
EDI
jobs
are
running,
you
can
actually
scale
up,
then
add
another
ports.
C
For
that,
as
also
mentioned,
is
the
other
big
benefit
is
that
it
is
available
as
well
in
the
front
as
on-premises.
So
that
means
that
we
can
further
uniform
make
standardized
our
way
that
we
deploy
our
application
next
slide.
Please,
so
is
a
simplified
schema
of
how
we
set
up
the
application
or
the
deployments
in
the
different
clusters.
So
we
have
three
notes
in
three
different
availability
domains
on
Oracle
cloud.
C
This
also
gives
me
added
benefit
and
we
agreed
with
Oracle
that,
if
we
with
every
customer
in
a
separate
namespace
that
they
would
see
this
as
a
separate
installation,
so
we
would
not
reach
our
meta
socialised
and
we
can
kind
of
modify
or
adjust
that
to
our
customers
needs
or
the
example
above
is
a
medium
customer
which
has
two
instances
of
the
master
in
the
service
but
master
per
in
the
enterprise
service
bus,
as
well
as
the
as
e1
e
OB.
I.
C
Sorry,
is
just
running
in
in
one
pot,
and
then
we
have
the
or
solution
for
the
smaller
customers
that
actually
only
have
one
instance
of
his
boss
and
his
reservist.
And
of
course
we
still
have
the
OB
I
for
the
documents
and
then
they,
the
bottom
I,
have
an
example
of
what
we
will
do
with
the
bigger
customers.
Although
there
we
choose
to
it
with
those
in
a
separate
closer
as
not
to
overload
all
the
rest
customers.
But
that
means
that
we
can
actually
use
this
solution
for
the
smaller
customers.
C
Instead
of
just
one
on
instance,
I
can
put,
we
haven't
tested
it
yet
how
far
we
can
go
with.
It
seems
that
we
can
easily
do
10
customers
on
a
3-node
solution.
The
other
thing
you
see
is
that
each
customer
has
its
own
PDB.
So
that's
a
private
database,
its
feature
of
Oracle,
and
that
is
running
on
a
database
cloud
service,
as
was
advised
by
Oracle
others,
but
also
in
literature.
It's
not
always
a
good
thing.
Put
your
database
in
a
docker
container
who
best
with
that
site
in
a
different
service.
C
Okay,
so
going
over
to
Cuba.
This
is
a
big
help,
but
it's
not
an
easy
walk
because,
as
Paul
mentions,
we
we
didn't
have
any
knowledge
of
underground
communities
and
it
is
a
big
chunk.
There
is
a
lot
of
stuff
available.
There
is
a
lot
of
decisions
to
make
on
how
to
do
things.
You
can
can
have
a
solution
set
up
in
a
different
way.
So
where
do
we
start?
Well,
as
also
mentioned,
we
didn't
have
any
experience
with
ops.
C
We
focused
really
on
application
development,
and
the
other
problem
is
that,
of
course,
setting
up
that
environment.
Is
you
also
want
to
monitor
and
manage
it
and
to
be
able
to
act
on
problems
and
if,
but
preferably
probe,
be
proactive,
so
X
before
a
problem
occurs.
The
solution
we
find
there
was
that
making
use
of
existing
tools
lifts.
One
thing:
I
learned
about
the
general
philosophy
of
Cuban
leaders
is
that
it
is
one
of
the
directions
is
make
it
as
simple
as
possible.
C
So
the
existing
tools
we
use
is,
as
mentioned
by
Renteria
by
Paul,
is
the
logic
humanities
operator,
which
really
does
a
bunch
of
things
that
otherwise
we
should
have
created
services
for
deployments,
jobs,
demons.
That's
all
those
things!
We
don't
need
to
do
it's
the
operator
that
takes
care
of
that
also
scaling
and
changes
its
taking
care
of
whiny
operator.
C
We
also
use
two
other
open-source
tools
from
Oracle
on
this
call
a
logic
deployment.
What
that
does
is
actually
it
helps
us
to
create
the
WebLogic
domains
not
only
created,
but
there
is
also
some
very
nice
features
like
actually
discovering
how
WebLogic
is
set
up
and
actually
creating
your
models,
so
you
will
be
able
to
create
a
new
domain
space,
also
the
possibility
to
update
your
domain
afterwards.
C
The
other
open-source
tool
we
are
using
is
the
Rapa
logic
image
to
name
already
says
that
one
is
actually
creating
your
token
images
for
you,
based
on
making
use
of
the
WebLogic
deployment
to
itself.
So
what
it
actually
does.
Is
it
loads
all
the
necessary
software
from
Oracle,
including
any
patches
you
want
to
apply
and
then
create
a
docker
file
and
execute
it,
and
that
docker
file
is
created
in
a
way
that
could
be
almost?
We
were
never
able
to
do
so.
It's
it's
actually
following
best
practices
or
Dawber.
C
So
that's
actually
used
at
the
moment.
We're
still
learning
a
lot
as
we
move
on,
but
the
nice
thing
is
it
both
of
these
things
almost
work
out
of
the
box,
so
that-
and
there
is
a
lot
of
documentation
available
thanks,
Lucky's,
okay.
So
this
is
a
very
brief
from
what
we
want
to
do
as
next
steps.
It's
just
some
topics
that
I
wanted
to
mention
is
the
first
one
is
its
micro
services
and
there
it
was
the
long,
a
question
on.
Should
we
go
for
micro
services
or
not
being
an
enterprise
application?
C
It's
it's
a
it's.
A
big
application
has
a
lot
of
features
and
functionalities,
but
it's
not
easy
and
certainly
my
opinion
time
consuming
to
transform
the
complete
application
to
micro
service.
However,
when
we
were
on
our
on
our
journey,
we
did
find
out
that
we
don't
have
to
actually
transform
the
complete
application
to
micro
service.
We
can
already
start
by
using
part
of
it
to
my
search,
one
of
them
that
we're
actually
at
the
moment
developing
is
as
I
mentioned.
C
We
are
using
VI
publishing
to
generate
documents
is
they're
using
the
bot
library,
which
is
actually
Java
libraries
and
for
the
VI
permission
and
put
those
or
make
those
available
as
a
micro
service
for
that
you're,
using
Caledon
as
a
tool
to
help
us
make
that
transition
to
micro
services
and
also
growl
a
VM
to
keep
that
image
as
small
as
possible.
Now,
the
by
having
been
experience
came
apparent
that
they
were
already
another
few
other
candidates
to
start
transforming
to
micro
services.
C
One
of
them
is,
we
have
a
workflow
management
system
and
one
of
the
things
that
the
system
needs
to
do
quite
often
and
which
take
some
resources.
It's
calculating
priorities
of
tasks.
That
was
also
a
very
good
case
where
we
saw
that.
Ok,
we
can
take
that
out
of
the
application
and
use
it
as
a
micro
service
same
as
generating
or
creating
EDI,
so
XML
messages
were
decent
magic
and
by
that
I
think
I
came
to
the
end
of
my
story.
B
Is
operated
that
helps
to
to
migrate
the
third
application,
but,
as
you
can,
you
saw
some
Tony
Abbott
Android
applications
have
a
lot
of
complex
interdependencies,
the
Brittany
monitoring
they
need
access
control
and
they
want
to
run
these
applications
in
in
a
in
the
same
kind
of
environment
that
you
would
want
to
start
developing
micro
services,
as
Tony
mentioned
so
to
the
bank,
and
what
we're
doing
is
to
is
to
build
out
the
environment
that
almost
the
same
as
what
Tony
talked
about.
So
we're.
B
Building
some
workload,
management
and
to
language
again
is
open
source
called
Verrazano
that
makes
use
of
underlying
infrastructure
management,
my
grantor
and
SDO
to
to
deploy
the
the
underlying
key
Panetta's
environment
and
were
pre-wiring
and
join
together.
The
monitoring
with
tooling
for
CI
CD
and
integrated
security
using
these
products,
and
it's
it's
a
an
opinionated
but
very
much
open
source
based
environment
to
help
the
deployment
of
these
enterprise
applications
as
they
are
onto
kubernetes,
running
and
on-premise
public
cloud
and,
of
course,
Multi
multi
cloud.
B
So
were
building
this
up
and
to
build
this
kind
of
picture,
which
is
while
the
operator
in
human
essence
is
great
to
be
to
be
successful.
You
have
to
have
a
completely
environment
which
to
support
those
those
applications,
and
it
also
gives,
as
Tony
mentioned,
clean
the
environment,
to
be
able
to
lift
and
shift,
and
these
traditional
enterprise
applications
to
the
to
the.
That
means.
You
don't
have
to
someday
one
REE
architect
and
it
gives
the
environment
with
hello,
darling,
sto,
and
these
are
the
environments
to
be
able
to
start
to
develop.
B
B
A
Yep
thanks
Paul
and
Tony
for
a
great
presentation.
Well,
we
do
have
some
time
for
some
questions
and
I
know
there.
A
couple
queued
up
that
I'll
get
to.
If
you
have
a
question
that
you
would
like
to
ask,
please
drop
it
into
the
Q&A
tab
at
the
bottom
of
your
screen,
we'll
get
to
as
many
as
we
have
time
for
so
first
question,
which
type
of
WebLogic
domain
configuration.
Do
you
run
in
prod
domain
image
in
home
or
domain
home
on
TV?
C
Okay,
I
guess
that's
questions
to
me.
We've
chosen
for
the
domain
language
in
in
hopes
not
on
the
persistent
volume
and
the
reason
for
that
is
it's
much
easier
if
you
want
to
connect
it
to
your
CI
CD.
So
if
the
moment
we
got
a
new
docker
image
with
the
WebLogic
domain,
it's
it's
just
easier
to
manage.
C
A
B
A
B
A
A
C
A
A
A
A
B
Foundation,
own
approaches
that,
if
micro-services
and
being
predominantly
stateless
I
know
you
don't
have
to
be
but
I
think
that's
one
of
the
areas
that
you
know.
These
applications
that
Tony
was
talking
about,
rely
quite
heavily
on
state
and
state
management.
So
they're,
not
all
necessarily
a
great
thing,
just
to
be
able
to
break
down
and
say
what
we're
just
going
to
use
a
service
machine.
We
completely
replace
that
because
that's
quite
an
undertaking.