►
Description
Tim Ellison- Java CTO at IBM
---
JakartaOne Livestream Cloud Native for Java (CN4J) is a one-day virtual conference for developers, engineers and technical business leaders with the focus of building enterprise Java on Kubernetes.
This virtual event is a mix of expert talks, demos, and thought-provoking sessions focused on enterprise applications implemented using open source vendor-neutral Jakarta EE and Eclipse MicroProfile specifications on Kubernetes.
A
Can
you
hear
me
I
heard
some
echo
on
my
end,
all
good
okay,
fantastic
just
want
to
make
sure,
because
I'm
kind
of
suddenly
got
confused
because
I
got
the
delay
of
a
few
seconds
and
then
my
voice
again.
So
anyways
welcome.
Welcome
and
I
just
wanted
to
kind
of
give
everyone
a
little
bit
of
a
heads
up
in
terms
of
what
we're
preparing
before
Tim
takes
over
and
starts
talking
about
the.
A
Familiar
that
we're
trying
to
run
the
live
streams
as
as
much
as
possible,
particular
now
in
the
new
era
that
were
approaching,
which
is
you
know,
pandemic
situation,
and
most
of
us
will
be
welcoming
communication
online.
So
heads-up
about
the
other
Jakarta
one
live
streams,
so
one
is
being
prepared
for
September
2020
and
it
is
going
to
be
our
annual
big
Jakarta.
One
live
stream.
If
you
remember
we
had
one
last
year
and
then
and
before
that
we
are
working
on
preparing
Jakarta
one
live
stream
Brazil.
A
So
this
is
going
to
be
a
very
similar
to
the
one
that
we
prepared
for
the
Japan
and
it
was
in
Japanese,
so
the
Brazil
one
will
be
in
Portuguese
and
please
watch
out
for
that.
Here
are
the
links,
but
I
will
share
that
with
you
later
as
well
and
on
the
social
media,
so
not
to
take
too
much
all
from
Tim's
time.
I
would
like
to
invite
Tim,
and
so
he
can
tell
us
that
about
the
run
times,
is
it
evolution
or
revolution
so
Tim?
If
you
want
to
take
it
over
okay.
B
Thank
You
Tanya,
and
let
me
just
go
to
display
mode
here
now,
so
hopefully
everybody
can
see
these
charts
and
I
just
wanted
to
echo
Tanya's
welcome
yeah.
This
is
really
extraordinary
times
for
everybody.
So
the
fact
that
we've
got
such
a
good
number
of
people
here
for
the
start
of
the
Jakarta
one
live
stream
I
think
is,
is
really
encouraging.
So
thank
you
for
joining.
This
is
a
really
exciting
time
in
cloud
native.
B
It's
exactly
the
right
moment
to
be
discussing
these
sorts
of
new
technologies,
because
technology
is
changing
very
rapidly,
we're
all
learning
how
to
adapt
as
we
work
from
home
or
other
places
and
eventually
get
back
into
into
our
business
settings.
But
business
is
changing
and
the
technology
will
be
changing
around
us
and
to
address
that.
So
what
I
thought
I'd
do
today
is
address
some
of
the
sort
of
non
technical
challenges
around
cloud
native
runtimes
and
cloud
native
Java
in
particular.
B
It
also
means
scalability
so
again,
when
the
business
demands,
change
and
change
so
rapidly,
we
can
see
a
surge
or
a
diminishing
of
demand
upon
the
business
in
different
areas.
Again,
we've
seen
this
absolutely
in
terms
of
the
pandemic
in
which
we're
all
living
at
the
moment.
There
is
certain
aspects
of
our
society
at
the
moment
which
are
putting
large
strains
on
the
computer
systems
that
we
built
years
ago.
They
have
to
be
able
to
scale
up
and
being
part
of.
B
The
cloud
gives
us
that
ability
to
scale,
but
likewise,
where
the
demand
has
it
drops
off
dramatically,
we
need
to
be
able
to
scale
it
back
and
not
be
spending
money
on
infrastructure
and
resources
where
they
aren't
required
for
the
moment
to
support
our
business.
And
thirdly,
I
would
claim
that
being
cloud
native
is
all
about
your
ability
to
adapt
to
those
changes
in
the
business
environment.
B
Having
a
large
established
business
is
no
longer
an
assurance
and
that
it
used
to
be
new
nimble
companies
will
come
along
into
the
market,
can
quickly
establish
a
new
and
innovative
idea,
or
a
very
convenient
way
of
operating.
That
hasn't
been
done
before
that
can't
be
provided
by
these
large
companies,
and
so
that's
why
everybody
has
to
become
adaptable
and
able
to
change
very
quickly.
B
So
with
these
kind
of
business
drivers
in
mind,
the
question
is:
why
do
we
need
to
modernize
our
existing
applications
and
we've
kind
of
spoke
a
little
bit
about
this
at
the
moment?
But
if
we
look
at
the
technology
around
it,
our
ability
to
modernize
to
adapt
to
those
business
drivers
can
be
somewhat
limited
by
the
technology
and
the
architectures
that
we
currently
have.
So
it
could
be
the
case
that
the
architecture
that
we
built
these
large
systems
around
has
got
some
limitations
about
the
ability
to
add
new
features
very
quickly
and
deliver
them.
B
But
it's
also
the
way
in
which
we
organize
our
teams
within
the
organization,
which
also
has
got
some
inherent
process
to
it,
and
perhaps
that
process
also
has
some
limitations
in
our
ability
to
deliver.
So
we're
not
only
talking
about
the
technical
changes
of
moving
to
a
cloud
native
around
time,
but
also
the
organizational
changes
will
be
required
and
I
think
those
two
things
really
do
have
to
go
hand
in
hand.
B
So
it
comes
back
to
it's
kind
of
two
schools
of
thoughts
as
to
how
we
can
address
this.
These
business
challenges
and
if
we
look
at
the
two
sort
of
extremes,
one
extreme
would
be
to
say
well
we're
going
to
rewrite
our
existing
systems
based
upon
the
new
technology
that
we've
got
now.
Obviously,
that's
a
very
high-risk
strategy,
because
it's
going
to
be
highly
disruptive
to
the
business.
Whilst
we
do
that
replacement-
and
it
also
requires
us
to
build
new
skills
very
rapidly.
B
B
We
could
make
a
disease
we're
going
to
just
write
new
systems
using
these
few
frameworks
and
technologies
and
integrate
them
into
the
existing
systems.
That
again,
it's
going
to
require
very
careful
planning
not
only
in
the
technology
that
we
use,
but
in
the
way
that
we
operate
as
teams
as
well.
At.
B
Can
just
claim
that
we're
going
to
incrementally
tweak
the
systems
that
we've
got
and
try
and
add
in
the
agility
and
the
changes
to
our
systems
that
exist
today.
That
kind
of
tends
to
build
up
very
large
bodies
of
spaghetti
code
complexity
for
the
ability
to
make
any
changes
in
the
future,
and
we
kind
of
really
there
are
deferring
and
building
up
a
technical
debt
of
any
revolutionary
type
of
change
that
we
need
to
be
able
to
enact
if
someone
was
to
come
along
and
disrupt
our
area
of
business.
B
B
So
it's
when
we're
talking
about
modernizing
existing
systems,
we're
talking
about
taking
existing
technology
and
adapting
it
to
modern
business
and
organizational
changes,
and
our
existing
systems,
which
we
often
tend
to
call
legacy
systems,
are
the
ones
that
got
us
where
we
are
today.
That's
our
investment,
that's
where
our
skills
lie,
so
we're
not
going
to
throw
that
away.
That's
not
yeah
legacy
is
not
the
dirty
word.
Java
systems
are
still
powering
businesses
the
world
very
successfully,
and
we
want
to
enhance
those.
B
It's
going
to
require
a
kind
of
blended
adaptation
of
existing
technology
as
you
move
forward
into
a
cloud
native
world.
So
so
the
goal
is
to
complete
your
modernization
with
a
maintainable
and
extensible
system
that
you
can
deploy
and
manage
at
the
pace
that
the
business
is
current
and
future
needs
within
the
capability
of
the
skills
that
we've
got
out
there
within
the
business.
B
B
Now,
if
we
turn
to
Java
specifically
Java
is
you
know
a
key
enterprise
skill
as
I
mentioned
earlier?
This
is
the
place
where
we've
got
our
investment,
and
so
there
is
a
really
strong
motivation
to
take
Java
with
us
on
this
journey.
As
we
move
to
cloud
modernization
there
are,
there
are
multiple
dimensions
which
we
can
look
at
job
as
role
in
application.
B
Modernization
we've
got
modifications
to
the
runtime
implementation
itself,
so
that
is
its
ability
to
adapt
to
to
changes
in
those
architectures,
as
I
spoke
about
earlier,
and
also
the
environment
insurance
is
the
Java
implementation
is
aware
of
containers
and
all
that
the
the
JIT
is
available
as
a
service
to
share
across
multiple
deployments,
Java
changes
by
providing
us
with
new
api's
and
capabilities
so
that
developers
have
got
new
technology
to
draw
upon
as
they
build
in
these
new
architectures.
So,
for
example,
you
know
micro
profile
and
Quercus.
B
Another
of
talks
later
today
from
Roberto
who's,
going
to
talk
a
little
bit
more
about
those
specifically
they're
offering
new
features
and
functions
which
are
going
to
be
available
to
Java
developers
which
are
relevant
in
that
cloud
environment
and
there
are
tools
available.
Who
can
that
can
have
a
look
at
an
existing
system
and
tell
you
the
suitability
of
moving
it
into
that
cloud
environment
within
those
new
api's
and
give
you
some
positive
feedback
about
those
as
well?
And
then,
as
we
modernize
Java
again?
B
B
So
if
we
look
at
the
modernization
journey
for
Java
I'd,
like
to
kind
of
break
it
down
into
three
different
types,
we've
got
just
the
Y
Kali.
You
know
the
lift
and
shift
to
cloud,
that's
taking
a
large
monolithic
application
and
moving
it
on
to
the
cloud
platform,
the
next
layer,
maybe
to
start
to
run,
applications
in
containers
and
deploying
containers
within
the
cloud
environment.
B
B
Even
if
you
just
do
that,
simple
lift
and
shift
you'll
get
some
advantages
of
Java,
realizing
that
it's
running
in
the
cloud
so
that
you
can
really
deliver
on
that
on
those
cost
advantages.
So
having
a
cloud
aware,
Java
is
certainly
relevant
even
in
this
type
of
model,
but
it
has
a
relatively
low
impact
on
your
ability
to
deliver
that
business
value,
you're,
reducing
your
costs
but
you're
not
getting
the
full
benefit
of
the
ability
to
deliver,
updates
to
your
application
very
quickly.
B
The
massive
sorts
of
things
which
will
come
with
different
styles
of
migration
to
cloud
so
I
spoke
about
containerization
of
applications
as
well.
This
is
going
to
have
a
bigger
impact
on
the
organization,
so
in
these
cases,
as
you
containerize
applications
to
deliver
it
into
a
cloud
environment,
the
developers
need
to
start
to
learn
about
the
additional
constraints
of
running
in
containers
such
as
immutability.
B
The
development
team
will
be
taking
on
more
responsibilities
that
they
would
typically
have
deferred
to
the
operations
team.
So,
for
example,
controlling
the
time
on
which
software
is
updated
within
containers
which
may
previously
being
part
of
the
operational
scope,
they
will
now
be
deferred
to
developers
to
choose,
as
they
just
deliver
a
container
out
into
the
environment,
which
leans
and
the
operations
team
become
responsible
for
delivering
a
standardized
platform
provider
for
running
containers.
B
That's
the
logging
and
the
monitoring
managing
secrets
that
are
flowing
through
through
the
cloud
system
and
security,
etc,
and
there
are
the
DevOps
team-
will
typically
be
doing
infrastructure
as
code.
So
here
we're
getting
into
the
ability
to
to
write
code
to
define
the
environment
through
the
ansible
through
again
kubernetes
structures
that
allow
for
this
full
level
of
optimization.
That
has
a
bigger
impact
on
your
business
now,
because
the
developers
are
much
closer
to
their
ability
to
update
containerized
applications
and
deliver
that
straight
through
and
then
I
mentioned
micro
services
and
functions
again.
B
This
is
this
is
not
a
goal
per
se
to
be
cloud
native.
This
is
an
architectural
style
which
is
suited
to
the
environment,
so
you
know
I'm
not
advocating
that
people
go
off
and
completely
rewrite
existing
applications
as
a
bunch
of
micro
services
that
may
not
be
appropriate.
But
if
you're
in
that
cloud
environment
then
having
access
to
the
frameworks
which
allow
you
to
build
micro-services
functions
and
bring
containerized
applications
into
the
cloud
gives
you
a
much
broader
set
of
tools
on
which
to
address
your
business
challenges.
B
If
you're
building
micro
services,
it
gives
you
the
ability,
as
a
DevOps
team,
now
to
decrease
the
scope
of
the
releases
that
you're
making.
So
we've
talked
about
kind
of
a
platform
and
the
environment
on
which
the
DevOps
team
can
be
developing
code
and
deploying
it
out
into
the
cloud
by
choosing
micro
services.
We
have
the
ability
to
decrease
the
scope
and
so
have
a
much
faster
turnaround,
and
this
is
where
we
start
to
get
the
benefits
of
the
agility
and
the
scalability.
B
B
Is
well-placed
to
deliver
on
all
of
these
fronts?
People
will
be
at
different
stages
in
their
journey
as
they
move
to
cloud
native,
and
none
of
them
are
any
better
than
any
other.
That's
kind
of
a
message
I
wanted
to
get
across
today
is
that
you
know,
while
it's
trendy
to
be
completely
reactive,
that
this
may
not
be
appropriate
for
the
style
of
application
that
you
have
grown
up
with
and
be
successful
with
and
want
to
start
meeting
on
that
journey
to
cloud
native.
B
So
you
know,
we
know
that
Jakarta
runs
large
amounts
of
business
at
the
moment
and
Jakarta
has
begun
this
very
exciting
journeys,
its
transition
to
the
Klipsch
foundation.
It's
getting
new
capabilities
which
are
going
to
be
very
much
focused
on
ensuring
it
integrates
well
with
the
newer
technologies
in
micro
profile
in
other
areas
which
themselves
are
developing.
Those
ap
is
for
very
cloud
focused
capabilities.
B
B
B
Away
Java
we're
not
rewriting
all
of
our
applications
in
new
languages,
but
we're
evolving
Java
to
be
aware
of
this
environment
it
capable
of
taking
the
existing
technologies.
We
have
with
us
and
being
just
as
relevant
in
cloud
native
as
any
other
technology,
which
is
there
and
I
think
it
closes
the
prime
place
where
that
has
been
well
demonstrate
and
the
community
has
come
together
with
that,
as
an
understanding
of
where
that
will
take
place,
so
I
just
wanted
to
wrap
up
with
a
quick.
Thank
you
for
for
your
time.
B
This
is,
you
know,
a
very
fast
changing
area.
I
think
you
everyone's
doing
the
right
thing
by
by
joining
a
conference
like
this
keeping
yourself
educated
and
up-to-date
on
what
the
the
latest
technologies
are.
There
are
some
really
interesting
talks
coming
along
from
the
experts
in
their
areas,
who
will
be
able
to
tell
you
about
all
the
technical
detail.
I
wanted
to
start
off
by
just
setting
it
in
that
context,
encouraging
you
to
stay
for
as
long
as
you
can
today
and
enjoy
the
technical
talks
and
the
remainder
of
the
conference.
So
thank.
A
A
Thank
you,
Tim
I
have
a
quick
question
here
that
might
be
answered
throughout
the
conference
later
on
as
well,
but
what
kind
of
testing
tools
out
of
the
box
kubernetes
provides
for
developer?
The
main
concern
is
I
test
the
deployed
container
or
Security
for
future
completeness
elements.
Would
you
be
able
to
give
any
details
on
the
testing
on.
B
Kubernetes
specifically
clearly
there's
a
different
way
in
testing
and
in
these
environments.
So
a
lot
of
people
may
have
parallel
systems
which
they
initially
starts
off
with
with
development,
but
then
pretty
quickly
get
into
a
be
testing
the
ability
to
reach
specific
proportions
of
work
load
onto
new
type,
their
versions
of
the
application
and
get
some
some
very
quick
feedback.
So
there's
actually
a
lot
more
opportunity.
B
I
think
here
to
to
roll
out
new
capabilities
using
some
some
real
data
with
some
real
users-
and
you
know,
there's
lots
of
good
examples
of
people
in
large
companies
who
have
have
that
kind
of
development
model
of
redirecting
proportions
of
their
work.
Low
down
to
two
new
new
versions
of
the
applications
see
what
the
impact
is
both
in
terms
of
performance
and
those
function
as
well.
A
Okay,
Tim
so
I
think
we're
going
to
end
this
broadcast
because
we're
moving
on
to
world
alliance
sessions,
and
he
will
talk
a
little
bit
more
about
specifically
to
Jakarta
once
again
thank
you,
Tim
and
once
again
thanks
everyone
for
dialing
in
we
have
a
very
exciting
day
ahead
of
us,
so
hang
in
hang
in
there
and
we
will
pull
you
into
another
session
or
go
through
the
session.
Thank
you
so
much
once
again
by
mail
by
Tim.
Sorry.