►
From YouTube: Modern Cloud-Native Jakarta EE Frameworks: tips, challenges, and trends | Jakarta Tech Talks | Feb 3
Description
Otavio Santana Presents:
Java has a large number of tools and frameworks to facilitate integration with databases, microservices, and so on. These tools have evolved considerably. It all started with class integrated with XML files and has undergone significant evolution with reflections and annotations within the class definitions. In the cloud-native scenario, requirements have changed and this impacts applications in ways that weren't critical before. For example, cold starts and boot time wasn't critical with application servers but is crucial in serverless and microservices. The objective of this presentation is to talk about how these frameworks behave in the native cloud age and they affect the new world of Jakarta EE: the trade-off of Reflection, Annotation Processing, and Native Image capabilities are some examples, and the tools and frameworks you can choose in for your next application.
Get Social!
Website: jakarta.ee
Subscribe: https://www.youtube.com/user/EclipseFdn
Follow us on Twitter: https://twitter.com/JakartaEE
Like us on Facebook: https://www.facebook.com/JakartaEE/
Join us on LinkedIn: https://www.linkedin.com/groups/13597
Tag us: #JakartaEE
Want more great Eclipse Community webinars? Become a member of our Jakarta Tech Talks Meetup: https://www.meetup.com/jakartatechtalks
A
Hello,
everybody
we
are
live.
Welcome
to
today's
jakarta
tech,
talk
our
speaker
today,
while
I'm
sure
he
needs
absolutely
no
introduction
for
most
of
you
we'll
give
him
one
anyways,
because
he
deserves
it.
He
is
a
senior
java
engineer
focused
on
cloud
and
java
technology.
He
works
on
several
eclipse
foundation
projects
such
as
micro
profile
and
jakarta
ee.
He
is
a
drug
leader,
a
global
speaker
and
a
recognized
oss
contributor,
and
that's
just
a
few
of
his
great
qualifications
and
accomplishments.
A
B
Thank
you
hudson.
This
was
a
nice
introduction,
hello,
everyone
again,
I'm
glad
to
be
here.
Please
if
you
have
any
question
any
comments,
please
let
me
know.
The
whole
idea
is
to
do
conversation
than
a
just
a
talk.
I
usually
don't
like
the
write.
Only
presentation
where
just
speak,
speak,
speak,
speak,
speak
aware:
nobody
you
do.
He
shares
something.
So
please,
if
you
have
anything
to
share,
let
me
know:
okay,.
B
Hello
adele,
hello,
joseph
please
by
the
way,
tell
me
where
you're
from
so
I'm
from
brazil
right
now,
I'm
living
in
portugal,
I'm
living
in
lyria,
that's
a
city
around
lisbon,
I
guess
one
hour
and
a
half
tower
canada,
austria,
nice.
So
today
I
will
cover
about
the
modern
cloud
native,
jakarta
e
frameworks,
tips,
challenge
and
trends.
The
whole
point
here
is
to
show
to
you
how
the
framework
works
right
now
and
the
whole
point
here.
I
understand
it's
a
topic
a
little
bit
advanced.
B
B
Okay,
hello,
juan
hello
tanner?
Thank
you,
introduction,
watson.
My
twitter
handle
is
at
ottawa
java.
Please
follow
me
on
twitter.
I'm
work
platform
message.
Platform
state
is
a
company
who
has
a
goal
to
make
easy
to.
You
move
your
cloud
application
to
the
cloud,
your
application
to
the
cloud
with
simple
way
where
you
as
a
developer,
don't
need
to
care
about
some
details.
However,
those
are
important,
for
example,
backups,
cicd
implementation
platform,
message,
use,
git,
ups
and
so
on.
B
B
If
you
take
a
look
in
the
history,
you
can
split
the
the
the
asian
formation
about
hardware
and
four
of
five
different
movements
or
different
moves
for
so
the
first
one
was
when
we
have
more
people
than
machines.
For
example,
when
we
had
mainframe
and
then
we
move
on
to
the
time
where
we
have.
We
have
one
person
to
one
machine,
the
pc
error
right,
so
one
personal
computer,
one
one
person,
then
we're
leaving
the
multiple
device.
Look
at
me
right
now.
B
Somebody
has
watched
google
watch,
maybe
we
we
are
leaving
the
moving
to
the
multiple
device
where
we
living
with
cloud
environments,
where
it's
so
easy
to
create
your
application.
Move
move
on
to
the
cloud
and
the
service
right
now
we
are
we.
We
can
see
application
that
talks
with
another
application.
That's
amazing,
for
example,
if
you
decide
to
buy
a
ticket,
I
will
receive
an
email
from
that
company.
B
This
may
will
be
read
from
my
gmail,
for
example,
if
you
will
read
the
information
and
then
put
that
information
as
on
a
calendar
event.
Okay,
so
I
just
buy
the
ticket.
I
just
bought
the
ticket
and
then
several
things
happened.
I
made
it
from
provider
the
google
card
event
and
so
on,
and
sometimes
the
google
calendar
give
you
give
us
advice
to
how
the
traffic
is
and
when
you
should
leave
that
place.
B
B
Now,
a
lot
of
people
decided
to
move
on
to
a
micro
service
moment
where
my
application
has
more
than
one
application
more
than
one
database
and
so
on
right
and
we
increase
the
complexity
of
tiers,
because
right
now
we
have
more
instance
and
also
want
to
deliver
is
faster
than
a
pass.
If
you,
if
you
are
old
like
me,
I
have
right
now
one
decade
of
developer
supplement:
okay,
that's
probably
not
old
enough,
but
I
was
able
to
see
a
deploy
by
here
right.
B
Basically,
every
december
we
stopped
the
whole
company
to
deploy
application
the
weekend,
for
example,
a
month
they
we
moved
to
a
monthly
deploy
right.
Every
month
we
have
a
window
of
deploy
where
you
do
it
that
usually
on
saturday
night,
where
nobody
use
that
season,
and
that
is
it
and
then
we
become
crazy
to
to
deploy
a
daily
deploy
so
every
day
at
night,
maybe
every
day
at
morning
we
decide
to
do
that
with
exception
of
friday,
because
friday
is
a
huge
risk
and
then
we
are
doing
deploy
instantly
even
friday.
B
You
work
in
the
company
that
that
had
around
almost
100
deploy
every
single
day.
So
right
now
we
are
looking
to
more
and
more
deploys
to
put
more
features
receive
feedbacks.
The
whole
point
is
we're
looking
for
a
given
methodology
right,
so
we
we
want
to
put
the
product
close
as
possible,
the
software
close
as
possible
for
the
client
so
with
more
release,
more
feedbacks
and
more
bugs,
and
so
on.
B
Okay
right
now
we
understood
about
what's
going
on
the
award
in
the
last
25
years,
but
what's
wrong
with
java
right
now,
because
there
are
huge
complaints
about
okay.
Java
has
an
issue
with
course
art
I
remember
there
is.
There
is
an
article
about
serverless
and
amazon
and
people
usually
don't
recommend
to
do
to
you.
Do
that
and
yes,
java
consumes
a
lot
of
memory,
but
my
question
is:
is
that
really
true?
B
I
mean
look
around
java
has
native
memory,
so
things
like
this
probably
won't
happen.
If
you
decide
to
use
java
instead
of
I
don't
know,
perhaps
node.js
robbie
and
so
on.
Yes
java,
we
will
will
have
a
virtual
trade
soon.
However,
it's
a
work
in
progress,
so
basically
right
now,
if
you
have
amount
of
threads
java,
will
use
this
kind
of
amount
of
threads
that
are
not.
It
is
not
a
big
deal
and
yes,
the
java
shops.
B
So
this
one
here
was
the
java
one
when
spotify
decided
to
leave
python
and
move
to
java-
and
we
have
several
case
like
that,
so
spotify
decided
to
leave
python
to
java
and
jvm
environment
as
well.
Twitter
did
exact
something
as
far
as
I
know,
netflix
is
this
exact
same
move
and
there
is
one
article
from
phobias.
It
said
that
over
60
thousand
people
companies
product
decide
to
do
the
exact
same
move
because
performance,
if
you
said
like
okay
job,
is
not
fast
enough
in
consumer
memory.
B
Perhaps
there
is
an
issue
in
our
application
right,
so
let's
go
deep
in
your
application,
so,
for
example,
here,
as
you
can
see,
the
number
of
code
of
our
application
generate
usually
is
just
20
of
my
whole
application
than
half
of
my
application
usually
comes
from
frameworks,
so
whatever
you
decide
to
use
spring
micro
profile
micro
nodes
held
on
whatever
just
a
small
piece
of
your
code
in
java,
usually
is
your
code
self?
Anything
else
is
frameworks,
library,
etc,
etc.
B
But
why
do
we
need
frameworks?
Frameworks
makes
our
life
easier
in
the
java
world.
It
reduces
the
bullet
plate
and
frameworks
are
in
general
to
do
mappers.
For
example,
I
have
my
java
class
and
lightroom
upper
to
my
object
to
my
database,
where
I
I
will
have
my
or
rm
object,
relational
mapping.
Mapping
I
can
do
design
something
with
http
right.
Jax
rs
is
basically,
I
put
several
notation,
for
example,
get
annotation
post
annotation
to
don't
do
that
manually
with
that
annotation
it
will
be
converted
to
http
http,
get
verb
and
so
on.
B
So
basically
you're
looking
to
framework
to
make
your
life
easier
and
to
reduce
the
code
place
and
make
us
more
effective
and
faster
than
if
you
don't
decide
to
write
anything
on
our
home
okay
in
the
past.
If
you
are
old
enough,
our
our
metadata
was
like
this,
where
I
have
my
class,
my
java
class
in
one
hand,
and
on
the
other
hand
I
have
my
xml
file,
where
I
need
to
do
this
kind
of
mapping
based
on
this
file.
B
So
I
have
my
class
card
where
I
have
my
id
name
and
age,
and
I
have
my
xml
file
where
I
have
my
table:
name,
column,
name
and
so
on.
The
whole
point
is
java.
Class
is
cameo
case
where
database
is
usually
is
an
ak.
So
I
can
do
this
kind
of
mapping
mapping
process
where
I
can
put,
for
example,
name
in
capital
in
my
class
and
follow
the
good
process
of
java.
B
And
based
on
these
two
files,
we
can
run
reflection.
The
whole
point
of
reflection
is
to
give
us
a
dynamic
error
in
the
java
world.
So
that's
a
brief,
brief
conception
of
reflection.
So
it's
a
dynamic
way
to
to
look
your
coach.
Basically,
with
reflection,
we
will
take
a
look
in
your
code
in
your
java
source
over
on
time
and
it's
not
just
java
who
has
this
kind
of
feature
so
c,
plus
plus,
I
guess,
go
and
so
on.
B
You
can
call
whatever
you
want,
but
the
whole
point
here
is
instead
of
use
two
files
right
now
we
we
use
just
one
file
with
several
metadata
facilities
that
will
make
our
life
easier
than
the
past.
So,
instead
of
have
two
places
to
change
your
code,
you
just
need
one
place,
and
this
kind
of
thing
feature
that
we
are
using
right
now,
for
example,
so
I'm
using
annotation.
B
B
B
I'm
not
saying
that's
right
and
I'm
not
saying
that's
wrong.
The
whole
point
is,
if
you
want
to
you,
can
do
that
with
reflection.
Okay.
So,
basically,
in
this
your
design
code,
for
example,
if
you
have
an
id
without
increment,
you
don't
need
to
have
the
the
setter
methods
so
basically
just
have
the
cat,
because,
with
reflection
you
can
broke
this
encapsulation
on
real
time
to
set
an
instance
value.
Okay,.
B
B
Okay,
you
don't
need
a
question.
Do
you
think
with
reflection?
We
have
code
more
expressive.
I
think
so.
You
can
explore
more
encapsulation,
for
example,
this
sample
here
right.
So
instead
of
have
the
setter,
I
can
just
put
the
field
there
as
private
and
don't
need
to
worry
about
put
the
setter
owns.
B
B
But
yes,
it's
just
my
opinion.
The
first
point,
the
issue
of
reflection.
We
have
a
couple
issues.
The
first
one
is,
you
will
read
the
whole
metadata
information
on
real
time
right.
So
take
a
look
here,
for
example,
when
I
start
the
application,
I
will
read:
the
class
cut,
take
the
empty
annotation
and
find
to
the
constructor
of
looking
for
the
fields
and
so
on.
B
The
second
point
is
the
beauty
of
java
is
because
everything
is
open
source
in
the
java
length
class.
We
have
the
inner
class
called
reflection
data
right,
where
every
time
that
you
read
any
information
from
reflection,
it
will
load
the
whole
reflection
data
in
this
case,
if
you,
if
you
want
to
just
get
the
field
of
the
name
of
the
class,
it
will
load
everything
about
this
class,
so
it
if
that
extends
some
class.
B
If
you
don't
remember
about
governor
collectors,
don't
worry.
Those
are
the
stage
of
half
prince
and
the
jvm
right
now
so
I'll
have
phantom
onto
strong
software
reference.
You
take
longer
to
be
released
on
the
memory,
so,
for
example,
if
you
have
like
10
class,
it
will
load
the
whole
information
from
reflection
data.
B
And
sometimes
when
you
have
you,
you
have
the
stop
the
word.
If
you
release
from
memory,
so
it
will
take
longer
to
return
this
kind
of
memory
and
take,
for
example,
the
framework.
So
each
framework
has
one
goal
right.
So
take
a
look
in
cdi.
The
goal
is
to
dependence
injection
jax
rs.
The
goal
is
to
att
http
verbs
and
annotation
parameters,
and
so
on.
Jpa
for
sure
is
take
the
information
and
mapping
to
you.
You
work
with
sql
technology,
no
secret
to
work
with
no
sick
technology,
and
so
on.
B
The
whole
point
is
each
framework
will
read
each
specific
class,
therefore,
a
bunch
of
reflection
data,
and
it
will
you
have
your
home
framework
metadata
in
memory,
so
it
will
be
your
consumes
a
lot
of
memory
it
to
you
process
a
lot
of
stuff,
so
it
will
take
longer
to
be
your
application,
be
ready,
for
example,
if
you
decide
to
use
microprofile,
just
a
version,
one
dot
o
it.
We
need
to
read
cdi
to
read
the
whole
class.
B
B
Another
point
we
are
talking
about
reflection
and
it's
hard
to
use
did
dirt
in
time
compiler.
So
reflection
is
one
way
amazing
to
use
as
you
on
set.
It
might
be
put
your
code
more
expressive.
That's
true,
however,
you're
not
able
to
take
a
huge
advantage
of
it.
One
option
that
you
can
use
if
you
want
to
that.
A
lot
of
framework
decided
to
go
to
this
way
is
basically,
you
can
do
a
hybrid
solution.
B
B
However,
the
start
type
becomes
even
worse
because
you
need
to
take
the
class
you
need
to
compile
the
class
think
about
it.
Need
to
click,
create
a
class,
it's
a
a
huge
bunch
of
strings
in
each
compiled
class.
So
it's
a
consumer
memory
until
you
get
get
ready
to
start
the
application
and
the
whole
point
is
okay.
You
can
design
the
application
this
way,
mostly
when
you
just
should
deploy
also
the
month
or
perhaps
also
the
day.
B
B
Okay,
when
it's
ready
to
be
faster,
however,
choose
ready,
it's
a
nightmare
and
with
the
micro
service
moment
it's
become
a
nightmare
to
us
right,
so
we
need
to
have
a
cold
start
and
need
to
have
it
right
now,
just
you
do
a
comparison
about
several
solutions.
As
you
can
see,
this
article
comes
from
girlfriend.
Man
is
meat
and
he
wrote
in
this
one
about
java
reflection
but
faster
and,
as
you
can
see
here,
we
have
a
couple
of
solutions,
so
the
direct
access.
B
B
If
you
compare,
however,
the
startup
time,
the
bootstrap
is
a
nightmare.
So
take
a
look
here.
The
refraction
and
the
method
handle
the
point.
The
points
and
the
java
compiler
is
a
huge
nightmare.
So
right
now
we
are
leaving
the
trade-off.
So
if
you
decide
to
go
to
java
compiler,
we
need
to
forget
about
tag,
because
when
application
ready,
it
will
be
almost
a
java
native
code.
B
B
B
B
This
kind
of
thing
won't
happen
because
you
need
to
you
need
to
have
your
getter
setter
or
perhaps
you
you
need
to
have
any
kind
of
public
id
or
something
like
that.
The
whole
thing,
the
whole
point
is
with
you
having
we
see
facing
the
trade-off
about
framework
architectures.
Okay,
so
you
need
to
choose
which
one
each
one
you
gonna
leave.
B
Also,
you
don't
need
to
use
the
reflection
data
anymore.
If
you
consume
less
memory,
however,
they
wish
you
the
issue
gonna
be
within
your
encapsulation.
If
you
have
one
way
to
do
that,
I
don't
know,
for
example,
public
getter,
setter
or
visible
by
package,
something
like
that,
but
you're
not
able
to
do
that.
B
It's
kind
of
solution,
where
I
put
it
just
a
private
and
my
framework-
will
write
that
anymore
anyway,
and
also
the
programability,
because
we
are
a
devil
developer,
use
a
lot
of
plug-in
play
frameworks
like
because
of
the
spi,
usually
with
java
notation
processor.
This
kind
of
dependence
must
be
there
on
the
compilation
time,
therefore,
any
kind
of
library
by
runtime
you're
not
able
to
use
at
least
with
that
approach.
B
B
And
yes,
another
point
is:
if
you
use,
I
have
time
compilation.
If
you
know
about
crawl
vm,
you
can
take
advantage
of
native
image,
so
you
can
use
this
kind
of
approach
with
servlets,
for
example.
However,
it
has
an
issue,
remember
that,
so,
if,
when
you
run
a
native
image,
there
is
no
jvm
governor
collector
anymore,
there
is
not
just
in
time
improvement
in
the
jvm
anymore.
B
Basically,
yes,
it
will
guarantee
to
you
an
amazing
start
time,
startup
time,
amazing,
bootstrap
time.
However,
they
wish
you
the
issue
gonna
be
about
if
you
have
application
longer
than
you
expected.
For
example,
if
you
decide
to
do
a
deploy
every
week,
if
you
decide
to
compare
one
application
native
in
application
run
and
jvm
with
the
time
the
application
jvm
will
be
better
and
better
and
better.
Okay,
thanks
to
the
just
in
time,
compiler.
B
Besides
that,
if
you're
using
java
8,
so
please
leave
as
soon
as
possible
to
at
least
java
11,
because
there
are
several
optimization
to
garbage
collectors,
several
improvements
on
containers.
So,
yes,
I
did
not
say
docker,
I
said
containers,
so
if
you
start
to
use
any
kind
of
containers
from
java
11,
we
you
you,
you
have
several
features.
B
B
Where,
again
I
use
reflection
to
read
this
kind
of
information
and
compile
with
or
on
runtime
java,
notation
process,
processor
or
any
kind
of
solution
that
allows
you
to
generate
this
kind
of
metadata
on
compilation,
time
and
native
solution.
Where
you
take
your
application
outside
the
jvm
will
run
natively,
okay
and
it
has
several
flavors
right.
So
reflection,
you
guarantee
you
a
server
plugability,
for
example.
B
B
The
income
cap,
the
encapsulation,
is
guaranteed.
If
you
do
a
good
design
for
sure,
for
example,
don't
need
to
usually
don't
need
to
handle
about
the
private
get
reset
anymore.
If
you
don't
want
to
the
java
compiler.
Yes,
the
probability
is
not
so
good.
Yes,
you
can
combine
if
you
want,
so
you
can
use
java
complete
and
sorry.
You
can
use
the
higher
solution,
so
you
can
use
several
plugin
plays
runtime
or
whatever
you
want.
However,
as
I
mentioned
before,
this
hybrid
solution
is
a
nightmare
on
the
bootstrap.
B
However,
once
warm
it's
amazing,
because
we
you
take
the
advantage
of
cheat
and
encapsulation
is
a
warning.
So,
yes,
you
can
still
use
encapsulation
in
java,
but
you
need
to
remember
that
it
will
be
accessed
by
the
frame
itself,
so
the
java
notation
process,
processor
or
any
kind
of
solution
where
you
need
to
take
this
metadata
before
one
time
on
compilation
time,
for
example,
the
probability
usually
don't
happen
because
you
you
need
to
install
everything
on
the
compilation
time.
B
B
It
will
take
advantage
of
just
in
time
compilation
as
well
and
encapsulation
issue
warning
a
native.
You
don't
have
the
probability
for
sure
the
core
start
is
usually
usually
amazing.
I
saw
a
lot
of
solutions
that
use
native
to
serverless,
where
I
run
application
then
cube
application
for
sure.
If
you
decide
to
do
this
kind
of
approach,
you
don't
need,
for
example,.
B
Coverage
collector
or
don't
need
teach
because
we
run
us
in
the
enquiry
application.
So
usually
I
just
saw
native
as
a
good
solution
to
serverless,
okay
and
encapsulation.
Yes,
you
should
can
do
encapsulation.
However,
you
need
to
remember
that
sometimes
you
use
the
get
and
set
method.
For
example,
it's
not
kind
of
magic
that
usually
happen
with
reflection,
because
you
can
broke
the
whole
contract.
B
Okay,
when
we
we
talk
about
the
java
framework
architecture
for
sure
the
future
is
uncertain,
but
everybody's
looking
to
the
containers,
the
modules
is
something
that
happened
right
now.
We
have
a
lot
of
modularization.
We
had
discussion
a
lot
of
modularization
on
jakarta,
ee
and
also
microprofile
for
sure
I
put
java
notation
process.
B
There
is
an
amazing
article
from
izi
from
payara
who
wrote
some
myth
about
okay
about
reflection
and
ahead
of
time.
Compiler,
okay
and
remember,
the
performance
is
something
that
you
need
to
handle,
because
there
is
a
huge
complexity.
When
you
talk
about
performance
right
now,
you
can
see
this
picture
here
right
in
the
java
world.
You
we
usually
at
least
right
now.
B
B
B
Probably
the
plane
whoa,
I
don't
think
so
so,
just
to
curiosity
with
just
one
mile,
the
motorcycle,
yes
exactly
the
bike,
they
buy
it
exactly.
The
bike
was
a
winner,
but
it
does
not.
It
does
not
mean
that
we
will
cross
the
ocean
with
the
bike
just
because
it
was
one
mile
faster
than
the
plane
right.
So
we
need
to
take
a
look
about
that.
So
performance
is
not
just
about.
B
B
B
It
is
a
simple
sample
here.
Okay,
thank
you.
The
whole
point
is,
I
have
my
class
okay.
I
have
my
class
and
I
will
convert
this
class
to
a
map,
a
java,
youtube
youtube
map
and
then
go
back
to
that
kind
of
class.
Okay.
Basically
it's
a
simple
framework
where
I
have
my
god
entity
or
whatever
entity.
I
I
will
convert
this
one
to
to
a
map
and
then
from
app
I
will
create,
but
that's
kind
of
empty.
Okay,
that's!
That
is
my
api
and,
as
you
can
see,
I
have
four.
B
No
sorry.
I
have
three
approach
to
the
exactly
implementation
so
think
about.
I
have
a
refre.
We
have
a
framework
to
this
kind
of
mapper
and
my
first
option,
for
example,
is
reflection
right.
So
I
have
my
mapper
here
where
I
have
my
reflection.
Mapper
that
implements
this
solution,
as
you
can
see
here
for
sure.
That's
a
so
simple
way
to
use
reflection,
so
ignore
that
I
know
you
can
do
better,
but
I
have
my
type
I
check.
B
If
this
this
information
are
new,
I
will
take
a
look
in
the
constructor
to
create
my
instance,
and
then
I
will
I
will
write
by
the
field.
As
you
can
see
here,
I
look
to
the
id
annotation
and
then
a
column,
annotation
and
then
do
the
right
operation.
So,
okay,
so
if
this
guy
is
not
an
id,
I
take
a
look
at
column
and
I
can
see
here
I
make
the
accessible
true.
So
I
don't
care
about
this
class.
B
B
The
second
one
is
a
harvard
hybrid
solution,
where
I
okay,
where
are
you
where
I
read
the
information
real
time
and
then
compile
my
codes
or
real
time
to
do
any
kind
of
operation,
as
I
mentioned
before
it
will
take
longer.
However,
when
it's
ready
it
will
be
faster
than
reflection.
So,
as
you
can
see,
I
have
more
class.
B
So
I
have
my
compile
mapper
here.
Where
are
you
take
a
look,
sorry,
the
annotation
and
then
create
this
class?
You
compile
the
class
you
instead
of
use
reflection
to
access
class,
I
will
use
runtime
compile
class
and
the
last
one
is
with
my
processor
right.
So,
as
I
mentioned
before,
I
have
my
mapper
here,
my
processor,
where,
on
the
compilation
time,
I
will
take
a
look
in
the
whole
information.
I
will
read
the
whole
metadata
and
then
do
this
kind
of
sample
here.
B
So
again
I
have
my
api
where
it
will
convert
two
from
map.
I
have
my
common
annotation.
I
have
three
solution:
the
compiler,
the
hybrid
solution,
reflection
that
where
I
will
use
information
real
time
and
the
processor
that
is
java,
notation,
processor
time
where
I
are
you
process
this
information
real
time
where
I
don't
need
to
read
that
anymore.
The
information
is
warm.
The
information
is
there
okay
to
show
to
you.
I
have
three
class.
I
have
my
animal
that
has
an
annotation
here,
my
car
and
the
person.
B
Okay,
my
pc
dependency
here
have
the
reflection,
because
I
need
to
run
this
guy
on
real
time.
Remember
that
compile
as
well.
I
need
to
run
on
real
time.
However,
my
java
notation
process-
I
don't
need
to
have
that
in
real
time,
basically,
because
it
will
be
required
only
on
the
compilation
time.
Okay,.
B
B
For
example,
here
I
have
my
animal
where
it
has
several
fields.
Okay,
as
you
can
see
here,
I'm
not
reading
this
guy
a
real
time,
so
I
put
kind
why?
Why
do
I
have
this
kind?
Because
this
belongs
to
the
notation
here
right,
so
it
you
read
the
notation
and
put
that
on
compilation
time:
okay,
increase
the
zoom
okay
one
moment
I
will.
B
B
B
B
B
B
B
B
B
B
The
trade-off
between
these
chose
the
hybrid
solution,
where
you
can
use
reflection
and
then
compile
your
class
all
your
time.
So
the
whole
point
is
to
just
see
this
kind
of
discussion
is
huge
and,
basically
that's
why
I'm
looking
to
okay
have
cdi
cdi
light.
Okay,
if
that,
if
there
is
any
question,
please
let
me
know,
if
not
thank
you
that
was
hopefully
we
enjoyed
this
presentation.
A
Yeah,
thank
you,
otavio.
That
was
great,
we'll
leave.
We
have
a
few
minutes
left
here
so
as
we're
wrapping
up,
if
anybody
has
any
questions,
feel
free
to
ask
them
still
in
the
chat
I
mean
we
can
still
answer
them,
but
I'll
just
give
a
couple
of
quick
information
to
the
audience
here.
What
we
have
coming
up
so
the
next
jakarta
tech
talk
happens
on
february
17th,
and
that
is
jakarta.
A
A
A
A
Finally,
we
always
appreciate
any
feedback.
So
if
you
want
to
click
on
the
green
button-
and
let
us
know
how
you
enjoyed
the
presentation
today,
that
would
be
awesome.
I
haven't
seen
any
more
questions,
so
if
anybody
has
a
question,
feel
free
to
ask
it,
but
otherwise
thank
you
very
much
otavio
for
presenting
us
to
us
today
and
everybody
else
enjoy
the
rest
of
your.