►
From YouTube: Industry Keynote | JakartaOne Livestream 2021
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/
B
B
Any
anyone
ready
to
do
some
vendor
keynotes
here
so
with
us.
Here
we
have
aleister
nottingham
from
ibm.
We
have
steve
millage
from
bayara
and
will
lions
from
oracle
david
blevins
from
tommy
ride
and
tatiana
duranczyk.
I
hope
I
pronounced
that
right
and
from
gelastic
so
welcome
everybody
and
you
all
have
what
is
it
eight
to
ten
minutes
and
we're
hard
on
time
management
here?
So
I'll
start
by
giving
the
word
to
alistair
from
ibm.
So
please
go
ahead.
C
D
D
Being
around
jakarta
and
the
first
one
I
wanted
to
cover
was
a
slight
announcement
which
is,
as
of
I
think
about
a
week
ago,
or
maybe
even
friday.
I
can
never
keep
track
of
these
we've
actually
ga
da
jakarta
to
ee9
support,
so
we
initially
put
jakarta
e9
support
out
in
our
beta
of
liberty
back
in
I
think
march
this
year
and
for
a
whole
bunch
of
reasons.
D
D
As
of
last
week.
We
we
got
got
ourselves
to
the
point
where
we
felt
we
had
a
release.
We
could
stand
behind
and
starting
from
friday
last
week,
we
submitted
all
of
these
kind
of
issues
you
can
see
here
for
the
certification
request.
So
hopefully,
when
the
process
goes
through,
liberty's
ga
release
will
be
on
the
jakarta
website,
as
kind
of
fully
certified
for
java,
8,
11
and
17..
So
that's
great
great
success
for
the
liberty
team.
D
We've
been
working
kind
of
hard
on
on
on
getting
there
and
one
of
the
things
that
allowed
us
to
get
there-
and
I
think
I
spoke
about
this
last
year-
was
the
eclipse
transformer
project
so
rather
than
starting
kind
of
from
manually,
going
through
the
source
code
and
changing
every
piece
of
source
to
import
the
jakarta
review
packages.
D
V8
was
ported
across
to
jakarta
39,
so
there
are
a
few
cases,
situations
where
we
didn't
use
the
transformer
to
to
pull
the
implementation
up.
D
So
if
we
pull
in
a
piece
of
open
source
in
the
open
source
project
itself
had
a
new
release,
we
would
pull
in
then
the
new
release
from
from
there,
but
for
for
things
like
our
servlet
container
and
ivjb
container,
this
definitely
was
the
way,
the
approach
that
we
took,
and
that
means
that
if
you
grab
the
liberty,
the
latest
liberty
release-
and
you
want
to
use
jakarta
e8,
because
that's
what
you're
used
to
you
can
do
that.
D
If
you
want
to
use
jakarta
e9,
you
can
do
that
and
the
source
code
is
kind
of
identical,
which
is
only
really
possible
because
the
the
apis
are,
broadly
speaking,
compatible
between
nine
is
just
the
package
name
change
the
namespace
changes
for
deployment
descriptors
following
on
from
jakarta
to
e9
micro
profile.
Five.
I
think
I
checked
yesterday
and
the
vote
for
micro
profile
5
past.
D
D
We
have
support
for
that
in
the
liberty
beta
22001
beta,
which
is
out
now,
was
the
compatible
implementation
for
that
vote,
and
you
can
kind
of
go
and
download
it,
and
that
has
both
jakarta
e9
and
micro
profile
5
in
it,
and
I
think
I'm
probably
going
to
do
less
than
my
eight
minutes,
which
I
I
always
expected.
So
if
we
look
ahead,
you
know
micro
profile.
5
is
now
a
standard.
D
We
don't
generally
ga
until
the
standard
is
complete,
so
micro
profile
night,
five
is,
is
coming
it's
in
beta
now
and
we've
just
started
the
process
of
putting
jakarta
tree
10
on
our
our
road
map.
So
I've
taken
a
screenshot
of
our
github
issues
board
where
we
place
all
of
the
work
that
we're
is
on
our
roadmap,
so
people
can
see-
and
it's
all
been
kind
of
prioritized
and
ordered.
D
So
we're
going
to
start
working
on
that
now
the
specification
is
still
kind
of
underway,
so
we
need
the
specifications
to
be
in
a
position
where
we
can
start
to
implement
them
before
you'll
start
to
see
an
implementation
rolling
out,
but
they'll
be
rolling
out
in
our
our
beta
program.
I
have
to
say
I'm
really
excited
about
what
about
jakarta:
u10,
jakarta
nine.
It
was
a
lot
of
internal
engineering
work.
It
wasn't
a
huge
amount
of
additional
function
for
the
end
users.
D
But
when
I
look
at
what's
going
on
for
jakarta
310,
I'm
really
excited
to
see
all
of
the
changes
that
coming
and
I'm
looking
forward
to
getting
them
implemented
in
in
liver,
tng
course,
and
with
that
I
have
no.
I
I'm
done
so
eva.
I
don't
know
who
to
hand
over
to
thank.
B
You
alexander,
that
was
awesome.
You
you
get
a
plus
one
for
the
time
management
that
that
kind
of
weighs
up
for
the
mute
button
in
the
beginning.
B
Right
so
yeah,
so
thank
you
aleister
and
next
up
is
steve.
Millage
from
the
piotr.
B
E
Cool
okay,
you
can
hear
me
all
right:
I'm
getting
internet
unstable
now,
typically,
okay,
okay,
thanks
thanks
aleister
handing
over
to
his
spot
on
time.
I
think
so
I'll
try
and
do
the
same
okay.
So
this
is
the
piara
keynote.
What
I
wanted
to
do
really
is:
take
you
just
through
some
thoughts
about
how
we
see
jakarta
and
how
we
see
payara
and
how
we
sort
of
interact
with
developers.
E
E
Okay,
so
one
of
the
key
things
we
did
a
seminar
pro
webinar
program
over
the
summer
and
one
of
the
things
we
wanted
to
do
really
was
highlight
some
of
the
myths
that
jakarta
ee
rve
has
had
over
the
past.
You
know
few
years,
ducati
javari,
taking
a
hammering
and
a
lot
of
these
are
due
to
myths
around
java,
ee
and
jakarta
ee.
So
I
want
to
just
re
reestablish
that
these
myths
are
myths
really
so
from
a
pirate
perspective,
one
of
the
key
points
is
jakarta.
Ee
can
do
microservices.
E
E
The
other
thing
that
psychiatry
application
servers
like
payara
often
get
beaten
up
about
is
resources
otherwise
slow
and
they're.
Heavy
and
again
I
wanted
to
just
dispel
that
myth
that
jakarta
ee
run
times
are
not
resource,
heavy
or
slow
compared
to
other
competitor
frameworks
that
you
may
choose
so,
for
example,
in
pyromicro
we
can
spin
up
a
server
with
you
know.
Less
than
30
megabytes
of
heat
usage,
so
jakarta
is
not
resource
heavy,
it's
not
slow.
It
is
incredibly
quick.
E
E
You
know
if
you
think,
payara
is
not
delivering
what
you
require
you
can
choose
to
switch,
and
that
gives
us
competitive
pressure
and
competitive
pressure
is
very
beneficial
to
you
as
a
developer
and
standards
development,
because
it
makes
us
innovate
not
in
the
apis
that
you
have
to
go
to,
but
in
actual
run
times
and
now,
as
we
go
close
to
the
release
of
ee10,
essentially
jakarta
is
driving
the
future
of
enterprise
development.
E
Then
payara.
We
are
absolutely
committed
to
the
jakarta
ee
model
and
I'm
going
to
talk
a
little
bit
about
the
jakarta
3
model
in
the
next
slide,
but
what
our
goal
is
to
be
first
for
jakarta
developers,
we
want
you
to
choose
payara,
and
we
wanted
to
choose
it
because
of
that
competition
that
we
have
with
other
vendors,
which
is
beneficial
and
the
reason
we've
really
committed
to
chicago
ee.
Is
we
actually
believe
that
the
jakarta
ee
deployment
model
is
actually
beneficial
to
developers
and
what
we
mean
by
that
is
carter.
E
Ee
delivers
a
a
very
strict
and
robust
separation
from
your
code,
where
you
spend
your
time
building
and
developing
your
business
logic
from
the
actual
infrastructure
that
runs
the
application.
E
So
that
gives
us
a
good
separation
of
concerns
in
that
you
can
concentrate
on
delivering
your
application
using
the
apis
that
we're
all
specifying
and
working
with
in
the
jakarta
working
group
and
payara
and
other
vendors
can
concentrate
on
delivering
that
infrastructure
for
you.
E
While
you
spend
your
time
building
your
application
and
we
think
this
gives
a
really
good
separation
and
gives
a
good
concentration
for
us
as
a
vendor,
and
we
think
it's
a
benefit
of
jakarta
e
over
other
frameworks
where
you
may
assemble
assemble
a
runtime
as
opposed
to
having
a
definition
of
what
a
runtime
needs
to
deliver
to
you
and
from
a
piara
perspective.
What
this
means
is
that
we
we
basically
handle
the
infrastructure,
you
build
your
applications.
So
if
you
look
at
piara
server,
it's
cons.
It's
constructed
from
many
different
projects.
E
Many
projects
in
the
eclipse
foundation,
which
are
implementing
specifications
like
tyrus
or
yasson
other
projects
in
eclipse
foundation,
are
hk2
which
are
delivering
a
dependency
injection
framework.
We
have
some
jboss
components
in
weld.
We
have
koba,
we
have
mahara
again
from
eclipse
and
then
we
also
have
some
other
components.
For
example
internally
in
paira
we
use
hazel
cast
for
our
clustering.
So
what
we
do
is
we
take
those
components
and
we
assemble
them
into
a
runtime
that
you
can
then
use
to
deliver
for
your
application.
E
While
you
build
your
application
to
your
to
these
new
jakarta
ee
apis
and
what
our
enterprise
engineering
team
is
doing,
is
it's
making
sure
that
all
these
things
work
together
and
can
deliver
a
runtime
with
a
soap
with
appropriate
qa
security
stability
and
all
the
good
things
that
you
need?
If
you're
building
you
know
a
production
application?
E
So
you
could
take
pyramid
micro
and
run
it
on
very
small
run
times
through
to
traditional
domain
models
like
pyora
server,
where
you
are
deploying,
potentially
across
virtualization
or
bare
metal
or
in
containers
as
well,
and
then
right
through
to
to
cloud
so
out
of
the
box,
both
pi,
our
server
supports
standard
cloud
runtimes
with
clustering
management
and
all
the
things
that
you'd
want,
so
that
you
can
basically
concentrate
on
building
applications
and
then
choose
your
own
time
appropriately
from
the
pi
or
stable
and
then,
after
that,
what
we
do
is
we
deliver
supported
software
for
you,
we
are
open
source,
but
the
pi
enterprise
is
a
is
a
an
enterprise
subscription
and
the
biggest
difference
for
the
enterprise
subscription
is
that
we
have
a
strong
software
life
cycle,
whereas
and
the
community
edition
obviously
changes
very
rapidly
on
a
monthly
basis.
E
We
release
new
versions
of
community
the
enterprise
product.
We
support
old
versions
back
through
pyro4,
pyro5
and
pyr6,
which
will
be
our
chicago
compatible
implementation
that
will
again
be
supported
for
10
years
and
we'll
be
supporting
three
different
versions
at
that
point
and
then
from
the
enterprise
as
well.
You
get
all
the
things
you'd
expect
from
an
enterprise
subscription,
so
we
provide
different
layers
of
support.
We
provide
security
alerts,
patching
and
all
the
things
that
you'd
expect
from
enterprise
software,
because
at
the
end
of
the
day,
cartery
applications
are
built
for
mission,
critical
production
environments.
E
It
can
deliver
microservices
architectures,
you
know
traditional
architectures,
but
fundamentally
what
you're
building
them
for
is
to
deliver
on
what
your
users
needs
are
and
your
business
requirements,
and
they
are
typically
mission
critical
and
that's
what
the
history
of
jakarta,
ee
and
javi
before
it
deliver.
That's
what
pi
r
enterprise
is
aimed
at
to
ensure
that
you
can
run
on
those
platforms.
E
So,
finally,
thank
you
for
that.
I've
got
a
picture
of
pictures
of
pizzas,
which
is,
I
was
insistent
they
put
on
by
our
marketing
team,
as
they
worked
so
hard
on
this.
So
just
finish
up
with,
as
I
say,
payara
is
so
committed
to
delivering
jakarta
either
our
team
has
been
off
making
pizzas
for
you
for
the
live
stream,
so
I'll.
E
E
B
B
You
very
much
steve
and
I
really
enjoyed
the
dismissing
the
myths
serious
you
had
this
summer,
so
go
go
out
and
watch
that
if
anyone
is
interested
in
dismissing
myths,
so
we're
right
on
time
for
a
lions
from
oracle,
welcome
will.
A
B
A
G
Okay,
great
now
steve
is
a
tough
act
to
follow
with
all
those
pizzas,
and
I
thought
oh,
the
pizzas.
I
forgot
about
the
pizza,
so
I
was
thinking
well
should
I
should
I
take
a
screenshot
of
steve's
pizzas
and
include
them
in
my
presentation,
but.
A
G
G
Here
we
go
so
and
thank
you
all
for
participating
in
this
event
and
thank
you
evar
and
tanya
for
hosting
this
event
and
all
the
people
at
the
eclipse
foundation
for
making
this
happen.
G
You
know
it's
a
great
opportunity
for
all
of
us
to
talk
about
these
technologies
and
how
we're
taking
advantage
of
them
in
this
talk,
I'm
going
to
talk
briefly
about
oracle's
participation
in
the
overall
jaccardi
process
and
what
we
are
doing
in
our
product
line
to
enable
our
users
to
take
advantage
of
the
jacardi
technologies
to
deploy
cloud
native
applications
in
java,
so
just
starting
with
oracle's
participation
in
the
jaccardi
process.
G
Excuse
me,
probably
many
of
you
are
familiar
with
the
fact
that
jacardi
e
originated
with
javi
technologies,
which
were
largely
driven
by
oracle.
G
We
worked
with
other
members
of
the
jacardi
community
to
contribute
those
technologies
in
the
form
of
specifications,
implementations
tcks
to
jacardi
ee
we've
been
a
strategic
member.
Since
the
process
began
several
years
ago
we
remain
an
active
contributor
to
jakarta
ee
and
I've
included
a
screenshot
of
the
page.
I
have
referenced.
Here's
that
show
oracle's
ongoing
contributions
to
jakarta
ee.
I'm
generally
pleased
that,
over
time,
other
vendors,
other
members
of
the
community
have
taken
an
active
role
in
leveling
the
participation
of
all
the
community
to
jacardi
technologies.
G
However,
oracle
remains
very
active,
and
this
includes
proposals
for
new
specifications
to
continue
to
bring
the
technologies
forward,
we're
also
active
in
the
micro
profile
working
group
and
contributing
to
that
effort,
which
is
very
complementary
to
ducati
ee,
so
we're
very
happy
with
the
way
the
technologies
have
evolved
and
continue
to
evolve.
G
So
now,
I'd
like
to
talk
a
little
bit
about
the
product
line
at
oracle
that
I'm
most
focused
on,
which
is
oracle
enterprise
cloud
data
of
java
and
how
that
product
line
leverages
and
enables
the
deployment
of
jaccardi
technologies
for
your
enterprise
applications
and
it
starts-
starts
with
the
oracle
weblogic
server,
which
is
a
leading
application
server
for
deployment
of
originally
java
ee
and
now
jakarta
e
applications.
Oracle
weblogic
server
is
a
dracardi
compatible
implementation
of
the
truck
to
cartie
standards
and
it
supports
cloud
native
deployments.
G
So
we
have
many
customers
who
have
deployed
their
applications,
their
weblogic
applications
running
in
containers
running
in
kubernetes
environments,
so
that
is
a
viable
path
for
you.
As
you're.
Considering
deploying
your
applications
in
cloud,
public
clouds
or
private
clouds.
Weblogic
server
is
one
of
the
deployment
platforms
you
can
use
for
those
applications.
G
We're
also
leading
the
development
and
delivery
of
helodont
helidon
is
an
open
source
project
which
provides
a
java
framework
for
building
java
based
microservices
helidon
supports
the
microprofile
standards
and,
along
with
that,
supports
key,
jakarta
ee
standards
and
can
be
used
as
a
complementary
or
as
a
standalone
technology
for
building
net
new
microservices
based
applications
in
java,
using
standards
like
micro
profile
and
jakarta
ee.
G
All
of
weblogic
coherence
and
helidon
leverage,
the
latest
in
java
technology
support
and
growl
vm
support.
So
all
these
products
are
certified
on
java.
In
the
case
of
helodon,
we're
supporting
the
latest
version
of
java
17.
All
these
products
are
certified
on
growl
vm.
In
the
case
of
helidon,
we
leverage
gravim
native
image,
support
to
enable
you
to
build
microservices
that
start
up
very
quickly
and
consume
very
little
memory.
G
G
We
recently
delivered
verrazano
1.a
1.0,
our
first
ga
version
of
verizonna,
which
is
supported
by
oracle,
which
provides
an
enterprise
container
platform
for
deploying
securing
and
managing
applications
deployed
in
kubernetes
and
in
containers
on
either
private
clouds
or
public
clouds
or
multi-cloud
environments.
G
Verrazano
is
based
on
a
series
of
cloud-native
computing
foundation,
technologies,
familiar
technologies
like
istio,
grafana,
prometheus
kubernetes,
elastic
stack,
etc.
So
we
provide
an
overall
family
of
products
which
enable
you
to
build
and
deploy
containerized
ducati
ee
applications
build
net
new
micro
services
using
helidon
that
can
run
alongside
those
dracardi
applications.
Running
in
containers
and
kubernetes
on
premises
in
public
clouds,
we
provide
verizono
for
unifying
management
of
those
applications
deployed
with
those
frameworks
with
multi-cloud
support.
Meaning
deployments
can
be
managed
across
multiple
clouds
and
open
run
time
support.
G
G
We've
released
the
first
version
of
verrazano
have
an
update
coming
soon
have
delivered
recently,
a
number
of
updates
to
our
tools
for
running
weblogic
and
kubernetes
updates
to
our
cloud
support:
new
releases
of
coherence,
community
edition,
new
releases
of
helidon
support,
supporting
micro
profile
3.3,
with
a
new
release
of
halidon,
supporting
micro
profile
5.0
in
development
plan.
2..
Excuse
me
too
much
to
talk
about
these
slides
will
be
available,
and
here
are
some
links,
so
you
can
get
to
more
information
about
our
product
line.
Thank
you
very
much.
B
B
Thank
you
will
and
thank
you
for
this
presentation
with
all
these
cool
and
amazing
technologists
and,
as
you
said,
the
next
speaker
up
is
david
blevins
from
tomico
tribe,
so
welcome
david.
F
All
right,
I
can't
share
yet
but
you're
able
to
hear
me
right.
Yeah.
A
F
Okay,
let
me
share
okay,
so
my
name
is
david
blevins
and
I'm
the
co-founder
and
ceo
of
pet
of
tommy
tribe.
So
just
very
briefly,
tommy
tribe
is
a
is
a
company
founded
from
members
of
the
apache
software
foundation
that
you
know
created
tommy
at
the
apache
software
foundation.
F
I
like
to
say
that
the
company
is
built
from
the
community
a
lot
of
times.
Companies
try
to
take
credit
for
building
the
you
know
the
software.
Certainly
we
do
actively
do
that,
but
it's
really
the
reverse
the
community-built
company,
so
everybody
in
the
company
is
basically
an
apache
contributor
and
the
primary
thing
we
do
for
people
is
offer
support
for
tommy
tomcat
activemq
and
we
actually
have
our
own
api
gateway,
tribe
stream,
that
we
support.
F
Tomcat
distributions
are
frequently
just
you
know,
discontinued,
like
seven
was
very
recently
discontinued,
and
we
do
still
maintain
that
for
people
we
also
have
a
community
partnership
program,
which
is
a
really
really
great
way
to
it's
kind
of
like
an
airline
rewards
where
we
give
you
free
services
like
feature
development
of
the
open
source.
F
So
that
way
you
can
sort
of
say,
hey,
I'm
spending
this
money
with
you.
I
need
these
things
from
the
open
source
project.
Can
you
give
them
to
me
and
we
kind
of
see
that
as
an
integral
way
for
us
to
get
you
involved
in
the
open
source
community?
F
So
we
had
some
really
interesting
milestones
this
year,
which
we're
super
proud
of.
So
the
first
one
is
that
apache
tommy
got
certified
this
year,
which
was
a
tremendous
accomplishment.
F
You
know
the
history
here
is
that
you
know
apache
lost
the
access
to
the
you
know,
java
tck
in
2013,
I
should
say
it
expired
and
apache
chose
not
to
renew
and
so
and
that
put
us
in
a
situation
where,
1.5
years
after
we
announced
tommy,
we
no
longer
had
the
ability
to
certify
any
eu
releases,
so
that
was
real
tough.
F
F
F
We
did
do
by
code
transformation
using
the
eclipse
transformer
and
some
tooling
of
our
own,
and
that
is
fantastic,
but
there
are
some
limitations
in
terms
of
getting
all
of
our
our
jars
up
into
maven
central
in
the
byte-coded
transformed
package,
which
does
affect
our
killian
tooling,
and
things
like
that,
so
we
decided
to
opt
for
going
for
a
straight
jakarta
switch.
F
The
great
thing
is
is
because
we
were
you
know
behind
on
the
spec
revisions.
The
transformation
process
allowed
to
allow
us
to
basically
improve
the
compliance
of
tommy8
and
tommy9
in
parallel,
so
that
was
absolutely
fantastic.
F
After
we
switch
that
we're
going
to
be
going
straight
into
taking
the
main
branch
to
jakarta
e10,
another
milestone
that
happened
this
year
is
the
apache
software
fashion
foundation
joined
the
jakarta
ee
working
group
as
a
guest
member.
So
that
was
a
really
really
great
thing
to
see.
You
know:
apache
famously
left
the
jcp
in
2010
over
licensing
issues
right
and
now
that
everything
is
all
open
source
and
those
licensing
issues
are
gone.
F
F
But
the
great
thing
about
that
is
just
very
symbolic
of
the
continued
healing
that's
happening
because
of
jakarta
ee,
and
so
it's
a
real
success
for
us
as
a
community,
and
I
do
want
to
talk
about
you
know
now
that
we're
certified.
You
know
the
the
importance
of
diversity
in
our
standards
and
where
apache
plays
a
role
in
that
you
know.
F
So
when
we
talk
about
you
know
standards,
you
know,
standards
create
portability
which
enable
multiple
implementations
that
creates
technical
competition,
which
is
something
steve
mentioned
earlier,
and
that
drives
innovation
and
delivers.
You
choice
right
and
that's
super
important.
That's
the
whole
reason
that
we're
here
is
to
basically
compete,
create
innovation
and
drive
choice,
and
so
you
know
we
do
have
you
know
you,
you
may
choose
one
specific
server
in
your
implement.
F
You
know
to
roll
out,
but
regardless
all
the
servers
and
all
the
implementations
are
actually
working
for
you,
because
they're
driving
innovation
into
the
specification
and
that
gets
delivered
to
you
through
the
implementation
you
choose
and
the
more
implementations
that
are
there,
the
more
innovation
that
that
will
get
delivered
to
you,
and
so
you
know,
regardless
of
what
server
you
choose,
they
all
definitely
deliver
you.
Some
value.
F
If
we
look
at
some
of
the
individual
specifications,
the
diversity,
you
know,
you
can
see
that
that
the
apache
implementations
play
an
absolutely
critical
role
in
maintaining
the
diversity
of
our
component
specifications.
So
if
you
look
at
cdi,
we
see
that
open
web
beans
is
kind
of
the.
You
know
lone
other
implementation
of
cdi
and
is
used
by
you
know
tommy,
and
so
you
know,
if
tommy
and
cdi
were
wiped
off
the
face
and
open
webbings
were
wiped
off
the
face
of
the
planet.
F
We
would,
we
would
not
have
the
diversity
there
right
and
the
story
continues
on
a
lot
of
specifications
we
have
apache
b
val,
which
provides
the
only
other
implementation
of
beam
validation.
Geronimo
whale
provides
the
only
imp,
other
implementation
of
jakarta
mail
activation,
the
only
other
general
activation.
F
The
only
other
implementation
of
activation
my
faces
provides
the
only
other
implementation
of
jsf
and
we
can
keep
going
to
spec
after
spec,
where
there
are
basically
the
apache
project,
holding
strong
and
delivering
some
great
diversity
to
our
ecosystem,
and
so
you
know,
I
think,
there's
an
important
statement
to
be
to
be
made
there.
That
apache
provides
diversity
where
it
wouldn't
exist.
F
Otherwise,
and
that
makes
patchy
a
really
really
critical
contributor
to
jakarta
ee
and
you
know
vital
to
all
of
our
success
right,
and
so
I
think
you
know,
there's
a
call
to
action
that
can
that
can
happen
there
is
that
you
know
the
great
way
to
support
diversity
and
add
more
strength
to
this
open
standards,
ecosystem
that
we're
building
and
strengthening
and
putting
ourselves
in
a
better
situation
than
we've
ever
been
is
you
know,
contribute
to
apache
projects?
Don't
forget
them.
F
You
know
it's
it's,
it's
always
great
to
look
at
the
the
pot.
You
know
the
stuff
that's
close
to
where
the
standards
are
being
developed,
but
you
know,
keep
your
eye
on
the
apache
projects
and
and
also
realize
that
they're
there
to
be
contributed
to,
and
if
you
want
to
start
an
apache
project.
F
F
Go
ahead
and
ping
me
and
I'll
help
you
through
that
process
and,
of
course,
if
you're
not
in
a
position
to
contribute
to
projects.
You
know,
of
course,
do
business
with
tommy
tribe,
because
we
pay
salaries
of
people
who
work
on
these
things,
and
so
you
know
all
of
this
is
is
a
great
way
to
strengthen
jakarta
ee
as
a
whole.
It's
something
that
you
can
do.
F
I
know
we
look
a
lot
of
times
at
the
vendors
and
look
what
they're
doing,
and
we
forget
that
we
are
the
wind
beneath
their
wings
and
our
actions
deliver
great
value
to
jakarta,
ee
as
a
whole,
and
so
you
know
I
would
say,
think
about
that,
and
you
know
it's
it's
super
important,
so
I
am
super
proud
of
the
accomplishments
that
we've
all
made
this
year.
We
are,
through
the
whole
eight
nine
process,
we're
starting
to
do
major
changes
with
jakarta
ee10.
F
We
are
getting
implementations
like
ourselves
back
in
the
game
that
had
struggled
because
of
access
to
tcks
and
things
like
that.
We
are
getting
our
diversity
back.
Basically,
all
these
projects
at
apache
got
certified
for
the
first
time
this
year
and
prior
to
that,
we
only
had
just
the
one
implementations
of
the
majority
specifications
so
we're
making
some
major
major
major
progress.
F
You
can
support
that
and
you
know
we.
We
appreciate
you
listening
and
thank
you
for
the
time.
B
One
of
the
compatible
implementations.
F
B
Good
at
being
on
time-
and
I'm
I'm
happy
to
to
invite
tatiana
from
gelastic
here
to
come
online,
and
you
can
probably
pronounce
your
name
more
correctly
than
I
did.
C
C
You
liking
commitment,
so
so
yeah
guys
I'm
director
of
product
marketing
and
virtuoso
company
at
the
moment,
and
I
would
like
to
share
a
bit
more
details
how
our
company
is
connected
with
the
jakarta
e
and
java
world
in
general
and
specifically
july
state
division,
because
this
year
july
state
became
a
part
of
big
bertholds.
C
Family
and
bertoza
has
a
huge
history
of
over
20
years
in
virtualization
market
in
containerization
cloud
hosting
and
now
we
are
part
of
this
team
and
the
services
are
already
delivered
to
more
than
700
service
providers
across
the
world.
We
are
proud
to
be
so
widely
used
by
all
the
service
providers
and
now
julystick
devops
platform
as
a
service
is
also
included
to
the
product
line
of
burton.
C
Mainly,
our
aim
is
to
make
the
life
of
developers
and
admin
guys
easier
while
running
different
types
of
applications
scaling
them
clustering,
making
the
deployment
process
as
easy
as
possible
with
the
help
of
our
platform,
and
this
platform
is
currently
available
already
across
more
than
100
data
centers
in
different
countries
and
can
be
installed
on
different
infrastructure.
C
This
can
be
bare
metal
or
any
infrastructure,
as
a
service
that
you
prefer,
but
initially
gelastic
was
mainly
jelastic
was
java
elastic
platform,
and
even
the
name
is
the
acronym
for
java
elastic,
because
we
were
providing
java
services
java
platform
for
customers,
and
we've
studied
this
purely
java
oriented
platform.
Only
afterwards
we
were
growing
bigger.
We
were
adding
new
functionality,
but
java
is
always
in
our
hearts,
so
we
keep
working
on
this
direction
very
deeply
and
community
thanks
to
the
community.
C
That
is
really
pleasant
for
us
to
know
that
the
community
sees
our
efforts
to
make
java
technology
even
better,
with
the
help
of
our
platform,
and
currently,
we
are
also
actively
involved
in
jakarta
and
microprofile
working
groups
trying
to
improve
the
flow
and
also
trying
to
get
the
technology
to
the
end,
customers
to
the
developers
and
developers
community
as
fast
as
possible
and
spread
it
to
across
the
cloud
and
across
all
the
service
providers
we
are
working
with
and,
for
instance,
I'm
involved
in
this.
C
As
a
marketing
committee
representative
happy
to
help
anytime
that
I
can
here
and
in
terms
of
technology,
we
were
one
of
the
first,
not
one
of
the
first,
but
we
were
the
first
cloud
platform
that
included
jakarta
e9
to
the
support
of
the
platform
and
repeatedly
we
don't
have
pizza
this
time.
But
I
decided
to
keep
our
nicely
done
cake
from
previous
time.
So
yeah.
C
Absolutely
that's
totally
done
for
jakarta
support,
and
nowadays
we
are
trying
to
push
the
latest
versions
as
fast
as
possible
for
the
community
to
have
access
to
the
features
for
the
community
to
be
ready
to
use
them
already
in
the
cloud
hosting
way,
and
we
also
tightly
worked
to
make
the
deployment
of
java
and
descartes
ie
applications
as
easy
as
possible.
C
So,
for
instance,
we
had,
we
have
been
asked
to
deploy
cargo
tracker
as
one
of
the
departe
applications
to
run
it
inside
kubernetes
inside
our
platform,
and
now
it's
running
successfully
with
all
the
features
included
and
everyone
can
go
to
the
wrapper
and
try
it
by
yourself
so
yeah,
basically,
with
the
platform
that
we
are
offering,
you
can
run
any
departure
here,
application.
You
don't
need
to
change
the
code,
you
don't
need
to
tune
it
a
lot.
C
In
addition
to
that,
we
provide
fully
automated
vertical
scaling,
so
customers
just
put
to
the
maximum
scaling
limit,
and
then
the
system
automatically
provides
the
required
resources
when
they
are
needed
and
takes
them
back
when
they
are
not
required
anymore
and
as
a
result,
this
helps
to
not
overpay
and
forget
about
right
sizing
problem,
because
you
don't
need
to
think
how
much
resources
you
need
at
this
point
and
how
much
resources
you
will
need
in
a
month
or
in
a
day
or
when
the
load
spike
goes
up,
because
the
system
will
think
for
you
about
that,
and
if
you
don't
need
those
resources,
the
system
takes
them
back,
so
you're
not
going
to
pay
for
that
you're
going
to
pay
only
for
actually
consumed
resources
and
this
kind
of
model
in
a
way
unique
nowadays
in
cloud
hosting,
and
we
hope
that
it
will
be
widely
spread
across
all
cloud
platforms
as
well,
because
we
consider
this
as
the
most
fair
way
to
to
have
the
pricing
of
this
way
for
cloud
customers.
C
In
addition
to
that,
you
have
a
possibility
to
scale
the
servers
horizontally.
This
can
be
manually
or
also
automatically
so
again,
you
just
set
up
specific
triggers
using
user
interface
rather
intuitive,
and
you
forget
about
the
resource
shorter
nature
resource
over
consumption,
because
the
platform
will
be
thinking
for
all
of
that
behind
your
back,
so
you
can
relax,
enjoy
your
life
work
on
your
projects
and
the
system
will
manage
all
the
infrastructure
and
service
stuff.
For
you,
and
also
talking
about
clusterization.
C
We
have
opportunity
to
get
automatic
clustering
for
populated
party
servers
and
java
servers.
You
don't
really
need
to
have
big
skills
to
do
that.
You
just
go
to
the
ui,
enable
auto
clustering
and
the
system
will
provide
this
sort
of
clustering
for
you
out
of
the
box.
As
a
result,
the
servers
will
be
synchronized.
You
will
get
load
balancing
on
top
to
distribute
the
load.
C
You
will
get
the
dust
node,
for
instance,
if
you
are
talking
about
glass,
fish
and
the
resources
will
be
provided
automatically
as
well
within
this
cluster,
no
need
to
go
deeply
inside
either.
You
don't
have
experience
or
you
just
don't
have
time
on
this
kind
of
routine
stuff.
You
can
just
automatically
get
it
out
of
the
box
and
this
is
available
within
our
devops
platform
for
you
already
nowadays.
C
So
I'm
going
to
be
short
so
because
I
see
that
we
are
short
of
time.
So
thank
you
for
listening
and
if
you're
going
to
have
any
questions
you
can
get
in
touch
with
me
directly
via
twitter,
for
instance,
or
you
can
get
in
touch
with
the
gelastic
or
virtuoso
team,
and
we
will
help
you
to
make
your
party
and
java
applications
scalable
and
efficient.
A
Right
on
time,
I
was
trying
to
be
fast.
Yes,
thank
you.
Thank
you
so
much.
This
was
great.
We
appreciate
you
being
part
of
this
big
event
and
part
of
jacarte
community
and
what
we'll
move
just
along
yeah.
B
So
the
next.
A
And
not
just
that
and
thank
them
for
being
part
of
this
amazing
working
group
for
supporting
the
working
group
and
sponsoring
events
like
this.
So
it's
a
privilege.