►
From YouTube: OpenShift Coffee Break: Modernizing Java Apps
Description
After the boreal hemisphere summer break, the EMEA OpenShift Coffee Break come back with a special episode on how to modernize Java apps together with Ana-Maria Mihalceanu, Developer Advocate at Red Hat.
We will discuss available frameworks and tools that help Java developers to modernize Java apps and to help the migration to microservices (and even more!). Of course with live demos, don't miss it!
YouTube: https://youtu.be/
Twitch: https://red.ht/twitch
A
A
A
Good
morning,
good
morning,
everyone
and
welcome
back
to
the
openshift
coffee
break
show
we
came
back
after
our
northern
hemisphere
summer
break,
but
today
we
come
back
with
a
great
guest,
a
great
topic,
I'm
very
happy
to
welcome
our
guest
of
today,
which
is
our
colleague,
anna
maria,
and
also
we
have,
of
course,
our
tarot
so
good
morning,
everyone.
How
are
you
folks.
A
It
yeah-
and
I-
and
I
hope
you
have
all
your
coffee
shot,
because
it's
important
to
start
today
with
a
good
energy.
Just
to
recap
of
what
is
this
show.
This
is
the
openshift
coffee
break
a
bi-weekly
show
on
openshift
tv,
where
we
talk
about
openshift
cloud
native
enterprise
architecture
and
all
that
kind
of
stuff.
My
name
is
natalia.
C
A
Yeah
excellent,
okay,
everything
at
texas.
We
talked
about
everything,
but
today
we
focus
on
the
developer,
experience
for
java
developer
and
on
how
to
modernize
java
application.
My
name
is
natalie
winter
product
manager,
manager
for
openshift
here
in
redat,
and
I
let
anna
maria
and
terrell
re
present
themselves.
B
Well,
I
am
anna
nice
to
see
you
and
to
meet
you
today,
I'm
working
as
a
developer
advocate
for
redhead
at
the
moment
and
became
recently
this
year
a
java
champion.
So
I'm
welcoming
you
all
with
this.
This
talk
where
we're
going
to
see
more
from
developer's
side,
quite
a
bit
of
devops
as
well,
so
hopefully
you'll
like
it.
C
A
Well,
I
I
would
like
to
say
that
if
you
have
any
question
during
the
show,
please
send
into
the
chat
on
twitch
and
youtube
we're
streaming
both
in
twitch
and
youtube,
and
and
we
will
come
back
to
the
show
and
ask
question
to
anna
and
and
and
everyone
okay,
so
well
anna
today,
the
topic
was
a
modernizing
java,
apps,
so
also
terra
was
asking
before
in
our
the
brief
session
brief
session.
What
what
is
this
modernization
about?
What
what
does
it
means
modernizing
apps
and
java
apps.
B
Well,
as
I
was
telling
to
you,
is
about
improving
applications
for
your
end
users,
you
as
a
developer,
architect,
tester
devops
engineer.
I
mean
all
the
team
involved
there
to
improve
applications
for
end
users,
but
also
feeling
good
while
modernizing.
I
think
that
we
are
in
a
very
good
spot
as
it
professionals
and
we
have
the
opportunity
when
changing
something
or
building
something
to
actually
not
improve
the
end
user
experience,
but
also
improve
our
experience
as
well.
A
Of
course,
of
course,
we
we
talk
all
open
source
over
here
good
morning
to
all
the
folks
attending
there's
someone
from
komarayu
from
from
india,
oh
good
good
afternoon,
to
you
and
good
afternoon
to
all
the
people
attending.
I
guess
there's
someone
probably
there's
there
is
also
someone
from
australia.
A
You
know
last
time
we
had
someone
from
uruguay,
which
it
was
a
totally
hero,
because
it
was
3
a.m
in
its
time,
so
it
was
fantastic,
so
yeah,
I'm
very
I'm
very
happy,
and
you
know
what
today,
of
course
we
have
our
discussion,
but
then
also
anna
is
going
to
show
us
also
some
live
demo
that
that
is
the
spirit.
Also
terror
is
one
big
fan
of
live
demo.
I
remember
when
we
were
doing.
Poc
was
all
live.
Of
course.
A
B
B
Okay,
so
welcome
to
modernizing
java
apps
we
already
met
earlier,
but
in
addition
to
what
I
already
shared,
I
love
both
java
and
kubernetes,
and
a
lot
of
other
technologies,
because
I'm
passionate
about
solving
challenging
technical
scenarios.
So
the
more
complicated
things
are.
I
really
love
to
solve
them.
That's
pretty
much
the
way
I'm
going
and
in
the
discussion
that
we're
going
to
have
today,
we'll
start
it
with
a
modernization.
B
So
why
should
you
modernize-
and
you
can
write
your
your
answers
in
the
in
the
chat,
because
I'm
going
to
I'm
going
to
look
at
that,
so
why
go
into
modernization
part
some
reasons
found
out
throughout
time
through
my
own
experience?
Well,
adding
features
to
what
was
already
in
an
application
was
becoming
harder
and
harder.
B
There
are
an
endangered
species
in
terms
of
architecture,
we're
gonna,
do
distributed
systems
and
we're
gonna
split.
What
is
complex
into
multiple
applications,
because
this
is
the
way
we
should
go
and
people
discovered
that
you
can
do
and
deploy
them
independently
and
in
the
beginning
this
was
a
little
bit
vm
oriented,
but
in
the
meantime,
with
kubernetes
and
containers,
things
got
even
better
and
not
only
deployment
independency,
but
when
it
comes
to
making
applications
that
work
independently,
they're
also
isolated
when
it
comes
to
faults.
B
That's
annoying
I
mean
I
find
that's
annoying
and
especially
when
you
want
to
pay
for
something
that's
annoying,
but
it
happens
even
nowadays
and
talking
about
kubernetes
and
containers.
Thanks
to
that
zero
downtime
is
not
any
more
like
a
fantasy
story.
It's
a
reality.
There
are
ways
to
deploy
things
and
achieve
zero,
downtime,
so
making
things
smaller,
having
zero
downtime
and
doing
them
independently
sounds
like
the
best
thing
ever
and
since
you're,
making
them
like
independent.
B
You
can
scale
them
independently.
So
what
this
means
is
that
your
end
users
are
going
for
a
certain
promotion
on
your
platform
and
there's
a
lot
of.
I
don't
know
of
charge
on
that.
On
those
end
points,
you're
not
going
down
with
everything
you
can
scale
independently.
You
don't
have
to
think
like
to
scale
independently
and
then
it
will
take
a
lot
of
time
for
things
to
get
started,
because,
if
you're,
using
all
the
goodness
that
is
microservices
plus
containers
in
a
proper
orchestration,
you
should
be
in
a
happy
spot.
B
D
C
B
Well,
the
thing
is
that
you
start
to
split
those
when
you
see
that
the
startup
time
maybe
is
becoming
heavier
because
you're
adding
may
way
more
to
the
plate
and
if
you're
looking
from
I
mean
if
you're,
comparing
the
original
scenario
to
where
you
got,
I
mean
you
always
have
to
compare
where
you
started
and
where
you
got.
Is
it
that
the
same
scenario
or
is
it
got
that
complex
and
you
can
sometimes
spot
that?
Actually,
it's
like
one
and
a
half
scenario.
B
So
when
it's
when,
like
one
and
a
half
scenarios,
that's
when
you're
thinking
like
maybe
it
would
be
a
good
thing
to
decouple
these
things.
Otherwise
I
will
grow
into
a
actually
a
containerized
monolith
and
that's
what
you
want
to
avoid
like
you,
don't
want
to
go
back
to
that
place.
Another
good
thing
about
microservices.
You
can
monitor
them
and
you
can
monitor.
What's
going
on
with
them
and
most
of
the
time
the
startup
time
is
being
affected
and
you're.
B
Also,
looking
into
your
application
code
and
you're
like
feeling
that
not
everything
is
belonging
here
and
that's
something
that
you
can
do
together
with
your
colleagues,
especially
if
you're
java
developers
you
use
to
work
together
to
do
same
features
and
if
you're
coming
from
a
monolithic
world
you're
used
to
you,
know
discussing
those
and
how
things
are
interacting
and
it's
you
have
to
be
brave
and
cut
things
when
they
need
to
be
good.
That's
that's
the
story,
so
be
brave.
C
B
Okay,
thank
you
for
interrupting
me.
I
wanted
to
share
with
you
so
how
the
story
started
for
microservices.
Well,
probably
you've
seen
this
before.
If
you
worked
in
a
typical
er
application,
you
probably
made
some
tires.
There
was
a
presentation.
There
was
a
business
integration,
resources
and
so
on,
and
these
are
really
nice
ways
to
organize
your
app,
especially
if
you're
starting
from
scratch
is
very
nice.
You
can
use
all
the
great
patterns
java
patterns
that
you
learn
in
school
that
you
read
in
books.
B
It's
easy
to
to
make
a
simple
app,
a
simple
microservices,
but
when
you're
looking
back
to
your
monolith-
and
you
know
it's
the
big
thing
and
you
spend
a
lot
of
time
in
making
those
features
and
coupling
those
features
is
very
difficult
to
decouple,
then
looking
at
containers,
you
are
looking
as
a
developer
and
see
that.
Well,
if
I
want
to
see
and
replicate
how
this
app
is
going
to
work,
I
need
to
build
a
I
mean
to
make
a
docker
file.
I
need
to
work
with
docker
images.
B
Let's
just
put
it
like
that,
but
nowadays,
in
order
to
go
fast,
you
need
to
not
just
to
use
the
talk
to
the
colleague,
but
you
also
have
to
talk
to
and
make
that
procedure.
Actually
an
automated
procedure
not
like
do
that
and
talk
all
the
time,
because
you
don't
have
one
big
app
anymore.
You
have
many
small
apps
and
it
will
become
a
burden
for
everybody.
They
would
have
to
talk
to
their
colleagues
from
operational
side
all
the
time
and
tell
them
yeah,
deploy
that
micro
service,
deploy
that
micro
service
and
so
on.
B
B
Even
if
you
think
that
all
your
features
are
complex
and
complicated,
try
to
take
one
and
just
chop
a
little
bit
of
its
functionalities
or
maybe
a
little
bit
of
its
dependencies
and
start
with
that
one.
Then
you
can
add
some
dependencies
from
it
to
your
modem
to
your
monolith,
but
carefully
carefully.
Do
that?
Like
really
think
if
you
want
to
add
that
one
sometimes
when
you
are
rebuilding
a
big,
a
big
application
that
can
now
becomes
like
a
platform
a
distributed
system,
you
can
also
look
in
the
market.
B
Maybe
there
are
managed
services
that
are
very
cheap
or
open
sourced.
That
can
do
that
thing
for
you
and
instead
of
that
team
to
spend
time
in
rebuilding
things
from
scratch.
Maybe
you
can
take
that
already
and
in
put
that
into
your
into
your
app.
Secondly,
maybe
there
are
better
dependencies
than
what
you
used
to
use
in
the
past,
so
always
look
what
is
available
in
the
market,
especially
open
source
market.
B
B
How
we're
going
to
do
that
so
try
to
think
of
that
aspect
from
the
early
stages
and
speaking
about
transactions
and
everything
you
have
to
divide
vertically.
What's
going
on
with
your
app,
so
remember
the
monolith,
it
was
very
horizontal
well
when
you're
going
with
distributed
systems,
you're
thinking
vertically.
So
all
the
time
think
of
your
system
like
there's
some
vertical,
oh
there's,
a
your
app
is
vertical.
B
Well,
yes,
because
when
you
were
deploying
your
monolith
on
your
previous
app
you're,
actually
assuming
that
there's
going
to
be
a
database
available
there.
So
why
can't
your
new
microservices
think
the
same
thing
but
of
course
always
think
about
how
the
event
consistency
is
going
to
go
through
the
multiple
persistence
stores
and
so
on.
So
don't
forget
about
that
one
as
well.
Now,
if
you
can
deploy
the
app
independently,
you
can
release
early.
This
means
it
can
go
to
the
business
users
or
and
say
hey.
B
B
Yes,
it's
not
a
one-time
thing,
it's
a
continuous
improvement
thing
and
it
continues
improvement.
I
think
for
many
small
apps,
but
the
thing
is
that,
once
you
are
up
to
speed
and
you
get
the
risk,
you
are
actually
going
to
feel
more
energized
into
building
these
things
and
to
get
even
more
energized.
You
have
to
have
some
what
development
practices
and
that's
what
I'm
going
to
share
with
you
now,
because
I
think
there's
been
a
lot
of
talking
and
need
to
share
some
demos
with
you,
as
promised.
A
A
Yeah
and-
and
this
is
a
good-
let's
say-
holly-
hop
to
a
nice
open
source
project
which
is
a
com
barrier
which
is
a
community
that
helps
with
some
tool
modernizing
and
migrating.
Let's
say
legacy
app.
I
would
like
to
share
in
the
chat
the
link
to
to
that
to
the
community,
because
it's
very
important
what
you
say
and,
moreover,
it's
a
process
before
it
is
a
you
know,
a
framework
or
just
a
technology
stuff.
C
C
So
I
think
that
it's
also
important
here
that
how
do
you
measure
that
you
are
actually
doing
correct
things
when
you're
modernizing
that
you
have
better
quality
you
release
faster
customers
are
end.
Users
are
more
happy,
so
you
need
to
measure
that
you
just
don't
modernize
insane
of
modernizing,
but
you're
actually
doing
something
that
profits.
The
whole
company.
B
Yeah
true
one
thing
regarding
measures:
if
you're
working
agile,
I
think
the
fastest
way
to
measure
is
like
if
you
reach
the
goals
of
your
sprint.
So
if
your
sprint
is
completed
and
you
reach
the
goals
and
you
manage
to
have
the
demo
with
what
your
end
user
with
your
users
expected,
so
that's
one
way
to
measure.
Of
course,
that
kind
of
success
doesn't
come
immediately.
It
comes
in
time
and
it
comes
also
with
acceptance
and
also
another
way
to
measure.
B
Of
course,
monitoring
is
very
important,
using
metrics
in
your
app
and
I'm
going
to
show
that
to
you
as
well.
So
all
the
time
keep
an
eye
on
what
you're
doing,
with
the
tools
that
you
have
at
hand,
and
this
is
where
the
devops
part
is
very
important,
because
most
of
those
tools
in
alerts
are
coming
from
the
devops
side.
B
So
you
can
get
alerts
and
there's
a
lot
of
processes
that
can
be
can
be
improved,
especially
when
it
comes
to
build
not
just
seeing
a
bill
that
has
failed,
but
you
can
also
see
how
much
time
it
took
a
build
to
be
done.
That's
very
important
as
well,
because
if
it
takes
like
30
minutes
to
build
something,
it's
not
very
performant.
B
You
have
to
ask
yourself
a
question
and
then
you
have
to
come
back
to
the
board
and
think
how
you're
going
to
improve
things
as
development
team,
how
much
time
for
things
to
get
deployed
up
and
running
and
all
the
time
measures
on
these
pods
can
be
done
throughout
the
entire
process.
So
keep
an
eye
on
that
one
as
well,
and
you
can
post
those
on
your
favorite
chatting
tool
with
the
team
icon,
slack
or
anything
else
that
you're
using.
So
all
the
time
you
can
integrate
stuff
devops.
A
B
Sure
so,
first
things
first
start
small,
so
we're
going
to
start
small
and
if
you
want
to
start
small
and
build
your
own
first
microservice
probably
you've
seen
this
before,
but
I
need
to
have
my
scene
and
starting
point
as
well:
I'm
going
to
go
to
code.quarkus.io
and
make
my
own
small
app
and
I'm
going
to
make
my
reading
app
built
with
maven
start
small.
So
we
were
talking
about
start
small
and
when
you
want
to
see
like
an
effective
result
of
your
work
most
of
the
time,
you're
building
some
kind
of
web
service.
B
B
Secondly,
I
said
that
maybe
sometimes
you
need
some
persistent
store
and
to
go
faster,
I'll
use
the
memory
database
and
and
we'll
sell
the
database,
and
I
don't
I
like
queries.
I've
written
a
lot
of
queries,
but
I
like,
when
things
are
being
kind
of
generated
and
I
can
improve
based
on
the
generated
stuff,
so
I'm
going
to
just
type
in
hibernate
and
select
hybrid
rm
with
nachi,
because
it's
not
just
going
to
make
some
some
work
to
be
taken
away
from
me.
B
B
I
see
that
there
are
a
few
options
for
me
to
build
my
container
image
so
no
more
docker
and
I'm
just
clicking
container
image
chip
to
generate
to
build
my
container
image
using
jib
and
I
need
to
deploy
things.
But
I
want
for
some
things
to
be
generated
for
me
and
since
we're
at
openshift
tv,
I'm
going
to
select
openshift
to
generate
openshift
resources
from
annotations.
So
remember
this
is
the
developer
point
of
view
of
doing
things
and
of
course
we
talked
about
metrics.
So
let's
add
micrometer.
A
B
D
B
B
We
need
to
adapt
this
to
real
life,
and
before
doing
that,
I
want
you
to
start
up
things
to
see
that
this
application
that
I
got
is
actually
working
as
expected
and
is
not.
You
know
just
generated
codes.
So
let's
go
here
and
say:
nbn
quarkus
dev,
so
I'm
going
to
start
quarkus
in
my
dev
mode
and
to
see
how
how
fast
it
starts,
how
things
are
going
for
it
and
okay,
by
the
way
I'm
going
to
use
quarkx
in
jvm
mode,
not
the
native
one
for
this
for
this
demo.
But
if
you.
B
Yeah,
I
also
have
yeah,
I
have
also
growl
a
but
we're
going
to
go
traditionally
java
way
with
the
jvm
based
one
okay,
so
things
are
pretty
much
getting
started
here
and
I
just
want
to
see
a
few
things
being
shown
in
my
dev
mode
before
jumping
back
to
the
ide
yeah.
Well,
here's
the
thing
what
I
want
to
share
with
you
see
this
thing:
dev
services
forge
two
started,
but
I
didn't
configure
any
database
yet
well.
B
The
thing
is
that
in
dev
mode
with
quarkus
2,
you
have
dev
services
for
most
of
the
persistent
databases
available.
This
means
that
you
can
work
and
do
development
work
in
devmode
with
a
database
without
configuring.
Anything
but
remember
this
is
just
deaf
mode,
so
it
works
only
with
this
mode
for
deploying
part.
Well,
you
need
to
go
back
here
and
you
have
to
give
some
information
about
your
database.
So
what
I'm
going
to
do?
B
Okay,
now
going
back
to
my
code,
part
I
want
to
like
make
an
entity.
I
want
to
talk
to
the
daily
so
going
back
here
and
I'm
going
to
create
my
message,
entity
edit
and
I'm
going
to
go
traditionally
hibernate
and
gpa,
so
we're
going
to
say,
add
entity
and
what
I'm
going
to
do
different,
I'm
going
to
use
notchy
entity.
Why
did
I
do
this?
Because
if
I'm
going
to
the
panachi
entity
and
just
making
this
a
little
bit
bigger,
I
already
see
that
the
primary
key
part
is
solved
for
me.
B
D
B
More
work
I
like
I
like
to
have
less
work
and
just
add
some
fields
to
the
entity
and
let's
go
a
little
bit
traditional
here,
no
lombok
or
anything
for
the
moment
and
just
generate
getters
and
setters
like
we
used
to
do
it
in
the
gold
in
the
good
old
days,
and
since
I'm
going
to
talk
directly
with
this
and
team,
I
want
to
use
also
an
annotation
to
get
more
data
from
it.
So
I'm
going
to
use
json
include.
B
Include
non-nulls
only
so
this
is
it
with
my
entity,
I'm
going
back
to
change
my
greeting
resource
and
I'm
gonna
do
something
that's
going
to
shock
some
people.
Now,
I'm
going
to
find
all
directly
on
my
entity
and
then
list,
and
this
is
going
to
retrieve
a
list
of
messages,
so
this
is
kind
of
odd
what
I've
done
here
right,
probably
some
of
you
like
what?
What
are
you
going?
How
can
you
do
this?
B
This
is
called
active
record
pattern,
so
you
don't
need
to
define
repositories
any
intermediary
if
you
want
to
work
directly
with
the
entity
thanks
to
the
panache
entity.
Part,
that's
where
the
goodness
stays-
and
this
is
how
you
are
able
to
do
this,
but
it's
not
going
to
produce
to
explain
it's
going
to
produce
application
json.
So
these
are
my
messages.
This
is
how
things
have
changed.
B
Let
me
look
how
the
death
mode
is
looking
like
if
you're
looking
to
death
mode,
you
can
see
here
that
says
test
pause.
Let
me
press
air
and
just
going
here
to
rerun,
come
on
running
test
for
the
first
time
is
going
to
go
well
and
this.
What
has
done
with
our
pressing
or
pressing
r?
What
happens
is
that
you
are
actually
going
into
continuous
testing
mode.
B
Value
and
well,
let's,
let's
also
give
some
information
for
my
database
to
be
not
that
empty.
So
I'm
gonna
generate
some
messages
and
going
back
to
my
dev
mode,
I
can
see
that
now
my
tests
are
complete.
All
my
tests
are
passing
well.
This
is
cool
I
like
when
this
is
going
is
happening
and
let
me
go
to
the
browser
a
little
bit
and
check
how
things
are
going
to
localhost
8080.
B
B
B
What
this
does
is
that
when
I'm
using
nvm
clean
package
is
going
to
push
the
container
image
to
my
designated
registry,
so
I'm
using
quite
rio
and
I'm
gonna
have
these
definitions
for
my
image.
So
it's
gonna
be
my
registry,
my
and
a
sandbox
weakening
gap
with
a
certain
tag-
and
I
also
see
here
that
I
have
some
kubernetes,
so
I
can
do
some
kubernetes
generation
as
well,
but
I
also
want
to
deploy
to
kubernetes.
So
I'm
going
to
say,
kubernetes.deploy
deploy
true.
B
B
It's
just
for
it's
just
for
the
demo
part.
Do
not
worry.
I
mean
you
can
validate
this
in
my
github
repository.
I'm
going
to
share
that
with
you.
That
code
is
working.
All
the
tests
are
working,
so
it's
just
for
this
one
time,
because
things
are
taking
a
little
bit
longer
for
me
when
I'm
live
streaming
from
my
for
my
computer.
So
that's
just
another
thing
that
I'm
doing,
and
probably
some
developers
are
doing
that
as
well.
Myself
included.
B
B
This
is
going
to
be
deployed
in
my
sandbox,
so
in
my
openshift
sandbox
every
every
each
and
every
one
of
you
can
get
a
sandbox
for
30
days.
I
think
you
have
a
free,
sandbox,
just
register
with
the
red
hat
account,
meaning
put
your
email
and
your
details
and
you
get
this
for
free
and
you
don't
need
anything
else
to
work
with
it,
except
well
for
maybe
oc
cli
or
kubernetes
cli.
B
B
Oh
yeah,
I
forgot
to
add
a
route
now.
This
is
a
way
to
add
her
out,
but
this
is
not
the
way
that
I
would
have
added
her
out
as
a
developer.
So
I'm
just
going
to
do
this.
I
said
I've
created
the
route
here,
create
route,
no
pause,
because
I'm
I
don't
know
much
at
this
moment,
so
I'm
just
going
to
click,
create
and.
B
Yeah,
but
as
a
developer,
I
don't
like
to
use
many
click
clicks.
Sometimes,
oh
and
my
app
is
running.
That's
cool,
it's
not
ready
yet
on
everything,
but
is
that
actually
running
on
my
on
my
endpoints
and
it's
really
really
available
cool,
but
if
I
wanted
to
avoid
using
that
create
button
to
create
routes,
what
I
should
have
done
is
actually
go
here.
B
B
It
is
more
something
that
is
generated
from
annotations,
so
you
can
find
what
was
deployed
here
in
target
kubernetes,
so
you
can
find
what
was
deployed
and
it's
securely
deployed
with
a
service
account
already
done
for
you.
This
is
using
the
right
image
for
policy,
if
not
present,
so
it's
very
cautious
with
the
resources
and
the
devops
persons
know
what
I'm
talking
about
here.
B
B
This
is
pretty
cool,
but
some
of
you
will
say
that
yeah,
but
I
still
have
to
do
this.
I
have
to
go
and
copy
and
paste
it
somewhere
in
a
file
in
a
folder,
so
I
can
work
with
things
later
and
because
you
know
something
your
devops
colleague
is
gonna,
say
yeah,
you've
done
this,
but
is
not
having
the
resources
defined.
So
your
app
is
not
very
efficient
in
terms
of
and
containering
kubernetes
resources
and
you're
going
to
be
like
what.
B
And
you're
going
to
paste
it
and
you're
going
to
say
a
prayer
that
maybe
there's
enough
resources
for
you
to
deploy
something
and
if
it's
not
there's
going
to
be
a
colleague,
that's
going
to
modify
it,
but
there's
a
better
way
to
do
this.
Remember
the
sandbox!
You
can
go
to
the
sandbox
and
you
can
see
how
much
memory
and
how
much
cpu
your
application
is
consuming
so
that
you
can
tailor
the
resources
yourself.
B
So
you
don't
have
to
like
wait
and
make
assumptions
and
prayers
for
that
to
happen.
So
remember
the
the
memory
part,
so
I
saw
that
there
were
like
125
megawatts,
so
I'm
just
going
to
go
to
150
and
always
the
limits
have
to
be
bigger,
so
I'm
just
going
to
double
it
and
the
cpu.
I'm
just
going
to
get
it
like
this,
but
this
is
very
kubernetes
oriented.
B
C
B
So
you
also
have
I
forgot
to
say
that
you
get
some
docker
files
that
are
already
securely.
I
mean
you
get
your
docker
file,
your
your
basis
and
everything
where
you're
from
is
secure
because
well
you're
they're,
coming
from
a
trusted
resource
they're,
not
just
getting
randomly
from
dockers.
You
already
get
that
when
you're
getting
that
generated
from
the
website
itself.
So
don't
worry
about
that
and
the
rest
of
it.
You
saw
that
there's
a
service
account
and
there's
all
the
role,
mining
and
everything
so
you're
not
messing
things
around
now.
B
B
B
B
B
D
D
B
B
A
B
B
B
D
B
I,
why
are
you
moving
back
now?
This
is
I
zoom,
okay
and
just
type
in
health
here
and
I'm
going
to
get
the
health
part.
I
don't
generate
again
and
just
reimport
the
project
come
on
and
I
want
to
overwrite
my
my
data,
I'm
just
adding
it
via
mvn.
So
I'm
going
back
here
and
adding
this
here
by
adding
the
carcass
smaller
health
extension.
B
I'm
just
you
know
putting
all
what
I
need
for
me
to
make
my
own
liveness
and
readiness
checks
and
you're
going
to
find
a
customized
license
check
in
the
repositories
so
going
back
here
going
to
maintain
part-
and
this
is
it's
annoying-
I'm
gonna
rephrase
refresh
this
one
and
I
want
to
show
you
some
magic
I'm
going
to
do
this
alien
cream
package.
Mine
is
didn't
escape
test.
B
B
Okay,
kubernetes
openshift,
yaml
and
now
your
devops
colleague
is
going
to
be
very
happy
because
you
already
have
your
liveness
probe
configured
and
that's
really
cool
and
also
the
readiness
part
already
done
so
really
cool
only
generated
by
adding
an
extension,
nothing
else.
Of
course
you
can
customize
and
you
find
that
in
repo
your
health
endpoints
so
be
free
to
do
that
and
of
course,
your
generated
yaml
is
gonna,
follow
what
you're
coding
in
java.
B
B
I
will
copy
the
information,
that's
here
in
openshift.yml
and
just
change
a
few
bits
here,
so
that
I
can
make
more
deployment
configs
and
more
other
kubernetes
and
openshift
objects
so
that
I
don't
have
to
rework
the
ammo
all
the
time
and
then
I'm
just
creating
those
objects
and
openshift
and
I'm
attaching
each
config
map
to
each
deployment.
I
have
so.
Let's
start
the
joy
just
go
here,
say:
ignite.ch.
D
B
B
A
C
B
B
B
And
this
is
it
how
I
can
get
environment
variables
that
are
available
actually
in
overshift
I
don't
have
config
maps
on
my
local
and
work
with
it.
I
work
with
these
in
my
java
code,
so
I
don't
even
have
to
care
how
many
of
those
will
be
there,
and
this
can
happen
if
you
are
deploying
in
multiple
zones,
your
your
microservice.
B
B
For
like
monitoring
and
seeing
your
app,
especially
if
there
are
different
regions
where
you're,
where
you're
publishing
your
app,
you
need
to
annotate
this
with
a
singleton
and,
of
course,
with
that
produces
and
this
one
returns
a
meter,
filter,
dot,
common
tags,
I'm
going
to
give
a
list
of
arrays
as
list
and
just
give
the
tags
that
I
have
so
I'm
going
to
say
here,
country,
config
dot,
country
and
then
tag
dot
off
country
config.
No,
not
another
country,
yeah
region
got
the
region,
big
dot
region
and
let
me
import
the
coins.
Okay.
B
Now,
let's
close
this
one,
and
I
think
I
have
configured
also
the
micrometer
part
from
using
external
configuration.
So
I
am
like
keeping
happy
my
devops
colleagues
who
are
working
pretty
happy
with
the
config
maps
and
I
am
staying
in
my
java
code.
Equally
happy.
I
don't
know
what
those
conflict
maps
are.
B
So,
let's
go
back
to
the
terminal
and
just
make
one
last
deployment.
Okay,
I'm
going
to
do
this
in
the
incline
package
thing
with
the
test,
so
that
you
trust
me
that
they're
working,
so
this
is
going
to
push
and
deploy
things
again
and
if
I
were
to
just
redeploy
all
the
things
with
my
magic
script,
I
would
have
to
go
here
and
since
I
already
have
some
of
the
objects
in
my
ignite,
I
wouldn't
need
to
create
the
config
maps
anymore.
B
But
I
would
do
this
and
probably
do
this
replace,
but
this
is
pretty
much
the
way
that
you
can
combine
the
best
of
the
two
worlds,
meaning
java
and
kubernetes
openshift,
all
from
clean
java
code
and
just
a
little
bit
of
kubernetes
knowledge.
I
mean
just
using
the
the
small
things
that
are
depicted
in
kubernetes
that
I
owe
now
going
back
to
my
sandbox.
This
is
pretty
cool
place
because
you
can
see
the
topology
of
what
you
deployed
there.
So
you
can
see
all
the
applications
you
have
deployed.
B
You
can
check
how
they're
doing
if
they're,
up
and
running.
Typically,
this
blue
bright
blue
here
means
that
they're
up
and
running
and
they're
okay.
You
can
also
look
about
how
much
they're
consuming,
so
you
have
a
pretty
good
monitoring
place
and
natalia
showed
me
this
one.
You
just
need
to
go
back
and
remember
where
it
was:
oh
yeah
code
ready
workspaces.
B
B
This
is
where
you
find
the
code
and
please
check
it
out,
because
it
has
a
little
bit
more
things
like
a
liveness
endpoint
already
configured
and
try
to
check
that
one
out
and
see
how
things
are
getting
generated
once
you
have
that
one
in
place,
it's
pretty
pretty
cool,
so
everything
that
was
done
today
is
available
there
and,
of
course,
if
you
spot
anything
that
is
not
working
or
you
would
like
to
have
it
improved
or
please
do
challenge
me,
I'm
welcoming
that
so
pretty
much
over
the
time.
I
think.
A
C
Yeah
also
as
a
device
oriented
now
now
I
see
that
the
next
developer
use
the
cool
tooling.
So
what
the
developer
developer
is
shipping
is
has
to
pass
on
the
ammo
files
to
the
devops
so
that
they
can
put
doors
to
the
kit
and
follow
githubs.
So
in
this
kind
of
there
is
a
still
more
gap
between
doing
something
in
deployments
and
development
and
then
deploying
to
other
pre-production
environments
and
using
like
proper
ways
to
like
manage.
C
B
Please
ask
me
about
this
when,
because
I
know
from
from
my
own
experience
that
when
you
go
to
production,
the
resource
split
and
the
scaling
part
in
the
configuration
part
is
not
anymore,
something
that
is
can
be
touched
by
a
developer
and
typically
when
making
changes
to
yamls
that
are
going
to
even
through
production.
You
should
check
with
your
devops
colleague
like
request
a
review
on
that
one.
B
A
That
was
a
very
I'm
shocked
about
how
it
look
at
easy
to
start.
You
know
it
looks
very
easy,
but
I
think
that
there
is
a
complexity
under
the
hood,
many
things,
so
you
use
it
the
quercus
generator,
let's
say
for
generating
the
palm
xml
and
then
you
had
an
extension
and
then
you
added
metering
and
deployment
and
config
maps.
It
looked
so
easy
to
modernize.
Apps
thanks
anna
today
was.
B
Well,
every
developer
and
mvit
professional
has
his
or
her
magic,
and
I
want
to
say
that
for
going
further
and
making
more
complex
and
making
live
your
own
applications,
you
have
to
put
your
own
magic,
meaning
what
you
learned
throughout
the
years
when
using
patterns
they
still
apply.
You
just
have
to
adjust
a
little
bit.
Your
practices
and
you'll
see
that
you
are
going
to
be
even
faster
and
more
productive
when
creating
microservices
and
modernizing
java
apps.
A
Cool
cool,
thank
you
and
we
don't
have
a.
I
don't
see
an
additional
question
in
the
chat.
There
was
all
only
someone
say
that
there
is
a
new
category
on
twitch
software
and
game
development.
Thanks
peter
we
will
take
note
about
it
to
reach
out
more
people
in
the
community,
and
I
shared
in
the
chat
anna,
your
repo,
so
the
people
can
doing
the
same
thing.
Try
to
do
the
same
thing,
no
from
your
repo
and
with
developer
sandbox.
They
can
use
developer
sandbox.
A
They
can
use
your
repo
and
deploy
and
do
all
the
cool
stuff
you
did
and
if
they
have
any
question,
maybe
they
can
bring
you
on
twitter
on
on
the
on
our
twitter.
I
don't
know
if
you
want
to
share
also
your
twitter
handle,
but
it's
in
the
slide
before,
if
you
would
like
to
share
it
so
that
people
can
ping
you
and
and
for
this
folks,
I'm
really
really
glad
to
have
this
show
today.
Thank
you
hannah.
It
was
a
very
cool
live
demo.
A
I'm
sure
taro
also
loved
it,
because
it's
a
super
fun
live
demos,
we've
seen
lots
of
things
and
what
we
have
today.
If
you
stay
on
openshift
today,
overshift
tv
today
we
have
the
level
up,
show
husk
and
admin.
So
please
stay
on
openshift
tv.
Today
we
have
our
common
schedule
and
we
will
come
back.
The
openshift
tv
will
coffee
break
will
come
back
on
september
22..
A
We
will
talk
about
quercus
for
iot,
with
the
quercus
for
iot
community.
So
I
would
like
to
thank
everyone
that
joined
today,
thanks
anna
for
awesome
demo.
We
would
like
to
have
you
back
when
you
want
for
another
awesome
demo,
and
with
this
I
I
just
say
hello
and
talk
to
you
by
september
22
on
openshift
tv
coffee
break.
Thank
you.
Everyone
bye,
thank.