►
From YouTube: Why Jakarta EE? - 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
It
was
actually
a
quite
nice
talk
from
was
Laura
about
the
starter
project
right.
B
Yeah
and
we
do
want
to
focus
on
the
on
the
new
developers
and
new
contributors,
so
it
was
really
right
on.
A
Yeah
and
and
today
we
actually
had
a
great
selection
of
talks
and
we
have
three
more
so
please
stay
tuned
and
keep
watching
right,
yeah,
so
I
think
today
we
talked
about
jakarti,
10
11,
and
we
Tony
actually
mentioned
that
next
year
is
going
to
be
the
fifth
anniversary
for
Jakarta.
B
A
So
I
think
it's
important
for
us
to
talk
about
the
importance
of
a
Jakarta
AE
and
and
why
developers
should
use
it
right
yeah.
So
what
do
you
think
Tony,
or
what
do
you
think
is
important
so.
B
First
thing
that
I
want
to
say
is
and
mention
again
and
again,
the
platform
project
and
all
the
conversations
that
are
happening
on
the
jakarti
platform.
Mailing
list
so
please
tune
in.
There
is
actually
quite
an
interesting
conversation
that
is
happening
right
now,
so
I
would
alert
you
to
join
in
and
and
be
part
of
it
and
observe
what's
going
on
there.
B
So
in
terms
of
why
do
I
think
jakarti
is
important.
Well,
jakarti
is,
is
a
successor
of
java,
ee
right
and
javai
has
been
proven,
standard
and
and
set
of
specifications
throughout
the
actually
two
for
two
decades
before
even
Jakarta
came
into
picture
for
a
development
of
the
Java
Enterprise
systems,
so
it
is,
it
has
been
proven
technology
that
has
been
focused
on
clear
separation
between
application
development
and
anything
that
is
related
to
run
time
and
the
infrastructure.
B
So
that
is
the
true
initial
and
and
continuous
value
of
the
jakarti
jakarti
is
also
as
opposed
to
many
other
Frameworks
out
there
open
multi-vendor
ecosystem
that
allows
playing
field
level
playing
field
for
for
everyone
to
participate.
So
if
you
look
at
our
working
group
members,
we
do
have
everyone
from
jugs
to
you
know
small
startup
companies
to
medium
companies,
and
then
you
know
I
would
call
Mega
companies
like
IBM
Oracle,
Red
Hat.
Now,
recently,
micro
Microsoft
I
was
going
to
say
microsystem.
B
Some
Microsystems
is
way
back
in
the
history,
but
Microsoft
were
super
happy
to
to
have
them
as
a
as
part
of
our
community.
So
from
that
perspective,
Jakarta
really
is
set
up
as
I
mentioned
set
of
specifications
and
and
it
needs
a
standard
that
others
use
to
develop
their
implementations
and
support
Java
Enterprise
developers.
It
is
a
reliable
sustainable.
B
You
know
it's
vendor
neutral
and
that
is
actually
of
the
extreme
importance
to
our
customers,
who
don't
need
to
feel
feel
locked
in
with
one
vendor
only
and
now
also
I
do
want
to
mention
and
played
up
from
the
importance
of
of
Jakarta
e.
That
Jakarta
plus
microprofile
is
a
very
powerful
combination
that
answers
all
the
needs
of
the
new
Cloud
application.
Architectures,
but
I
do
also
that,
for
example,
that
that
are
relying
on
on
building
assistance
based
on
on
microservices.
B
But
at
the
same
time,
not
all
the
all
new
applications
are
built
based
on
the
micro
services
and
Jakarta.
Ee
can
answer
needs
of
many
many
applications
out
there
that
are
still
very
relevant
for
the
cloud
native,
but
not
necessarily
need
to
build
upon
microservices,
and
if
they
do,
they
could
do
it
even
with
with
without
microprofile,
but
as
I'm
I
was
saying.
B
Micro
profile
and
Jakarta
is
definitely
a
very
powerful
combination,
and
it
is
really
not
like
some
of
some
of
our
users
are
are
continuously
mentioning
yes,
but
anything
Jakarta
e
can
do
with
or
without
micro
profile
spring
or
spring
boot
can
do
it
as
well.
Well,
that
is
true,
but
it
is
not
necessarily
healthy
for
our
community
to
be
have
to
to
have
just
one
option
available
to
them.
B
There
are
many
other
options,
and
one
of
them
are
is
definitely
Jakarta,
so
I
would
invite
everyone
to
look
into
all
the
different
reasons
and
all
the
different
specifications
that
Jakarta
is
offering
and
do
remind
you
that
most
of
the
Frameworks
out
there
are
still
relying
on
some
of
the
Jakarta
specifications
as
well.
B
So
while
someone
can
interpret
yes,
but
you
know,
it
is
basis
for
other
Frameworks,
one
can
also
say
well:
I,
don't
necessarily
need
to
use
other
Frameworks
I
can
just
use
directly
Jakarta,
so
the
options
are
out
there
for
for
the
user
right,
but.
A
Yeah
all
great
points
actually
Tanya,
but
we
want
to
hear
from
you
as
well,
so
please
feel
free
to
put
in
the
chat
section.
You
know,
what
do
you
think
is
the
importance
of
Jakarta
and
why
developers
should
care
about
Jakarta.
We
want
to
hear
from
you
as
well,
and
we
actually
have
a
video
that
we
interviewed
some
of
our
community
members
and
ask
them
why.
B
C
So
I
think
the
significance
here
is.
It
really
enables
us
to
have
Innovation
within
Enterprise
level,
Java
that
enables
us
whether
you're,
using
microservices
or
monoliths,
whether
you've
got
a
Brownfield
application
or
a
Greenville
application.
It
allows
us
to
introduce
that
Innovation
as
and
when
we're
ready
and
enables
us
to
have
access
to
that
Innovation
as
it
comes
out,
and
the
great
thing
about
it
being
open
source
is
that
you
can
have.
D
D
Chicory
is
sort
of
everywhere
and
the
way
we
experience
that
with
Ducati
in9
was
that
we
changed
the
namespace
and
we
changed
it
from
java
X
to
Jakarta,
and
you
would
think
that
was
kind
of
a
thing
that
would
affect
Chicago
developers,
but
it
kind
of
rippled
through
the
entire
ecosystem.
So
everything
from
Spring
framework
to
Spring,
Boot
and
tomcat
and
Jetty
and
hybrid,
and
you
name
it.
Everybody
will
accept
affected
by
this
name
so
exchange
and
we'll
have
to
do
some
work
in
order
to
get
there.
B
Jakarta
e
really
provides
update
to
the
existing
technology
and
is
enabling
Java
Enterprise
developers
to
move
forward
into
the
cloud
era.
So
any
Java
Enterprise
developer
needs
to
be
aware
of
jakarte
as
one
of
the
few
solutions
for
enabling
Java
Enterprise
developers
to
focus
on
the
business
part
of
the
application
and
not
necessarily
needing
to
worry
about
the
lower
level
infrastructure
interactions.
E
By
being
a
standard
compliant
and
using
the
specs
that
Jakarta
e
provides,
users
are
independent,
so
they
are
not
tied
to
a
particular
vendor.
If
that
vendor
gets
purchased
or
even
should
go
bankrupt.
Someday
that
means
being
standard
comfortable
has
them
on
the
safe
side,
so
they
are
not
with
a
technology
that
may
longer
be
available
or
not.
May
no
longer
be
affordable.
F
You
know
today,
Jakarta
without
this
technology,
Java
wouldn't
be
what
it
is.
There
wouldn't
be
as
many
players
it
wouldn't
be
as
broadly
adopted
as
it
is
today.
So
it
is
very
important
to
keep
this
technology
relevant
and
strong,
but
ultimately
every
single
Java
developers,
career
and
livelihood
actually
depends
on
the
on
the
health
and
success
of
this
technology.
You
know
again
for
in
the
next
10
or
20
years
or
more.
We
hope.
G
G
G
Infrastructure
implementation,
the
dot
container,
whether
or
not
it
runs
in,
is
infrastructure.
The
clouds
are
not
your
reference
on
its
infrastructure
as
developer,
you
can
really
focus
on
only
the
technology
that
you
want
to
use
for
building
business
features.
Everything
else
can
be
left
to
the
people
with
infrastructure.
A
Okay,
so
that
was
quite
interesting.
So
actually,
let's
continue
this
conversation
in
the
next
studio
session.
But
why
don't
we
look
at
the
next
speaker
and
and
okay
join
that
talk.
B
So
we
we
heard
quite
a
bit
about
Java
today
and
and
Enterprise
our
development,
but
we
didn't
really
talk
about
testing,
so
our
next
talk
is
going
to
be
really
important
because
it's
talking
about
easy
Java
integration,
testing
with
test
containers
and
the
Fabio
will
tell
us
all
about
it.
So
why
don't
we
flip
it
over
to
Fabio
and
and
learn
about
testing.