►
From YouTube: Foundations of Modern Java Server Apps - JakartaOne 2022
Description
Java has a long history of running on the server. From the early days of servlets to JSP, Java web frameworks, Java EE, and Spring, to today’s hip microservice frameworks, the platform has been a strong, solid player, relied upon by thousands of companies, governments, and organizations. But what do these microservice frameworks like Dropwizard, Spring Boot, and Eclipse MicroProfile have in common with the older days of Java? It turns out, there’s quite a lot of foundational tech that made the newer frameworks possible. In this talk, we’ll take a look at different parts of the foundation that you may not even realize you’re using, for everything like handling REST requests, processing JSON, using Web Sockets, talking to a database, performing validation, and more. We’ll also look at how these standards evolve within the Eclipse Jakarta EE, and what’s in store for the future.
-
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
Okay,
so
I
guess
we're
light
now
hi
my
name
is
keto,
and
this
session
is
called
foundations
of
modern
Java
server
apps.
You
can
find
this
session
and
other
ones
at
ketoman.com.
If
you
want
some
more
information
and
I
hope
you
guys
have
enjoyed
the
the
whole
day
today.
I
know
it's
been
a
long
day,
so
for
better
or
worse,
I
guess
I'm,
not
in
the
last
session.
So
before
I
begin
I'll,
just
tell
you
a
little
bit
about
myself.
A
I
am
the
principal
consultant
at
Virtua,
where
we
do
training,
Consulting,
mentoring,
architecture,
all
around
Java,
Jakarta,
ee
web
components,
macro
profile.
Also,
some
front-end
development
too,
like
with
web
components,
angular
and
even
some
react,
sometimes
so.
Basically,
full
stack
development
with
job
on
the
back
end
and
then
also
a
cloud
deployments
as
well.
A
We're
currently
working
on
a
a
project
called
speaker
tracks,
which
you
should
check
out
if
you
like
well,
if
you're
a
frequent
speaker,
conferences
or
meetups
or
or
things
like
that,
it's
just
basically
a
partner
to
help.
You
track
that
stuff
I'm
the
co-host
of
the
stack
podcast,
which
is
podcast
about
front-end
and
back-end
development.
In
the
Enterprise
space,
a
lot
of
stuff
about
Java,
there's
like
three
Java
Champions
on
there,
so
there's
me:
Josh,
Gino,
Daniel,
inahosa
and
also
Ian
labitz,
and
we
basically
every
month
or
so.
A
A
A
A
But
basically
you
know
you
have
your
your
Docker
or
oci
container
and
then
inside
of
it
you
have
some
sort
of
Deployable
units
that
represents
your
application
and
then,
of
course
you
have
your
code,
and
that
is
your
business
logic.
That's
all
of
your
your
fun
stuff
and
then,
of
course,
as
is
typical
in
any
application.
These
days,
you
have
the
Giants
that
you're
built
on
top
of
so
you'll
have
some
sort
of
microservice
framework
and
you'll.
A
A
A
A
A
You
may
want
to
send
email.
This
is
something
we
don't
think
about
too
often,
but
pops
up
relatively
often
it's
like
oh
I-
need
to
send
an
email.
How
do
I
do
that?
Well,
you
need
some
sort
of
API
and
then,
of
course,
we
get
it
into
the
the
more
microservice
specific
features
right.
You
need
health
checks,
so
you
want
the
ability
to
send
a
requests
to
your
endpoints
or
endpoints
and
determine
you
know
this
database
up.
Is
my
service
healthy?
A
A
You
you
can
log,
you
know
if
you
paid
attention
to
the
session
identifier
or
the
user
ID,
or
something
or
created
your
own,
unique
identifier,
you
could
follow
it
throughout
the
user's
life
cycle,
but
when
you
have
a
whole
bunch
of
macro
Services
that
are
processing
a
a
user's
Journey,
you
need
some
way
to
trace.
What's
going
on,
so
you
need
some
sort
of
distribution
for
that
and
then,
of
course,
you
know
if
you
have
different
different
microservices,
you
may
need
to
do
some
actual
fault
tolerance
right.
A
A
Then,
of
course,
there's
metrics,
so
you've
got
a
whole
bunch
of
services,
and
now
you
need
to
take
a
step
back
and
figure
out.
You
know:
are
they
performing
with
they're
supposed
to
what's
the
database
performance
like?
What's
the
you
know
how
many
requests
I
get
per
second,
you
know
all
that
kind
of
fun
stuff,
so
you
need
metrics
for
that.
For
that.
A
And
then,
if
you
have
a
rest,
endpoint
or
a
set
of
rest
in
points,
you
want
to
be
able
to
document
them
in
some
sort
of
standard
format.
So
that's
where
open
API
documentation
comes
in
handy,
so
the
ability
to
generate
that
automatically
will
save
you
a
lot
of
time
and
then,
if
you
aren't
doing
the
rest
endpoint,
you
may
want
to
use
something
like
graphql,
so
some
microservice
Frameworks
Provide
support
for
graphql
as
well
as
an
alternative
to
rest.
A
A
So
let's
take
a
look
at
how
that
actually
works,
and
you
know
a
real,
a
real
framework.
So,
let's
start
with
spring
boots
so
spring
brute,
as
most
people
know,
is
pretty
much
the
most
popular
framework
for
doing
microservices
these
days.
And
if
you
take
a
look
at
how
it's
built,
it
uses
the
spring
philosophy.
It
has
all
these
same
features.
A
A
Okay
and
then,
of
course,
you
need
to
do
your
your
Json,
serialization
and
deserialization,
and
for
that
you
can
use
Jason
Jackson,
which
is
the
most
popular
or
Jason
binding,
and
for
parsing
you
can
use
Jason,
Jackson
or
Jason
parsing.
Okay
for
validation.
You
have
one
choice,
which
is
Jakarta,
Bean,
validation
and
I
should
mention
Jason,
binding
and
Jason.
A
So
for
security.
You
have
Spring
Security,
which
has
been
around
for
a
long
time.
It's
pretty
robust
for
persistence.
You
can
use
jpa,
you
can
use
Jakarta
persistence
and
there's
several
other
options
as
well
like
spring
data
Etc
and
for
dependency
injection,
of
course,
you're
going
to
use
spring
framework,
which
is
the
core
of
spring
for
messaging.
You
can
actually
use
to
cartoon
messaging
or
you
can
also
use
Kafka
or
other
messaging
providers
for
mail
you're,
going
to
use
either
the
spring
Java
mail,
sender
or
Jakarta
mail
for
health
checks.
A
A
A
So
carcass,
just
if
you're
not
aware,
is
another
micro
profile,
I'm,
sorry,
it's
another
microservice
framework
for
Java,
it's
from
Red
Hat
and
it's
relatively
popular
and
the
way
it
handles
things
again.
You've
got
your
Docker
container
and
your
you
have
an
executable
jar
or
native
image
and
I
should
mention
for
spring.
The
native
stuff
is
really
new
for
quarkus.
It's
been
around
longer,
at
least
that's
my
understanding.
A
A
You
can
also
use
Jakarta
restful
web
services,
Jackson
or
Jakarta
Jason,
binding
and
Jackson,
or
the
Carter
Jason
parsing.
For
for
your
Json
work
for
validation,
use,
Bean
validation
for
security.
You
can
use
quarker
security,
which
is
their
own
implementation
of
a
lot
of
different
security
features,
but
that
does
use
micro
profiles,
JWT
world-based
authentication.
A
A
For
messaging,
you
can
use
Kafka,
Jakarta
messaging
others
for
mail.
We
have
Quark
as
male
for
Health.
You
use
Market
profile
health
or
tracing
they're,
currently
using
open
Telemetry.
Although
we'll
talk
about
this
a
little
bit
later,
but
I
I'm,
pretty
sure
there
I
don't
know
for
sure.
Someone
can
correct
me
if
I'm
wrong,
but
I'm
pretty
sure
they'll
be
switching
to
a
micro
profile,
open,
open
macro
profile,
Telemetry,
which
we'll
be
up.
I'll
talk
about
later
for
fault,
tolerance.
They
have
macro
profile,
fault,
tolerance
for
metrics.
A
A
So
quercus
is
built
using
a
lot
of
standard,
Jakarta
e-specs,
some
specific
quercus
features,
or
just
you
know
only
in
the
carcass
world,
and
then
it
also
uses
several
different
micro
profile
specifications
and
some
popular
libraries
like
open,
Telemetry
and
micrometer
and,
of
course,
I'm
going
to
integrates
with
other
sorts
of
Technologies.
It
uses
those
apis
as
well.
A
A
So
again
we
got
your
code.
We've
got
para
micro.
It
has
most
of
these
features.
It
doesn't
have
graphql,
but
you
know
I'd
say
even
as
much
as
I
love
graphql.
Most
most
people
are
not
using
it
anyways,
so
they're,
just
writing.
Rest
endpoints!
You
have
everything
you
need
so
for
the
HP
integration
we
had
Grizzly,
which
was
a
part
of
glass
fish.
A
For
the
HTTP
Java
integration
we
have
Jakarta
servlet
rest
processing
is
Jakarta
restful,
API
apis
and
my
my
slides
are
getting
ahead
of
me
here
and
We've
also
got
Jakarta
Json,
binding
and
descar's
adjacent
parsing
and
Chicago
Bean
validation
for
security.
We
have
Jakarta
security
and
and
also
microprofile
JWT,
role-based
Authentication,
and
those
two
work
pretty
well
together.
A
There's
been
some
talk
about
how
the
bill
will
work
together
in
the
long
term,
but
but
definitely
they
serve
different
purposes,
so
they
work
pretty
well,
while
Jakarta
security
provides
sort
of
the
higher
level
apis
and
ways
of
handling
authentication
things
like
that.
Of
course,
the
micro
profile
awt
handles
specifically
the
the
jot
side
of
things.
A
So
then
for
database
integration,
we
have
to
Carter
persistence
for
a
dependency
injection.
Cdi
messaging
is
Jakarta
messaging,
males,
Jacquard
to
male
health
checks.
You
get
micro
profile,
health
tracing,
you
have
Market
profile,
open
tracing
fault,
tolerance,
shift,
micro
profile,
fault,
tolerance,
metrics.
A
You
have
macro
profile,
metrics,
there's
also
micro
profile,
config
and
micro
profile,
open
API,
so
so
paramicro-
and
this
is
not
the
only
implementation
you
can
find
the
same
thing
with
open,
Liberty
or
other
server
runtimes,
where
they
basically
are
using
almost
all
of
the
micro
profile
specifications
and
many
of
the
jakarte
specifications.
So
so
you
can
get.
You
know,
we've
kind
of
gone
from
Spring
having
you
know,
a
future
card
to
eat
pieces
to
paramaco
using
pretty
much
all
of
them.
A
A
So
we've
got
two
standards:
bodies,
multi-vendor,
providing
a
lot
of
the
under
underlying
apis
that
are
in
use
here
and
I
should
mention
that
micro
profile
6,
which
is
is
I,
believe,
was
released
today.
I
think
I
didn't
see
all
the
sessions
Market
profile.
Six
actually
is
using
micro
profile
Telemetry
instead
of
open
tracing,
and
so
this
is
a
new
specification
that
replaces
the
old
apis.
A
A
I,
don't
know,
hopefully
nobody's
talked
about
this
too
much
yet
today,
but
so
micro
profile
has
actually
started
in
2016.
and
it
seems
like
it's
it's
kind
of
hard
to
leave.
It's
been
that
long
now,
and
it
was
it
started
basically
as
as
a
way
to
handle
the
lack
of
development
on
the
current
on
the
job
AE
side
before
it
became
Jakarta,
and
these
are
all
of
the
well
that
that
link.
A
There
gives
you
essentially
the
the
initial
blog
post,
which
is
still
there
on
Tommy,
try,
which
is
nice
and
you'll,
see
down
here.
These
are
all
the
committers,
so
in
addition
to
the
ones
I've
mentioned,
Microsoft
is
now
on
there
and
there's.
Also
a
few
Java
user
groups
as
well
I
mean
Fujitsu,
is
a
is
a
big
committer
as
well.
So
so
it's
not
just
the
initial
ones,
I
mentioned
earlier
and
again
I.
A
A
A
But
you
know
these
are
some
of
the
common
annotations
that
we
always
see
in
our
in
our
Jakarta
apps,
when
you're
dealing
with
CDI
and
also
the
djp,
but
we'll
we'll
leave
we'll
talk
about
CGI
CDI.
Excuse
me,
you
often
have
you
have
to
write
interceptors,
The,
Intercept
method
calls
essentially
and
that's
a
key
part
of
Jakarta
EE,
and
also
a
lot
of
the
good
old
jsr
300
I
think
it
was
303
annotations.
A
That
Springs
as
well
so
so
you
know
these
are
a
lot
of
specifications
that
are
basically
required
by
the
ones
that
are
in
Gray.
So
that's
what
we
have
in
the
core
profile
now
I've
highlighted
something
else
here
which
is
called
the
web
profile
and
I'm.
Sure
many
of
you
remember
this,
and
many
of
you
probably
still
use
it,
and
essentially
these
are
the
set
of
apis
which
are
useful
for
web
applications.
A
These
days,
like
jstl
to
Carter
standard
tag,
libraries
managed
beans
have
actually
been
deprecated,
they're,
actually
part
of,
because
you
know
you
can
basically
use
CDI
instead,
but
also
there's
other
things
like
the
card
tickets
currency
which
lets
you
use
a
lot
of
new
concurrency
constructs
in
a
managed
environment
and
some
other
features
as
well.
So
all
those
are
part
of
the
web
profile.
A
So
a
lot
of
times
you
may
have
you
know
an
app
that
ends
up
using
more.
Some
of
the
web
profile
features
as
well,
and
that's
obviously
a
good
example
of
that
would
be
something
that
uses
Jacquard
to
mail
right.
So
you
may
have
like
a
core
profile
app,
but
you
also
want
to
use
the
cart
to
mail,
or
you
also
want
to
use
a
bean
validation
or
something
like
that.
A
But
of
course,
Jakarta
ee
is
pretty
huge,
so
there's
some
other
things
that
are
not
part
of
the
web
profile,
so
there's
good
old
ejb,
which
is
now
I,
guess
Jeb,
and
there
is
Jakarta
authorization
which
is
really
more
of
a
low
level
guy
and
then
a
card
to
batch
and
and
I
noticed.
I
have
Jakarta
mail
here,
twice
my
bad
and
to
card
to
activation
and
character
connectors.
A
So
some
of
these
older
technologies
that
aren't
terribly
popular
these
days.
These
are
part
of
the
the
whole
overall
platform
and
there's
some,
some
of
which
are
optional,
which
were
the
the
apis
for
web
services.
Xml,
binding
and
soap,
attachments
and
I
will
say:
I
have
actually
in
the
last
year,
been
on
a
project
where
we
ended
up
using
some
of
the
old
soap
stuff,
but
nobody
didn't
add
any
new
features
we
just
couldn't
get
rid
of
it.
A
Let
me
put
it
that
way,
so
so
I
have
actually
worked
with
a
lot
of
the
soaps
out
recently.
So
so
this
is
the
entire
Jakarta
e
platform
and
notice.
There's
actually
a
couple
things
missing
here.
So
if
you
saw
a
residence
talk,
you
saw
Jakarta,
no
sequel
and
Jakarta
data
is
coming
up
as
well
as
a
more
of
a
unified
API
for
working
with
data
and
Jakarta
RPC
for
handling
more
protobuf
style
requests.
A
Things
like
that,
it's
kind
of
funny
to
see
something
with
RPC
come
back
to
the
Jakarta
e
world
and
there's
also
other
specifications.
Jakarta
MVC
we've
been
around
for
a
while,
and
it
is
basically
sort
of
a
very
lightweight
web
framework
for
doing
web
web
interfaces
that
don't
require
UI
components
or
anything
like
that
and
Jakarta
management
was
recently
removed.
A
So
as
I'm
sure
all
of
you
know,
who've
been
been
at
this
conference
today.
Jakarta
is
alive
and
well
and
growing,
and
you
know
the
key
thing
for
me
now
is
that
it's
it's
alive
now
right,
it's
sort
of
like
it
was
a
life
support
for
a
while,
and
then
it
was
you
know,
was
breathing,
and
now
it's
like
alive,
so
I
think
what
we're
going
to
see
is
more
Innovation
and
more
standardization.
A
So
I
don't
know
if
anyone
showed
this
earlier,
but
these
are
all
of
the
different
servers
that
are
certified
printer
car
to
EE
and
the
key
thing
you
know
when
I
Was
preparing
for
this
talk,
I
did
I.
Did
this
talk
at
Java,
one
as
well?
I
was
when
I
was
preparing
for
it.
I
was
like
looking
at
this
and
thinking
wow.
A
That
means
that
there's
some
pretty
broad
adoption,
which
is
pretty
nice.
So
these
are
some
of
the
implementations
that
are
out
here
and
a
lot
of
them,
or
some
of
them
are
not
even
not
in
the
US,
which
is
very
nice,
so
I
think
we're
also
seeing
some
headwinds
in
China
as
well,
which
is
a
great
thing.
A
A
So
this
is
what
we
had
before,
like
your
typical
Java
microservice
right,
you're,
drawing
inside
of
a
Docker
container.
It's
using
you
know
some
micro
profile
or
microservice
framework.
It
has.
Your
code
brings
out
of
an
executable
jar
or
native
image
right,
but
let's
just
take
away
that
container
right.
So,
let's
say
we're
not
running
in
Dr
land,
anymore,
okay,
and
let's
just
go
back
in
time
a
bit.
A
Remember
this
Good
Old
Back
to
the
Future
and,
let's
just
say,
we'll,
take
the
same
stuff
and
put
it
inside
of
oh,
your
normal
Java
ee
server.
You
know
pre
microservice
hype
or
post
micro
service
type,
because
you
can
still
run
the
same
stuff,
which
is
one
ingredient,
so
we
have
a
Java
ee
server
and
your
stuff
is
your
code
is
just
inside
the
wire.
A
And
that
server
has
a
whole
bunch
of
apis
right
and
those
in
the
previous
slide.
Those
were
the
generic
versions
right.
These
were
all
the
ones
all
these
specific
ones
that
are
part
of
Java
EE
and
I
left.
The
word
Jakarta
in
here
just
to
keep
things
simple,
but
if
you
go
back,
you
know
far
enough
more
than
five
years
or
you're
using
a
legacy
server.
All
these
are
the
Java
versions.
Right,
the
you
know:
Java
ee,
Bean,
validation
Etc.
A
A
And
then
you
know,
if
you
take
a
step
back
further
well,
your
app
server
may
have
even
more
apis.
You
may
just
not
have
the
web
ones
right,
it
might
have
the
whole
web
profile,
then
all
the
other
apis.
We
talked
about
like
character,
messaging,
all
the
XML
stuff
and,
of
course,
ejb
right,
so
hopefully
I'm
bringing
back
lots
of
memories,
and
you
know
this
is
not
again.
This
is
not
a
bad
way
to
do
things
today,
depending
on
your
your
environment,.
A
I
look
at
the
admin
console
and
I'm
like
so
basically
from
this
admin
console
I
can
manage
a
whole
cluster
of
java.
Ee
servers
and
I
can
check
on
their
health.
I
can
look
at
their
logs,
I
can
deploy
across
many
different
nodes.
I
can
even
organize
them
into
different.
You
know
cells
and
things
like
that,
and
you
know
what
I
the
more
I
look
at
this
I'm
like
gee.
This
sounds
sort
of
like
something
that
we
do
now,
except.
A
So
so
again,
this
is
one
of
those
things
you
know
the
longer
you're
in
the
industry,
the
more
it
goes
back
and
forth
and
arguably,
when
it
goes
back,
it
comes
back
better
but
but
I
I,
just
just
I,
wanted
everyone
to
come
with
me
on
this
thought
experiment
to
go
back
to
what
it
was
like
before
and
sort
of.
Compare
that
to
what
it's
like
now.
Of
course,
the
the
benefit
of
the
container
based
architecture
based
on
oci
is
that
you
know
you
can
put
anything
you
want
inside
container
right.
A
A
A
So
again,
we've
got
the
sort
of
Core
specs
and
then
the
rest
clients
in
other
specs
and
if
you're
not
familiar
Rush
client
is
really
just
about
talking
from
your
your
service
to
other
rest
Services.
So
that's
sort
of
important
even
for
I,
just
notice
that
I
left
out
graphql
out
of
this
part,
even
for
a
micro
profile,
graphql
there's
a
client
side
as
well
so
for
micro
profile.
A
If
you're
interested
one
of
the
good
things
about
a
micro
profile
and
Jakarta
ee
is
that
it's
pretty
easy
to
get
involved,
and
you
know,
look
at
code
file
issues
and
issue.
Trackers
read:
specs
respondent
mailing
lists
all
that
kind
of
fun
stuff.
So
you
do
all
that
kind
of
fun
stuff
at
micro,
profile.io
and
again,
these
are
all
the
different
companies
that
are
involved.
A
There's
a
project
page
on
on
the
eclipse
site
and
I,
encourage
you
just
go
check
out
the
mailing
list
and
and
see
what
see
what's
out
there.
The
other
thing
I
encourage
you
to
do.
Is
you
know
if
there's
a
particular
technology
you're
interested
in
go
ahead
and
read
the
spec
they're
very
readable?
They
all
are
written
and
generated
in
a
beautiful
last
guitar.
So
so
the
specs
are
actually
very
easy
to
read.
A
So
I
encourage
you
to
take
a
look,
and
the
same
goes
for
Jakarta
ee.
Not
all
the
specs
are
quite
as
easy
to
read
because
they're
they're
older
and
some
of
them
are
pretty
big,
but
but
the
newer
ones
are
and
and
again
you
can
get
involved
right,
and
the
key
thing
to
remember
here
is
that
again
it's
it's
alive.
A
There's
a
lot
of
events,
videos
and
stuff
on
the
jakarti
website.
There's
also
a
YouTube
channel.
You
can
check
it
out
and
here's
some
links
for
getting
involved.
I'm
sure
you
guys
have
seen
lots
of
links
today,
I'm
sure
it's
no
surprise,
there's
also
a
contribution
guide
on
the
Jakarta
e
Ambassador
site.
There's
there's
a
card
to
E10
version,
but
there
will
be
a
card
E11
pretty
soon
I
think
it'll
be
out
before
the
end
of
the
year.
So
you
should
check
that
out.
A
A
So
so
you
know,
even
when
you're
building
a
microservice
you're
going
to
be
building
on
some
Foundation
of
code
and
it's
just
important
to
recognize
what
that
code
is
and
where
it
comes
from,
so
that
you
can
help
evolve
and
also
so
that
when
people,
you
know
say
to
you
hey,
this
is
a
Jakarta
restful
web
service.
You
know
what
that
means.
A
Instead
of
saying
this
is
a
so-and-so
web
service
from
this
particular
stack
that
I'm
using
and
I'll
tell
you
this
from
experience
because
I,
you
know
I've
been
on
projects
with
younger
developers
and
are
using
all
this
stuff
and
they
really
have
no
idea.
What
spec
is
what
so
this
this
presentation
is
my
attempt
to
make
some
of
that
little
book
there
so
go
forth,
build
build
the
wonderful
buildings
and
just
make
sure
you
use
some
good
scaffolding
and
you'll
be
good
to
go.