►
From YouTube: Driving Jakarta EE Success | JakartaOne Livestream
Description
Will Lyons - Senior Director of Enterprise Cloud Native Java Product Management at Oracle Corporation
---
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
B
B
B
B
Let's
start
with
jacquard
EDA,
so
jacquard
ee8
was
released
in
September
2019,
so
gee
that's
about
eight
months
ago,
nine
months
ago.
It's
a
result
of
an
effort.
As
you
know,
combined
effort
of
different
members
of
the
jacquard
II
working
group
and
the
jacquard
II
community
and
the
primary
goal
of
Jakarta
ena.
Excuse
me.
Cardi
gate
was
to
deliver
a
first
release
of
the
platform
that
was
fully
compatible
with
Java
EE
8,
but
was
based
on
the
open
specification
process.
B
So
most
of
the
Java
EE
vendors
have
now
delivered
implementations
which
passed
the
Jakarta
eek
pat
ability
tests.
So
we've
actually
been
quite
successful
in
Korea
vendor
support.
So
here
is
a
current
listing
of
all
the
vendors
who
and
the
implementations
that
have
passed:
the
Jakarta,
ee8
technology
compatibility
kit,
so
between
open
Liberty,
PI,
R
server,
wildfly,
Oracle,
WebLogic
server
and,
of
course,
Eclipse
GlassFish
server
and
a
pusuk
application
server,
Prenton
AB
server,
the
JBoss
Enterprise
of
application
platform
in
team
X
juice.
B
We
have
nine
implementations
which
are
placing
the
full
platform
TCK
in
our
implementations,
passing
the
web
profile.
So
we've
actually
achieved
a
great
deal
of
success
in
encouraging
vendors
to
deliver
compatible
implementations
and
I.
One
of
the
reasons
for
this
is
not
only
the
compatibility
with
Java
EE
8,
so
we
could
leverage
that,
but
we
have
an
open-source
TCK.
So
it's
real
easy
to
get
started
and
using
the
TCK
and
getting
your
implementation
into
a
state
where
it's
passing.
So
we
feel
really
good
about
that.
B
We
also
feel
good
about
jacquard
e's
relevance
to
cloud
native
computing,
certainly
within
Oracle
and
I'm
sure,
among
the
other,
among
yourselves
and
among
the
other
vendors
who
are
participating
in
the
working
group.
We
are
seeing
a
significant
shift
in
usage
by
our
customers
and
interest
in
running
micro
services,
running
applications
in
containers,
most
typically
orchestrating
containers
through
use
of
technologies
like
kubernetes,
and
we're
certainly
seeing
that
in
terms
of
demand
for
running
2-car
de
applications
in
kubernetes.
B
One
of
the
standard
components
that's
used
for
managing
applications
in
kubernetes
is
called
a
kubernetes
operator.
The
kubernetes
operator
is
a
component
that
is
used
to
extend
kubernetes
api
x'
and
manage
specific
types
of
applications
running
in
kubernetes,
and
you
can
see
here
that-
and
this
is
just
a
sampling.
This
is
not
a
comprehensive
representation,
but
both
open,
Liberty,
wildfly
WebLogic
have
implemented
kubernetes
operators
to
support
the
usage
of
these
technologies
running
in
kubernetes
and
containers.
Payara
has
delivered
a
capability
called
docker
nodes
for
implementing
native
support
for
docker
containers
when
running
PI
R
server.
B
If
you
look
on
Amazon
Web,
Services,
IBM
cloud
user
from
Microsoft
and
Oracle
cloud,
you
can
see
that
all
these
vendors
and
others
deliver
support
for
jacquard
EEE,
the
simplify
the
provisioning
of
jacquard
e
configurations
and
generally
support
enablement
of
jacquard
ee
applications
running
in
their
cloud.
So
we
have
a
platform
which
is
built
for
in
supports
cloud
native
infrastructures
and
which
is
actively
supported
by
some
of
the
major
public
cloud
offerings
in
the
industry.
B
We
also
are
leveraging
jacquard
EEE
in
other
cloud
native
implementations
and
with
other
cloud
native
technologies,
for
example,
micro
profile
and
you'll,
be
hearing
several
presentations
on
micro
profile
today,
Eclipse
micro
profile
leverages
the
jacquard
ee
specifications,
so
micro
profile,
implementations
level,
jax-rs,
CDI,
JSON
P
and
in
JSON
B,
and
it's
an
example.
I've
listed
Helen
on
MP,
which
is
an
open
source
implementation
you'll
be
hearing
about
today,
which
both
leverages
those
standards,
because
it
is
a
micro
profile,
compatible
implementation
and
we're
delivering
new
implementations
that
leverage
not
only
these
standards
but
leverage.
B
The
component
implementations
which
are
provided
in
Eclipse
GlassFish
and
which
are
delivered
in
the
EE
4j
projects
and
repositories,
hosted
at
the
Eclipse
Foundation,
and
we
not
only
leverage
the
technologies
I
just
mentioned,
but
also
provides
the
port
for
Java
persistence,
the
Java
transaction
API
and
excuse
me
Jakarta
persistence
and
to
cut
transactions
and
Jakarta
WebSocket.
So
we
have
examples
of
other
cloud
native
technologies
which
are
leveraging
jakarta.
Ee
api's.
Forgive
me
for
my
occasional
lapse
into
a
java
ee
terminology.
It's
it's
an
old
sin.
B
A
B
The
things
we
have
done
to
drive
participation
in
the
community.
We
conducted
a
livestream
event
like
this
one
in
Japan,
with
over
200
attendees
prior
to
the
lockdown
on
physical
conferences,
which
unfortunately
began
occurring
during
March.
We
participated
in
four
physical
conferences.
We
were
actually
going
to
be
have
a
major
presence
at
cube
con,
which
has
had
to
be
postponed.
Unfortunately,
but
we
were
actively
participating
in
physical
conferences,
we've
done
online
tech
talks.
This
is
an
ongoing
series
of
talks
given
by
community
members
that
are
relative
or
relevant
for
Jakarta
EE
technologies.
B
We've
done
presentations
on
Jakarta
aid
self,
the
Jakarta
Update
series
we
have
a
very
active
series
of
blogs
that
are
being
delivered.
Ivar
is
a
very
active
member
of
the
blogging
community,
and
we've
also
launched
a
new
YouTube
channel
Studio
Jakarta,
EE
I,
believe
all
of
these
presentations
are
going
to
be
made
available
with
the
links
so
that
you
can
go
and
visit
all
these
sites
participate
and
Tech
Talks
update
series
and
in
the
YouTube
channel
we
have
also
just
completed
the
2020
version
of
The
Jakarta.
B
A
developer
survey
were
analysing
the
results
and
will
report
on
them
soon,
but
we
had
a
very
positive
response
with
2000
over
2000
respondents.
So
we're
very
happy
about
that.
We've
also
we've
delivered
an
initial
for
those
of
you
who
are
members
of
Java
user
groups
around
the
world.
We've
stood
up
a
crowd
test
account
like
this
one,
which
we
have
made
available
for
Java
groups,
Java
user
groups
to
use
to
host
their
virtual
meetings,
while
physical
meetings
are
being
put
on
hold.
B
We've
also
created
a
program
for
Java
user
groups
to
adopt
a
spec,
to
encourage
particular
juggs
to
pick
a
jacquard
ee
spec
and
participate
in
requirements
or
development
or
testing
of
that
specification.
We've
also
taken
steps
to
simplify
the
ability
for
individuals
to
participate
in
the
jacquard
ee
working
group.
So
for
those
of
you
who
may
be
may
have
an
interest
in
jakarta
ee,
but
your
parent
company
that
you're
working
for
is
not
a
member
of
the
eclipse
foundation.
B
B
We're
also
seeing
growing
participation
in
Jakarta
II
projects
throughout
the
community
and
across
the
community.
So
what
this
pie
chart
shows
is
contributions
from
Jakarta
Yi
working
group
members
to
Jakarta
projects
during
2019
and
during
2019.
That
was
the
timeframe
when
most
of
our
efforts
were
focused
on
Jakarta,
ee8
delivery,
and
many
of
the
contributions
naturally
were
driven
by
Oracle
in
terms
of
specifications
in
terms
of
contributions
of
GlassFish
technology.
B
We're
seeing
a
lot
of
forward
progress
in
2020
towards
a
more
even
distribution,
any
more,
even
participation
from
Jakarta
ye
members
across
the
community,
so
whereas
Oracle
was
contributing
over
50%
of
contributions
during
2019.
If
you
look
at
commits
to
Jakarta
spec
projects
in
q1,
you
see
a
much
more
even
distribution
across
the
vendor,
members
of
the
Jakarta
working
group
and
a
much
larger
contribution
from
other
community
participants.
B
So
what's
coming
next
from
the
technology
delivery
side,
the
next
thing
we're
focusing
on
is
Jakarta
ee9.
So
the
Jakarta
Jakarta
e9
is
the
next
release
of
the
Jakarta
a
platform.
So
it
will
be
a
full
release
of
the
platform
and
the
component
ap
is
the
intent
is
to
deliver
functional
and
architectural
equivalence
to
Jakarta,
ee8
and
Jakarta.
Yet
functionality.
B
We've
actually
got
an
open
source
project
within
the
Eclipse
Foundation
called
the
Eclipse
transformer
project
which
is
being
built
which
can
take
an
existing
Jakarta
8
application
and
transform
its
use
of
packages
to
Jakarta
9.
We're
seeing
some
good
success
with
that,
and
we
hope
that
that
project
continues
to
evolve.
B
So
we
have
a
project
underway
to
deliver.
Jakarta
e9
forget
the
precise
kickoff
date,
but
it
was
in
the
late
December
or
early
January
time
frame
an
overview.
The
project
is
provided
at
this
URL.
The
goal
is
to
move
to
the
Jakarta
namespace
as
I
described.
There
are
no
new
specifications,
with
the
exception
of
certain
specifications
that
were
formerly
delivered
in
Java
SE
and
were
removed
from
java
SE,
so
have
to
be
delivered
outside
Java
C
to
run
on
Java
C
11
we're
removing
a
small
number
of
deprecated
specifications
that
were
very
infrequently
used.
B
We
will
be
supporting
Java
SE
11,
so
there
will
be
the
option
to
run
on
Java
SE
8,
but
you
know,
implementations
must
support
Java
C
11
and
we've
got
over
30
specifications
TC
case
to
deliver,
along
with
appropriate,
compatible
implementations
for
the
various
components
and
for
the
full
platform
itself.
So
it's
a
very
significant
project
but
we're
making
good
progress.
So
we've
got
API
release
candidates
available
for
all
the
specifications.
B
We've
got
milestone,
implementations
for
all
the
components
I
have
it
on
good
authority
from
the
project
leads
that
were
actually
there.
At
this
point,
we've
got
a
growing
number
of
component
TCK,
so
TC
Kade's.
That
can
actually
be
used
to
verify
the
compatibility
of
the
component
implementations
that
are
being
delivered
and
we
actually
have
new,
builds
actually
completing
for
the
next
version
of
Eclipse
GlassFish,
which,
for
a
variety
of
technical
reasons,
happens
to
be
a
technical
prerequisite
for
this
release,
in
addition
to
being
a
compatible
implementation
of
G
jacquard
89.
B
Our
hope
is
that
we're
going
to
be
delivering
a
milestone,
release
of
Jakarta
e9.
We
won't
have
full
implementations
passing
all
tcks,
but
we
hope
to
have
implementations
that
are
working
and
can
be
released
for
evaluation
for
usage
by
tooling
vendors
and
by
the
community
to
begin
experimenting
with
ee9
and
preparing
for
a
ga
release
in
the
early
fall
timeframe.
So
roughly
September
is
timeframe.
B
So
how
can
you
help
we're
always
looking
for
assistance
with
the
community
to
promote
Jakarta
technologies
and
the
jacquard
e
brand
in
the
community
to
help
with
technical
work,
to
help
develop
collateral,
to
support
the
overall
initiative
and,
to
you
know,
test
things
out
to
report
bugs
to
help
deliver
the
platform
and
improve
the
technologies?
We're
delivering
you'll
be
getting
copies
of
this
presentation.
Please
use
use
these
links
to
sign
up
for
the
mailing
lists.
B
So
real
happy
with
the
progress
we
made,
a
both
seeing
successful,
Jakarta
e8
implementations,
encouraging
participation
in
Jack
par
de
throughout
the
community,
the
delivery
process,
that's
underway
for
the
jacquard
ei9
platform,
and
we're
appreciative
of
you
joining
this
presentation
and
hope
that
you
sign
up
for
other
events
and
for
participation
and
other
initiatives
going
forward.
So
I've
got
five
six
minutes
left.
Are
there
questions
yeah.
B
A
B
So
Java
X,
as
many
of
you
probably
know,
is
a
package
name
and
a
namespace
and
a
naming
convention
that
is
used
by
Java
SE
and,
as
many
of
you
know,
that's
very
important.
Technology
for
Oracle,
very
important
for
the
community
itself
and
Oracle
takes
an
active
interest
in
protecting
the
intellectual
property
associated
with
Java
and
the
compatibility
of
Java
SE
implementations.
B
We
worked
very
hard
with
the
Eclipse
Foundation
to
find
a
way
where
an
independent
effort
at
the
Eclipse
Foundation
could
continue
to
use
the
Java
X
namespace,
while
retaining
what
we
felt
were
appropriate
protections
of
Java,
SE,
IP
and
Java
C
compatibility,
and
we
were
unable
to
come
to
an
agreement
between
the
two
organizations.
I
am
not
in
a
position
to
go
into
greater
detail
than
that,
but
I
would
say
both
organizations
made
a
good-faith
effort
to
achieve
this.
We
were
unable
to.
B
A
A
And
there
are
tutorials
and
examples
that
run
on
glass
fish
and
they
run
on
any
Jacare
ii
compatible
server,
whether
they
run
on
the
latest
version
or
not,
that
is
kind
of
up
to
the
community
to
participate.
So
I
encourage
you
to
join
these
projects
and
help
get
this
sample
is
up
and
running.
We
have
the
the
first
couple
of
Jakara
he
and
the
Shikari
a
tutorial
so
and
all
the
samples
of
your
voyage.
A
B
I
see
just
to
clarify
for
Alexander
EDF
is
not
supported
today
on
1401,
but
we
plan
to
support
it
in
the
future.
I
just
want
to
be
factually
precise.
In
my
answers
to
your
questions,
okay
I
looks
like
we're
at
the
end
of
our
time.
Hey.
Thank
you
all
very
much.
Thank
you
Ivar
and
enjoy
the
remainder
of
the
event.
We've
got
great
participation
or
real
pleased
by
that
yeah.