►
From YouTube: Industry Keynote - JakartaOne 2022
Description
Jakarta EE gives developers a comprehensive set of vendor-neutral, open specifications that are used for developing modern, cloud native Java applications from the ground up. With Jakarta EE, technology developers and consumers can be confident they have the best technologies for developing cloud native, mission-critical applications. And they can build on decades of Java developer expertise to move existing workloads to the cloud.
Learn more: https://jakarta.ee/
Follow us on Twitter: https://twitter.com/home
Follow us on LinkedIn: https://www.linkedin.com/showcase/jakartaee/
Like us on Facebook: https://www.facebook.com/JakartaEE/
A
Hi
so
my
name's
Steve
Milleridge
I'm,
the
founder
of
payara
and
I'm,
going
to
take
you
through
the
piara
keynote
on
Jakarta
one
live
stream
is
a
Jakarta
ee10
compatible
implementation
for
the
for
the
application
server
and
it
also
is
compatible
with
microprofile
five,
so
we're
committed
to
both
jakartri
10
and
micro
profile,
5.,
we're
moving
to
micro
profile
6
when
that
will
be
released
in
this
month
at
some
point
and
we'll
move
into
it
in
the
first
quarter.
A
A
A
However,
your
software
development,
as
it
is
that
the
date
May
shift,
but
that
is
when
we're
currently
scheduled
and
that
will
also
deliver
whether
upgrade
tooling,
to
allow
you
to
move
your
prior
five
environments
into
Pi.
R6
as
far
as
possible
through
automation
and
we're
also
going
to
deliver
a
tooling
to
help
you
migrate
from
prior
five
applications.
Sorry
Jakarta,
E9
applications,
sorry
to
graduate
applications,
digado
E10
and
also
those
applications
that
will
be
on
five
onto
six
and
that's
scheduled
to
be
delivered
with
prioritics
Enterprise.
A
So
I
want
to
dig
a
bit
into
how
we
see
Jakarta
EE
and
how
jakartri
fits
in
The
Wider
landscape
of
Enterprise
Java
development.
So
one
of
the
things
that
we're
focusing
on
as
a
company
is
basically
the
benefits
of
the
Jakarta
application
model.
One
of
the
key
things
about
Jakarta,
EE
and
Java
ee
before
is
that
separation
of
your
application
deployment
from
your
runtime.
This
is
one
of
the
key
innovations
that
Enterprise
Java
brought
right
back
at
the
beginning.
A
So
in
the
jakartri
model
you
obviously
build
your
application.
You
use
the
Jakarta
EE
apis
and
you
don't
need
to
worry
about
a
lot
of
things
that
the
runtime
provide
for
you.
For
example,
the
Jacob
application
server
or
runtime
like
pyara,
delivers
many
many
different
services
to
you
as
an
application
developer
that
you
don't
need
to
worry
about.
A
One
of
the
major
infrastructure
developments,
one
of
the
major
Innovations
over
the
past
few
years-
is
infrastructure,
so
infrastructure
as
compute
and
what
pyara
does
is
we
handle
that
infrastructure
for
you
what
you
do
as
an
application
developer?
Is
you
build
your
card
tree
applications
and
pyara
platform,
basically
assembles
a
whole
load
of
Open
Source
projects.
It
makes
so
sure
that
all
those
projects
work
together
and
delivers
you
into
the
contrary,
compatible
runtime
and
then
through
our
Enterprise
engineering.
A
And
what
you're
trying
to
do
is
make
sure
that
you
know
you
as
an
application
developer.
If
you
take
that
separation
of
runtime
from
your
application,
then
what
we
want
to
do
is
give
you
the
platforms
to
deploy
it
and
the
platforms
that
scale
across
all
the
different
types
of
compute
infrastructure
that
you
may
come
across.
A
That
allows
you
to
take
your
wow
file
and
just
package
it
in
a
single
jar
in
a
similar
fashion
to
other
runtimes
like
spring
boot,
and
we
also
then
deliver
prior
server,
which
gives
you
traditional
application.
Server
jvm
clustering
domain
management
across
VMS
containers
I
want
to
talk
with
kubernetes
if
necessary,
and
then
what
we're
also
delivering
is
a
revolutionary
new
platform
called
priori
Cloud,
which
is
a
kubernetes
native
application,
server
or
prior
Cloud
delivers,
is
a
complete
runtime
built
on
top
of
kubernetes.
A
So
so,
basically,
the
advantage
of
separating
your
runtime
from
deployment
is
that
you
don't
need
to
worry
about
many
different
things.
You
don't
need
to
assemble
a
runtime
from
lots
of
pieces,
it's
completely
versioned,
it
can
be
secure.
We
can
deliver
monitoring
and
insights
into
the
running
of
their
application
through
metrics
and
health
checks,
and
we
can
deliver
you
as
completely
scalable
platform
and
power
cloud
is
a
new
innovation
and
revolutionary
runtime
that
sits
on
top
of
kubernetes.
So.
B
A
You're
trying
to
take
your
application,
for
example,
in
power
micro,
and
you
want
you
to
deploy
it
onto
a
container
and
you
need
to
deploy
it
into
kubernetes.
Then
there's
many
things
you
need
to
do.
You
need
to
do
many
things
that
aren't
related
to
software
development.
For
example.
You
need
to
build
yourself
a
Docker
file
to
build
a
container
image
to
deploy
that
image
into
a
container
registry.
You
need
to
create
five
definitions
for
kubernetes.
You
need
to
create
yaml
files.
You
need
to
configure
it.
A
You
need
to
configure
your
secrets
and
then
you
need
to
work
out
how
you're
going
to
get
that
onto
applicability's
infrastructure,
which
hopefully
you're
not
managing
yourself
or
someone
else
is
managing
on
your
behalf.
And
then
you
need
to
sort
out
your
Ingress
through
API
gateways
or
whatever
well
pay
our
Cloud
does.
Is
it
basically
does
that
for
you?
So
what
we're
doing
is
building
a
decantery
application,
sorry
to
runtime
on
top
of
kubernetes
natively.
A
So
when
you
deploy
an
application
with
priori
Cloud,
you
basically
take
your
wire
file
and
it
manages
and
handles
all
the
infrastructure
for
you.
That's
on
topic
abilities.
So
that
maintains
kubernetes
itself,
it's
provisioning
nodes,
Provisions
pods,
it
does
all
the
Ingress
routing
it
can
generate
SSL
certificates
from
your
own
behalf.
A
So
prior
cloud
is
one
of
our
newest
products,
and
that
provides
you
on
that
hyperscale
kubernetes
native
end
of
the
of
the
spectrum
of
compute
infrastructure,
so
just
to
summarize
so
piora,
basically
Jakarta
ee,
first
application
application
company
we're
delivering
platforms
for
Psychiatry
developers
that
scale
right
through
from
small
devices
onto
hyperscale
Cloud.
We
have
from
on
the
application
server
side
of
things.
A
The
Jaco
10
compatible
implementation
with
pi
R6,
that's
first
chips
in
power,
Community,
which
is
designed
to
deliver
Innovation
to
developers
first,
and
then
we
also
have
power
Enterprise,
which
is
designed
to
support
Mission
critical
application
workloads.
It
is
fully
supported
application
server.
So
thank
you.
That's
piara!.
B
E
E
Thanks
for
having
me
today,
my
name
is
Xavi
Montero
and
I've
been
working
for
Tommy
tribe
for
I.
Think
about
30k.
Now,
so
quite
a
lot
of
time,
I
may
Focus
about
the
my
main
focus.
The
last
years
I've
been
to
work
on
Dr
microprofon
and
also
on
some
open
source
implementations.
But
I'll
get
to
do
that
a
bit
later.
E
Let
me
briefly
introduce
Tommy
tribe.
Hopefully
the
train
is
moving
very
briefly.
So
Tommy
tribe
is
a
company
built
from
the
community
itself.
E
E
We
do
provide
24
7
support
and
we
are
geographically
spread
over
six
countries.
So
quite
the
company,
one
of
the
biggest
challenges
today
is
around
security
and
for
people
we
do
productivity
scanning
and
notifications.
We
do
that
for
people
because
well
a
lot
of
Open
Source
projects
that
you
may
use
like
Apache
Tomcat,
for
instance,
only
keeps
two
active
versions
and,
and
basically
the
don't
get
seven,
for
instance,
is
discontinued
and
you
don't
get
any
lce
patching
anymore
on
those
versions.
E
What's
to
me,
Tommy
itself
is
an
application
server
built
on
top
of
Apache
Tomcat.
What
we
do,
basically,
is
that
we
don't
know
the
vanilla,
but
she
don't
get
we
just
on
the
tropical
of
libraries
inside
for
CGI,
Json
processing,
jpa
and
so
on,
with
the
right
all
the
integration
code
ourselves
and
deployment
to
make
sure
that
everything
works
smoothly
together.
We
zip
that
up
again-
and
here
we
go-
we
get
Tommy.
We
do
have
four
flavors
currently
of
Tomi.
E
We
do
have
the
web
profile
ones
35,
but
we
do
also
provide
a
micro
profile,
compatible
version
which
is
micro,
profile.
Five
compatible
I'll
get
into
that
a
bit
later.
Why
we
do?
Why?
Do
we
do
that?
Well,
just
because
Apache
Tomcat
was
and
and
he's
probably
still,
the
most
widely
used
application
server,
but
only
few
people
use
Tomcat
the
way
it
is
a
lot
of
people.
I
think
Steve
mentioned
that
quickly
in
his
presentation,
a
lot
of
people
don't
only
build
their
application.
E
They
also
drop
a
lot
of
libraries
to
I,
don't
know
to
manage
persistency
or
restful
Services
dependency
injections.
So
what
they
do
basically
is
they
build
their
own
application
server?
E
We
think
that
their
role
is
not
the
right
application
server
in
an
XML
configuration
file
or
to
white
blooming.
Their
role
is
to
focus
on
their
business
and
write
applications.
It
also
makes
the
environment
harder
to
patch.
Let's
say
that
there
is
a
CV
in
one
of
the
libraries
they
have
now
to
go
through
all
the
applications
and
update
the
library
in
there,
as
opposed
to
just
update
the
application
server
and
everything
is
dispatched
for
them.
E
So
we
do
that,
basically
for
people
to
to
focus
on
the
application
and
not
the
application
server.
The
the
Tommy
itself
is
around
40
megabytes
for
the
light
version,
which
is
the
web
profile.
The
the
more
complete
version
is
less
than
100
megabytes,
so
it's
still
very,
very
lightweight
and,
and
the
good
news
is
that
everything
that
you
can
use
with
Tomcat
remains
valid.
E
A
few
Milestones
so
last
year
we
announced
the
compatible
version
of
Tommy,
so
it
was
against
the
chokatai
9.1.
We
did
that
using
the
eclipse,
bytecode
Transformer,
which
basically
allowed
us
to
to
catch
up
with
five
different
versions
of
ee
that
we
haven't
been
able
to
able
to
do
before
it
was.
E
It
was
very,
very
good
news
for
the
community
and-
and
we
were
very
proud
of
of
the
achievement
since
then,
we
moved
forward
in
order
to
reach
the
final
version
of
Tommy
and
and
to
do
that,
we
decided
to
get
away
of
the
bytecode
transformation.
E
We
we
decided
to
split
between
Java,
X
and
Jakarta,
and
and
move
our
source
base
to
Jakarta
and
avoid
bike
transformation,
just
because
we
realized
that
it
was
very,
very
hard
to
get
all
the
tooling
to
be
updated
as
well.
So,
basically,
all
the
arcillion,
the
the
test
framework,
the
embedded
container,
they
were
all
broken
and
only
the
zip
file
was
really
working
with
Jakarta.
E
It
also
basically
allowed
us
to
catch
up
with
micro
profile
at
the
same
time
and
I'm
I'm
very
proud
and
and
pleased
to
announce
that
we
just
meeting
the
CCR
to
be
a
micro
profile,
5
compatible
and-
and
we
are
very,
very
close
to
the
microprofile
6.0
compatible
as
well.
So
the
migration
allowed
us
to
to
basically
move
the
two
forwards
and-
and
the
plan
now
is
really
to
to
focus
on
jakartai
10
and
also
on
micropro56.0,
as
I
mentioned.
E
I.
Just
wanted
to
to
take
the
opportunity
of
of
this
presentation
to
quickly
speak
about
our
experience
in
migrating
from
java
X
to
Jakarta
I.
Think
probably,
the
vast
majority
of
this
audience
is
still
using
Java
X
applications,
and
some
of
them
might
be
asking
themselves
how
they
can
proceed
now.
So
we
did
our
first
bike
conversion
for
Tommy.
We
then
moved
to
the
source
code
approach
and
I
thought
it
was
good
to
at
least
give
you
some
options
with
the
the
inbox
and
and
the
side
effects.
E
The
most
of
most
of
the
tools
can
also
be
used
to
transform
your
source
code.
We
we
used
a
mixed
approach
to
convert
dummy
to
Jakarta
I.
Think
most
of
our
work.
We
did
it
with
a
script
based
approach,
but
I
know
that
some
open
source
libraries
like
small
Rye,
they
use
an
hybrid.
You
know,
approach
using
script
and
and
those
other
tools
to
migrate
from
java
X
to
to
Jakarta.
E
We
do
recommend
you
to
to
embrace
the
the
source
code
migration
as
soon
as
possible.
We
are
right
there
in
Jakarta.
Jakarta
is
moving
forward
very
quickly
with
new
features
and
therefore
I
I
do
believe
that
staying
on
Java
X
is
not
a
good,
a
good
way
to
to
behave
and
a
good
way
to
to
set
you
up
for
success.
E
E
One
is
the
classifier.
It
just
doesn't
work
because
it
breaks
all
the
transitive
dependencies
and
and
dependency
Management
in
Maven.
The
most
practical
approach
is
probably
to
bump
up
the
the
major
version
it's
the
most
natural.
It
has
side
effects,
of
course,
because
if
you
have
version
three
for
Java,
X
and
version
4
for
Jakarta,
then
well,
it
means
that
you
cannot
really
do
any
more
major
version
for
javex.
E
E
E
You
can
see
that
on
the
entire
tools
that
we
use
in
Tomi,
only
a
few
of
them
are
basically
Jakarta
compatible
and
and
well,
as
you
can
see,
even
those
which
are
compatible
sometimes
bring
some
some
limitations
like
the
cxf1,
which
is
ongoing,
but
requires
Java
17
to
run
them
I'm
running
short
in
my
presentations,
so
I'll
go
straight
into
the
end.
E
I
just
quoted
the
the
website
for
do
I
like
that
to
get
a
vendor
on
road
tool,
open
specifications
in
Jakarta,
we
need
more
implementations
and,
to
you
know
really,
the
the
worst
thing
we
could
get
into
is
basically
write
specifications
and
only
get
one
implementation.
So
really,
if
you
want
to
get
diversity
and
and
get
new
features
and
and
bring
Innovation
to
Jakarta,
please
make
sure
to
contribute
to
open
source
implementations.
E
D
Start
sharing
my
screen.
Can
you
please
see
that
Tanya?
Yes,
very
good
thanks
thanks
will
so.
Thank
you
very
much.
My
name
is
Ian
Robinson
I
am.
B
D
An
IBM
distinguished
engineer,
I
represent
IBM
at
a
variety
of
different
Clips
venues,
Jakarta
being
one
of
them
micro
profile
being
another
I'm,
also
responsible
for
or
my
my
team
is
responsible
for
the
Liberty
implementation
and
a
lot
of
the
other
things
that
we
do
in
the
ecosystem
around
Jakarta
EE,
and
that's
really
what
I
want
to
talk
about.
D
So
there
have
been
many
sessions
today
and
Emily
has
got
one
coming
up
in
an
hour
or
so
time
after
this
one
that
we'll
talk
about
aspects
of
Jakarta
ee10
and
the
relationship
to
it
of
microprofile.
Obviously,
one
of
the
things
that
is
significantly
new
in
Jakarta
ee10
is
the
core
profile,
which
is
this
set
of
specifications
here.
D
One
of
the
motivations
for
our
I
should
say
that,
as
things
stand
at
the
moment,
the
certified
implementations
of
the
core
profile
are
these
three
runtimes
here
open
Liberty
is
the
one
that
I'm
going
to
talk
about
and
I'm
going
to
take
my
life
into
my
hands
by
doing
a
demo
of
some
some
not
yet
generally
available,
but
but
available
beta
capabilities
I'm
going
to
show
that
in
a
moment.
D
So
one
of
the
motivations
for
the
Jakarta
ee-10
core
Prime
core
profile
is
microprofile,
so
the
current
version
of
micro
profile
is
microprofile.
Five
I've
drawn
a
red
line
around
the
Jakarta
ee
specifications
that
form
the
core
of
micro
profile.
So
these
are
the
things
that
were
pretty
much
the
same
as
as
were
identified
right
at
the
beginning
of
the
launch
of
my
profile,
which
is
probably
the
best
part
about
five
years
ago
now.
D
Microprofile
sixth,
will
be
the
next
version
of
micro
profile
and
that's
going
through.
Let's
go
through
the
final
stages
of
its
preparedness.
At
the
moment,
it's
not
quite
there
yet,
but
hopefully
it'll
be
with
us
soon
and,
as
you
can
see
here,
all
of
those
Jakarta
dependencies
and
now
can
now
be
provided
by
the
Jakarta
ee10
core
profile.
So
this
is
a
motivational
use
case
for
Jakarta
ee
tank
core
profile.
Now
I
wanted
to
I'm
going
to
go
into
my
demonstration
now
and
get
out
of
slide
sharing
mode.
D
What
I'd
like
to
do
is
to
show
some
of
the
contributions
and
efforts
that
IBM
in
particular,
are
making
around
these
Technologies.
D
So
I'm
going
to
show
you
what
we'll
be
doing
with
our
runtime
code
in
open
literacy,
what
we're
doing
with
some
of
our
tools,
ecosystem
work,
so
I'm
going
to
show
you
a
Jakarta
language
server
inside
the
Eclipse
IDE
I'm,
going
to
show
I'm
going
to
show
running
a
brand
new
Jakarta
ee10,
a
micro
profile,
6
candidate
application
in
an
instant
on
container
that
will
start
up
in
hopefully
just
100,
also
micro,
microsec
milliseconds,
not
microseconds.
D
That
would
be
really
cool,
milliseconds
and
then
I'm
going
to
show
it
being
deployed
very
very
easily
to
a
kubernetes
environment.
So,
let's
switch
to
my
Clips
IDE.
Here
we
go
so
what
I've
got
running
here
is
a
liberty
server
using
the
Jakarta
language
server
protocol
that
IBM
have
helped
develop.
I
will
go
to
the
community
for
that
in
a
moment,
because
I'm
gonna
shout
I'm
going
to
do
a
an
invitation
to
to
get
more
help
from
the
community
to
con
to
carry
on
building
that
out.
So
what
we've
got
here?
D
I've
got
a
liberty
server
running
with
a
set
of
Jakarta
ee10
features,
so
Jax
RS
features,
jsonp
features,
CDI
features
open.
Liberty
is
a
runtime
that
runs
only
what
you
configure
it
to
run
and
the
application
that
I'm
going
to
show
requires
that
set.
So
this
is
essentially
a
core
profile
application,
with
some
micro
profile
capabilities
added
into
it
as
well.
What
we're
doing
here
is
we're
running
Liberty
in
developer
mode,
so
I
can
change
things
and
they
will
instantly
be
reflected
in
the
runtime
without
having
to
rebuild
my
application
or
restart
it.
D
We
can
see
over
here,
let's
see
so.
If
we,
if
I
add
a
new
endpoint
to
my
application,
I'll
show
you
some
of
the
things
that
we
can
do
with
the
language
with
the
the
Jakarta
language
server
protocol,
so
I
can,
for
example,
create
a
new.
Let's
create
a
new
live
stream,
foreign.
D
Language
server
is
going
to
allow
me
to
do.
Is
it's
going
to
give
me
syntax,
assist
and
I
can
say
right.
I
would
like
a
rest
class.
It'll
generate
me.
A
template
for
a
rest
class
I
can
create
a
new,
a
new
endpoint,
a
new
Jax
RSM
product.
Let's
call
it
live
stream.
Let's
say
hello
live
stream.
Let's
save
that
application.
D
We
can
go
and
have
a
look
at
that
application
here
and
and
immediately
what
I've,
what
I've
added
as
a
as
a
as
a
new
live
endpoint
is
immediately
available,
but
when
I
was
testing,
this
earlier
on,
I
was
hoping
to
congratulate
either
Spain
or
Morocco,
depending
on
who
was
winning
at
this
point
in
time.
Unfortunately,
a
Look
Away.
Now,
if
you
don't
know,
I,
don't
want
to
know
the
score.
D
Unfortunately,
the
last
time
I
looked,
it
was
still
nil,
nil,
but
what
this?
What
what
we're
showing
here
is
the
ability
to
be
able
to
update
an
application
very
very
easily.
The
application
that
I'm
actually
showing
is
a
simple
rest
application
and
it's
it's
simply
a
Jax
RS
application.
It
has
micro
profile,
health
and
metrics
endpoints,
and
this
is
using
the
latest
versions
of
those
specifications.
It's
E10
and
micro
profile.
Six.
D
What
I'm
going
to
show
you
now
is
how
I
can
take
this
application
and
run
it
in
in
a
container
that
will
start
up
in
only
a
few
hundred
milliseconds.
Anybody
that
was
on
live
stream
earlier
on
today
may
have
caught
Tom
and
Grace's
session
on
Liberty
instant,
and
what
I'm
going
to
do
now
is
I'm,
going
to
show
that
running
I'm
going
to
show
how
I
can
take
that
application
that
we've
just
seen
in
the
Eclipse
IDE
and
make
it
start
really
really
quickly
in
a
Java
container.
D
The
application,
the
Liberty
server
itself-
and
this
is
that
this
is
without
making
any
changes
to
my
application
at
all.
So
the
application
is
completely
unaware
that
it's
running
in
this
environment.
You
can
do
this
with
any
Jakarta
or
micro
profile
application,
if
you,
if
you're
running
it,
on
a
liberty
instant
on
container.
So
let's,
let's
take
a
look
at
that.
D
So
first
of
all,
I've
got
just
a
couple
of
containers
without
already
pre-built
the
container
for
the
application
that
I
just
showed
in
the
Eclipse
IDE.
So
what
I'm
now
going
to
do
is
I'm
going
to
create
a
second
version
of
that
container
with
a
checkpoint
inside
it,
and
so
what
we're
going
to
do
here,
first
of
all,
is
create
the
checkpoint.
D
This
is
a
little
bit
similar
to
something
Andre
was
showing
earlier
on
when
he
was
comparing
different
startup
times
of
containers
built
in
different
ways.
If
I
run
this
Liberty
server
with
this
Jakarta
et-10
and
micro
profile,
six
candidate
application
in
it
that
started
up,
as
you
can
see
at
the
bottom
here
in
five
and
a
half
seconds,
if
I
now
run
the
version
with
the
checkpoints
in
its
same
application.
As
you
can
see,
this
came
up
in
266
milliseconds,
which
is
about
15
times
faster.
D
Without
the
application
needing
to
be
aware,
if
I
want
to
deploy
that
container,
that
I
just
built
into
into
a
kubernetes
environment,
you
can
just
deploy
that
with
a
standard
kubernetes
deployment
yaml,
but
we
we
can
do
things
a
little
bit
more
simply
than
that
with
Liberty
I've
got
a
I've
got
an
open
shift
environment
which
I'll
show
in
a
moment
that
has
an
open,
Liberty
operator
installed
in
it,
which
means
that
I
can
deploy
applications
very
very
easily,
using
a
limited
custom
resource
which,
which
cuts
out
an
awful
lot
of
the
detail
from
from
a
standard
typical
kubernetes
deployment
handle,
it
will
take
care
of
Auto,
Auto,
defining
and
creating
things
like
roots
and
services,
so
that
all
you
need
to
do
is
deploy
your
application
and
it'll
take
care
of
creating
and
managing
all
of
the
artifacts
around
that.
D
D
So
if
I
get
this
window
out
of
the
way
now,
so
this
is
my
instant
on
container,
it's
now
being
deployed
into
my
openshift
environment.
There
you
go,
I
asked
it
to
create
two
pods.
There
are
two
pods
that
have
been
created
and
if
we
just
take
a
quick
look
at
the
output,
this
was
my
instant
on
container
and,
as
you
can
see,
it's
just
started
in
openshift.
Oh.
D
What
do
you
do
so?
Thank
you
very
much.
Please
come
and
help
us
please
come
and
help
us
at
the
Jakarta
language
server
project.
Thank.
C
You
well
I
think
we.
B
Know
and
I
love
your
jakarte.
C
Background
how
about
my
t-shirt,
though
my
t-shirt
is
impressive:
okay,
not
bad
all
right,
hello,
everybody!
My
name
is
Will
Lyons
I
manage
product
management
for
Oracle,
Enterprise,
Cloud
native
Java,
I
I've
never
been
called
a
distinguished
product
manager,
but
I
I.
C
B
C
To
talk
a
little
bit
about
Oracle
and
how
Oracle
is
contributing
to
and
and
taking
advantage
of
and
leveraging,
Jakarta
EE,
so
Oracle
has
been
a
strategic
member
of
the
charty
working
group.
Since
it's.
C
We
contributed
many
specifications,
implementations
the
tck
to
the
working
group.
We
remain
a
strong
contributor
to
both
jakarti
EE
and
to
microprofile
and
I'm,
really
pleased
with
the
success
we've
observed
in
collaboration
with
everybody
on
this
call
and
all.
B
C
In
creating
an
open
and
vendor
neutral
process,
I've
taken
a
snapshot
of
some
of
the
most
recent
contribution
data
from
the
eclipse
Foundation,
and
we
can
see
that
the
general
Community,
not
necessarily
those
affiliated
with
specific
strategic
members
of
the
working
group,
are
making
a
significant
number
of
contributions
to
jakarti,
EE
and
we'd
like
to
see
that
continue
and
I
encourage
all
of
you
to
take
advantage
of
Mike
malinkovic's
advice
and
become
a
contributor,
become
a
committer
and
help
us
to
move
to
Carter
e
forward.
C
So
so
how
is
Oracle
leveraging
jakarti
and
its
product
line?
Well,
we
start
with
Oracle
weblogic
server.
Weblogic
server
is
an
application.
Server.
Weblogic
1411
is
compatible
with
jakarti
E8.
It
is
the
foundation
for
the
Oracle
Fusion
middleware
product
line
and
many
of
Oracle
applications
and
Oracle
cloud
services.
C
C
We
also
offer
Oracle
coherence.
Coherence
provides
a
data
grid
which
is
a
set
of
jdms
which
can
be
used
as
a
distributed
cache
for
Oracle
applications
for
haladon
applications.
C
It
can
also
be
used
with
other
Technologies,
like
micronauts
spring
non-java
Frameworks,
like
JavaScript
or
net,
to
provide
a
distributed
cache
and
also
it
provides
a
distributed
processing
of
data
that
exists
in
this
highly
scalable
and
fault,
tolerant
data
grid.
C
All
these
products
are
Java
based.
We
have
integration
across
all
of
these
Technologies
to
enable
you
to
build
standards-based,
highly
scalable,
highly
available
applications
that
are
fully
integrated
with
a
very
diverse
set
of
java
Technologies
in
the
Java
ecosystem,
and
all
of
these
Technologies
are
supported
in
kubernetes,
so
you
can
deploy
in
kubernetes.
C
Both
traditional
applications
built
on
an
application
server
like
weblogic
server
or
microservices
applications
built
on
haladon
to
run
them
in
containers
to,
and
also
with
coherence,
applications
and
coherence,
caches
to
run
those
in
containers
to
run
them
in
kubernetes
infrastructure,
on
private
clouds,
on
premises
and
in
a
diversity
of
public
clouds,
and
part
of
our
product
line
is
also
the
Verrazano
Enterprise
container
platform,
which
provides
a
platform
for
deploying
securing
monitoring
and
managing
applications
and
microservices
that
are
deployed
to
kubernetes.
C
So
Verrazano
supports
deployment
management
and
monitoring
of
applications
built
with
weblogic
coherence
with
heladon
with
spring,
with
Micronaut,
with
JavaScript
applications
and
other
applications
in
a
polyglot.
Architecture
and
Verrazano
also
supports
not
only
deployments
to
individual
kubernetes
clusters
and
clouds,
but
multi-cloud
and
multi-cluster
deployments.
C
So
the
goal
of
Oracle
Enterprise
Cloud
native
Java
and
the
product
line
I
just
reviewed,
is
to
enable
Cloud
native
Java.
So
our
goals
really
are
aligned
very
much
with
the
goals
of
the
jakarti
working
group
to
enable
you
to
deploy
containerized
traditional
Java,
the
cardi
ee
applications
to
build
and
deploy
microservices
based
on
micro
profile
that
can
run
alongside
those
traditional
web
logic
applications
and
to
provide
a
unified
management
framework
that
can
be
used
to
manage
those
traditional
and
microservices-based
applications.
As
a.
A
C
C
This
provides
just
a
brief
snapshot
of
what
we're
supporting
today.
I've
already
mentioned,
weblogic
server
to
supplement
weblogic
server.
We've
delivered
a
variety
of
tools
in
open
source
that
enable
you
to
take
your
weblogic
applications.
Introspect
them
create
container
images
from
those
deploy
them
using
a
weblogic
operator
to
kubernetes
to
monitor
those
weblogic
applications
as
they're
running
in
kubernetes,
with
Prometheus
and
grafana,
and
open
search
for
logging.
C
These
tools
are
supported
both
in
on-premises
and
in
Oracle
offerings
we
deliver
in
Oracle
Cloud.
We
also
provide
offerings
where
weblogic
is
supporting
in
other
public
clouds
like
Azure,
and
we
have
new
releases
of
weblogic
coming
up
next
year.
In
the
coherence
side,
we
have
released
Oracle
coherence
and
we
have
neglected
to
mention
this.
C
We
have
also
open
sourced
many
aspects
of
coherence
in
what
we
call
coherence,
Community
Edition,
the
most
current
release
of
coherence,
Community
Edition
supports
integration
with
the
cardi
E9
applications,
including
heladon
applications
and
other
applications
that
use
jakarti,
9
apis
and
we're
also
planning
a
new
release
of
Oracle
coherence,
leveraging
all
the
innovations
that
are
delivered
in
coherence,
Community
Edition,
in
open
source
in
2023.
On
the
heladon
side,
we
have
two
major
releases
of
Helen
on
currently
supported
in
production,
which
both
support
those
are
held
on
2
and
Haledon.
C
3.0,
which
support
microprofile
held
on
3.0,
supports
micro
profile,
five
and
leverages
to
cardi
9
apis
and
we'll
be
We've,
delivered
our
first
release
of
heladon
Nema
or
held
on
4.0,
which
I'll
talk
about
in
just
a
minute,
and
we've
delivered
our
fourth
minor
release
of
Verrazano
Verrazano
1.4,
which
supports
again
deployment
of
applications
built
built
using
all
of
these
Technologies
I
just
want
to
drill
down
just
a
bit
on
hold
on
4.0
the
alpha
release,
which
is
available
today
in
open
source,
and
this
is
the
first
microservices
framework
based
on
the
Java
virtual
threading
model,
delivered
in
what
used
to
be
called
project
Loom,
which
is
essentially
offers
the
scalability
of
asynchronous
or
reactive
programming
with
the
Simplicity
of
writing
synchronous
code.
C
So
this
is
fulfilling
in
a
micro
profile
based
framework.
Our
the
Alpha
2
release
of
heladon
4.0
supports
microprofile,
the
Simplicity
of
standard
space
programming,
using
synchronous
models
with
a
scalability
benefits
offered
by
virtual
threads
and
our
GA
Target,
for
this
is
in
2023
we're
expecting
to
go
ga
when
Java
se21
goes
ga
and
what
what
this
highlights
is
that
you
know
one
of
the
things
we're
really
excited
about
is
that
using
Jakarta,
EE
and
microprofile
Technologies.
C
You
can
take
advantage
of
the
latest
innovations
that
are
delivered
in
the
Java
platform
in
a
standards-based
environment
that
enables
integration
with
existing
applications
and
Technologies
you're
already
familiar
with
today.
So
take
a
look
at
heladon,
4.0,
Alpha,
2
and
Helen
on
Nema
and
The
Innovation
we're
delivering
in
terms
of
virtual
threading
support.
C
So
this
necessarily
is
just
a
brief
run-through
of
all
of
the
Technologies
we're
supporting
in
an
Enterprise,
Cloud
native
Java
I
assume
these
presentations
will
be
made
available
and
I've
provided
links
where
you
can
drill
down
and
take
a
closer
look
at
all
the
Technologies
we're
delivering
in
this
space
and
in
open
source,
and
thank
you
much
for.
Thank
you
very
much
for
the
time
today
and
I'll
turn.
It
over
to
Scott.
F
F
Okay,
so
my
name
is
Scott
Hunter
and
I'm,
the
VP
of
product
on
the
Azure
developer,
experience
team.
You
know
at
Microsoft,
we've
really
invested
in
Java
the
last
couple
years,
whether
it's
building
our
own
jvm,
whether
it's
the
tools
that
we
build
for
visual
studio
code
or
the
sdks
and
stuff
we
build
for
the
Azure
cloud
and
some
of
the
the
contributions
we've
made
for
the
open
jdk
and
such
I
build
most
of
our
developer
experiences
around
Azure.
F
And
so
you
know
if
customers
once
wants
to
run
Java
in
Azure
they're,
probably
using
some
of
the
stuff
that
might
can
build,
and
what
I
want
to
talk
about
today
is
Howard.
How
we're
jumping
in
the.
F
And
so
you
can
see
here
that
you
know
we're
part
of
the
Jakarta
ee
working
group
as
an
Enterprise
number
Micro
profile
working
group.
F
As
a
corporate
member,
we
are
elected
steering
committee
member
on
the
Jakarta
e
steering
committee
and
marketing
and
we're
a
platform
committer,
and
you
know
our
job
is
honestly
just
to
help
Advance
all
the
driver
Technologies
and
make
sure
that
if
a
customer
chooses
to
run
them
in
our
Cloud
that
there's
great
support
there
and
this
kind
of
complements
the
the
participation
we
have
in
the
JCP
as
well
to
basically
help
drive
and
Advance
Java
I
see,
and
so
we
have
a
ton
of
Investments
and
offerings
in
Azure
for
customers
who
want
to
run
Java,
and
this
is
mainly
done
with
partnership
with
some
of
our
big
strategic
Partners.
F
But
you
know
we
want
to
have
a
diverse
ecosystem
of
offerings
for
Java
developers,
and
so
you
can
see
if
you,
whether
you
want
platform
as
a
service,
that's
where
we're
going
to
actually
manage
the
cloud
for
you.
We'll
do
the
updates,
we'll
let
you
scale
up
and
scale
down
very
easily,
and
so
we,
we
have
a
ton
of
offerings
here,
whether
it's
our
app
service,
which
I'll
talk
about
a
little
bit
more.
F
That's
our
primary
hosting
model
for
platform
as
a
service
or
service
bus,
which
is
a
mechanism
for
sending
messages
in
our
in
our
in
our
in
our
cloud
and
then,
of
course,
we
want
to
make
sure
you
know
we
live
in
a
container
world.
F
We
live
in
a
microservice
world,
and
so
whether
you
know
you
want
to
run
an
Azure
community
service,
which
is
a
managed
kubernetes
that
we
have
in
Azure
or
you
want
to
run
in
Azure,
Red
Hat,
open
jet,
both
of
those
are
supported,
and
then,
of
course,
we
have
plenty
of
customers
just
want
to
run
in
VMS
and
virtual
machines,
and
so
that's
our
is,
and
so
you
can
see
whether
you
know
wherever
you
want
to
run
your
job.
F
We
have
a
lot
of
great
offerings
for
the
ecosystem,
so
I'm
going
to
drill
into
a
couple
of
these.
This
is
our
default
support
and
so
we're
the
only
top
tier
public
cloud
with
the
manage
Jakarta
ee
application
server
offering,
and
so
this
is
JBoss
EAP
on
app
Service.
F
F
Update
notifications-
and
you
can
see
we
just
added
clustering
support.
We're
gonna
have
clustering
support
in
the
fourth
quarter
of
this
year
and
then
early
next
year,
we'll
have
jobs
done
support
as
well.
So
this
is
for
the
customer
that
really
wants
us
to
manage
the
whole
system
for
them,
and
we
got
a
great
offering
there.
F
F
Customer
could
come
in
select
those
offerings
and
we'll
boot
up
the
right
amount
of
tech
to
do
this,
and
you
can
see
that
once
again
in
this
case,
it's
it's
built
and
maintained
by
both
Microsoft
and
red
hat,
and
you
can
decide
to
run
it
as
a
standalone
or
in
a
cluster
configuration
and
depending
on
how
much
you
want
to
scale
it.
We
have
a
two
Virtual
Machine
Technologies,
just
VMS
and
virtual
machine
scale
steps
both
of
those
who
work
there.
F
F
Last
Model
next
is
weblogic
one
of
the
ways
we
can
run
weblogic
on
Azure
and
we've
got
a
variety
of
offerings
here
as
well.
Once
again,
it's
a
after
Marketplace
solution,
they'll
be
managed
by
both
of
them
and
Oracle,
and
we
offer
weblogical
machines
and
kubernetes
once
again
bring
your
own
license
and
you
can
see.
We've
got
support
Integrations
with
a
variety
of
things,
whether
it's
Oracle
DB
coherence,
our
Azure
load,
balancer,
app,
Gateway,
Azure
SQL.
F
You
know
postgres
app,
Insight,
Etc,
monitoring,
yeah,
so
lots
of
lots
of
invest
Investments
there
and
we
have
integrated
Azure.
My
SQL
support
coming
that
we
already
shipped
that
in
September,
and
so
next
is
going
to
be.
You
know,
open
Liberty
web
sphere
and
we've
got
once
again
great
offerings
for
this
inside
of
our
Cloud
as
well.
Once
again,
some
Marketplace
offering
that
has
been.
You
know
in
this
case
maintained
and
supported
by
both
IBM
and
Microsoft.
F
Once
again
bring
your
own
license
and
we
have
lots
of
integrated.
C
F
And
and
starting
Journeys
coming
as
well
and
then
finally,
we
have
webviewer
on
Virtual
machines,
and
so
once
again
it's
gonna
be
a
Marketplace
offering
once
again
a
partnership
between
Microsoft
and
IBM.
F
Bring
your
own
license,
use
a
trial
license,
and
you
know
it
supports
both
single
single
single
instance
and
clusters
and
has
deep
Integrations
with
the
IBM
HTTP
server
and
you'll,
see
here
that
our
app
Gateway
supports
coming
in
very
soon
and
once
again
we
decided
integrated
support
for
Oracle,
DB,
db2,
Azure
SQL
and
this
past
November,
and
so
that's
just
a
quick
run
through
of
all
the
ways
that
you
can
run.
You
know
Jakarta
ee
applications
in
Azure,
and
you
know
you
can
see
here.
F
We've
got
a
bunch
of
stuff
on
the
road
now
still
to
go
and
how
to
how
to
start
get
started
guys
on
running
quircus
on
AKs.
That's
our
kubernetes
service
Corpus
on
functions.
That's
our
that's
our
lose
my
mind.
Functions
is
just
your
your
kind
of
go
run
as
you
go.
You
only
get
charged
what
you
call.
F
Yes,
you
pay,
as
you
go,
support
coming
as
well
and
so
and
we'll
have
a
bunch
of
database
support
a
bunch
of
templates
and
Morehouse.
You
guys
as
well.
So
you
know
we're
super
excited
to
be
part
of
the
community
and
make
sure
that
I
said.
If
you
choose
Microsoft,
we
have
a
great
way
to
run
all
your
Java
workloads,
and
so
with
that
I
will
hand
it
come
on.