►
From YouTube: Why Jakarta EE Developers are First Class Citizens on Azure | Jakarta Tech Talks Reza Rahman
Description
Reza Rahman presents a comprehensive overview of what Jakarta EE on Azure really means. He will cover what is possible today and what the current roadmap is. This includes supporting WebLogic, WebSphere/Open Liberty, JBoss EAP, WildFly, and Payara on virtual machines, Kubernetes, or PaaS.
Get Social!
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
If
you
have
any
questions,
please
feel
free
to
drop
them
in
the
chat
section
on
in
the
bar
on
the
right
hand,
side
of
your
screen
and,
at
this
point
I'll
turn
it
over,
take
it
away.
Okay.
So,
first
of
all,
thank
you
for
having
me
and
thank
you
folks
for
tuning
in
to
this
talk.
Obviously
this
is
near
and
dear
to
my
heart.
This
is
essentially
what
I
do
at
microsoft
in
my
day,
job
as
principal
program
manager.
A
So
basically,
this
talk
is
about
all
of
the
work
that
we're
doing
in
terms
of
what
is
possible
for
jakarta,
your
job
ie
developers
on
azure
today,
and
what
is
it
that
we
are
working
on
primarily
through
our
partnerships
in
the
in
the
java,
ee
or
jakarta
ecosystem,
and
the
one
thing
that
I
wanted
to
point
out
is:
there's
no
reason
to
hold
questions
until
very,
very
late.
I
think
we're
we'll
be
fine
in
terms
of
our
time.
A
So
if
you
have
questions,
please
post
them
throughout
just
so,
we
have
more
of
a
dialogue
going
as
opposed
to
simply
me
doing
a
lecture
so
feel
free
to
to
do
that,
and
it's
really
not
an
issue.
If
you
have
any
questions
later
on,
if
you
want
to
get
in
touch
with
me
later
on,
I
will
post
the
location
of
the
slides,
it's
actually
on
speaker
deck
right
now.
If
you
look
at
my
speaker
account,
this
slide
is
already
posted.
A
My
email
address
is
there
absolutely
feel
free
to
drop
me
an
email
whenever
okay,
so
this
is
my
plan
for
the
next
50
or
60
minutes
or
so
I'll,
be
talking
to
to
you
a
little
bit
about
the
jakarta
ecosystem
context.
Hopefully,
most
of
us
are
already
aware
of
this.
I
won't
be
spending
a
tremendous
amount
of
time,
but
mostly
this
is
to
relay
what
we
are
looking
at
from
a
microsoft
standpoint
in
into
the
jakarta
ecosystem
and,
basically,
our
understanding
of
where,
where
are
we
operating?
What
is
what
is
the?
A
What
is
the
context
in
which
we
do?
We
are
doing
all
of
this
work,
then
I'll
be
spending
a
good
deal
of
time
talking
to
you
about
what
are
the
current
capabilities
and
what
is
the
work
that
we
are
doing
right
now?
What
is
it?
What
is
the
kind
of
things
that
you
can
take
advantage
of
right
now
and,
of
course,
what
are
we
doing
in
the
future?
A
So
what
have
we
not
done
yet
that
is
already
on
our
program
now
before
we
do
that,
it's
fair
to
acknowledge
that
typically
azure
has
not
been.
You
know
your
your
prime
destination
for
jakarta
developers
for
some
number
of
years,
but
I
think,
while
saying
that
you
also
have
to
turn
around
and
say
that
we
are
now
more
than
catching
up
right.
A
So,
in
fact,
if
you
really
look
take
a
look
at
our
objective,
look
at
what
we
are
doing,
we're
probably
doing
more
for
the
jakarta
ecosystem
on
the
cloud
than
most
of
the
other
cloud
vendors
right.
So
while
we're
not
directly
contributing
to
the
jakarta
specifications,
we
are
indirectly
contributing
by
making
azure
a
really
good
place
to
run
these
sorts
of
workloads
and
also
working
with
our
partnerships
to
make
sure
that
all
of
those
all
of
the
good
work
that
ibm
is
doing
and
red
hat
is
doing
and
oracle
is
doing.
A
A
A
Their
application
is
important
to
them
from
a
business
standpoint,
but
in
reality
this
continues
to
be
a
very
important
technology
industry-wide
as
well,
when
you
take
a
when
you
take
a
more
global
approach
and
take
a
look
at
a
global
perspective
on
things
so
still
about
25
to
35
percent
of
existing
and
new
applications
out.
There
are
running
on
some
kind
of
jakarta
application
server
or
the
other,
whether
that's
weblogic,
websphere,
jboss,
eap,
wildfly
pyara.
So
that's
a
pretty
significant
footprint.
A
When
you
look
at
millions
of
java
developers
out
there,
that's
a
good
chunk
of
people
are
really
directly
dependent
on
on
this
technology
platform.
Now,
even
if
you
discount
that
right.
So
when
you
look
at
these
industry
surveys
and
even
in
our
own
customer
base
in
azure,
the
reality
is
the
vast
majority
of
java
developers
are
in
one
shape
or
form
or
the
other
dependent
on
this
technology
set
right
so
they're,
using
at
least
one
or
more
of
these
apis
in
their
application.
A
Somehow
right
so
whether
it's
using
tomcat
or
jetty
or
hibernate,
or
activemq,
or
jersey
or
cxf,
what
have
you
there's
so
many
different
ways
in
which
jakarta
e
touches
java
developers?
It's
really
quite
astounding,
it's
it's
probably
other
than
java
sc.
It's
probably
the
second
most
important
technology
in
the
in
the
ecosystem,
in
terms
of
the
impact
that
it
has
and
a
lot
of
these
applications
are
moving
to
the
cloud
not
all
of
them.
It
seems
to
be
a
little
bit
behind
the
curve
in
terms
of
jakarta,
developer
or
developers.
A
If
you
look
at
java
developers
as
a
whole,
slightly
less
of
that
percentage
is
is
on
the
cloud
in
terms
of
jakarta
developers,
but
that
is
also
changing.
We've
seen
seen
that
in
the
surveys,
people
certainly
have
the
trend
of
moving
to
the
cloud
as
well,
and
these
are
the
fundamental
reasons
why,
from
an
azure
standpoint,
it
is
very,
very
important
to
address
this
market
properly
a
little
bit
of
a
survey
reference
here
this.
This
is
a
2020,
jakarta
developer
survey.
A
But
in
terms
of
pure
jakarta
e,
this
is
probably
an
over
representation
a
little
bit,
probably
because
of
selection
bias.
But
over
here
we
were
talking
about
35,
so
in
that
range
of
people
that
are
using
jakarta
e
application
servers
of
some
kind
that
are
reporting
back.
Yes,
even
in
cloud
native
applications
they're
using
about
a
third
roughly,
a
third
of
people
are
using
that
technology
set.
One
interesting
data
point
that
I
really
find
intriguing
and
something
we
are
tracking
actively
is
the
interest,
certainly
in
focus
and
micro
profile.
A
So
we
do
have
some
support
for
that.
In
azure,
we
are
probably
going
to
beef
up
that
support
a
little
bit
going
forward,
as
we
see
greater
interest,
especially
in
our
in
our
own
customer
base,
direct
interest
in
technologies
like
workers
and
and
the
micro
profile
suite.
Now,
of
course,
as
we
all
know,
microphone
and
chakra,
they
are
not
mutually
exclusive.
The
jakarta
e
run
times
runtimes
pretty
much
all
of
them.
A
Support
microprofile
as
well
so
interested
in
microprofile
does
not
necessarily
mean
a
fundamental
shift
for
us
strategy
wise
quite
yet,
because,
ultimately,
it's
going
to
be
the
same
sort
of
runtimes
like
open
liberty
or
or
pyara
or
wildfly,
that
are
supporting
both
technologies
in
the
end.
But
there
are
exceptions
like
quercus,
for
example,
okay,
so
I
think
again
we're
all
reasonably
aware
of
what
is
going
on
in
terms
of
the
transition
and
why
this
is
jakarta,
we're
referring
to
jakarta
developers,
as
was
the
java
e
developers.
A
I
think
jakarta.
Eight
was
a
reasonably
successful
release.
We've
not
seen
a
tremendous
amount
of
uptake
yet
in
terms
of
azure
usage,
but
I
think
out
in
the
wild.
A
decent
number
of
folks
again,
referring
back
to
the
to
the
survey,
have
in
fact
begin
to
adopt
jakarta
e8.
Hopefully
that
trend
continues
with
jakarta
39,
so
we're
just
a
few
weeks
out
out
of
the
jakarta
e9
release.
A
Hopefully
that
will
be
out
soon
and,
as
you
know,
the
primary
objective
there
is
to
decouple
from
sort
of
the
oracle
ip
realm
of
influence
syndrome
in
including
copyright
right
this.
So
this
this
truly
decouples
the
technology
away
from
the
jcp
legacy
and
sort
of
single
vendor
legacy
into
something
a
lot
more
open
standard,
but
it
will
require
the
ecosystem
to
essentially
adapt
to
this
new
name.
Space
change
and,
of
course,
there's
also
jakarta,
is
beyond
whatever
is
beyond
jakarta.
A
A
So
this
is
an
important
little
little
analysis
actually
to
point
out
as
well,
if
you
haven't
seen
it
before.
So
this
is
the
good
folk
side
at
infoq
they
put
out
a
java
and
jvm
analysis
every
year
you
can,
you
can
take
a
look
at
it,
there's
a
short
link
to
that
in
the
slide
deck.
But,
as
you
can
see
here,
it's
in
good
shape,
so
it
used
to
be
the
jakarta
e
and
microprofile
used
to
be
in
the
innovators
box.
So
it's
progressing
reasonably
well.
A
Obviously,
between
the
java
e
and
jakarta
transition,
there's
been
sort
of
a
stagnant
period,
so
the
the
more
we
move
away
from
the
stagnant
period,
the
better
it's
going
to
be
and
the
more
more
reason,
all
the
more
reason
for
microsoft
and
azure
to
take
these
technologies
even
more
seriously
and
essentially
begin
to
invest
in
them.
Even
more
so,
let's
talk
about
the
current
state,
so
I'll
talk
about
the
current
state
in
terms
of
a
map.
A
If
you
will
so,
I
actually
think
about
the
work
we're
doing
at
microsoft
in
terms
of
this
map
as
well.
So
there's
various
different
pathways.
When
you're
talking
about
the
cloud
that
people
can
move
into
the
cloud,
it's
not
just
a
single
short
deal.
It's
a
the
cloud
at
the
end
of
the
day
is
all
about
flexibility
and
all
about
options.
So
there
are
options
for
java
developers
to
be
moving
into
azure
as
well.
The
classical
one
is
virtual
machines.
A
So
in
virtual
machines
we
want
to
support
all
of
the
major
platform
all
of
the
major
platforms,
jakarta,
runtimes,
weblogic
webster,
traditional
wildfly
in
containers
and
openshift,
or
rather
kubernetes
and
openshift.
Again,
we
want
to
want
to
support
all
the
modern,
more
modern
runtimes
here
as
well,
including
jboss,
wildfly,
weblogic
server,
payara,
webster
liberty,
wester,
open
liberty,
as
opposed
to
russia,
traditional
and
in
terms
of
past
services.
A
A
That
actually
is
previous
to
has
a
public
review
of
jakarta,
messaging
or
jms
support
within
within
that
service.
We
also
have
redis
redis
surprisingly
popular
amongst
java
developers
and
in
fact,
amongst
java
ee
developers
as
well.
We
find
that
both
in
terms
of
our
customer
engagement,
as
well
as
our
surveys
and
there's
different
ways
of
using
gravis,
so
you
can
use
redis
as
a
hibernate
or
jpa
second
level
cache.
A
A
So
before
I
move
forward,
there's
one
specific
call
out
that
I
that
I
want
to
do
as
you'll
see
in
a
moment.
You
know
where
we
are
in
this
map
is
in
various
different
places.
We
have
various
bits
of
various
bits
of
progress
being
made.
Some
are
pretty
near
complete.
Some
are
still
being
completed,
but
one
vendor
actually
really
stands
out
in
terms
of
the
way
they
support
azure,
where
we
really
haven't
needed
to
do
anything
with
them.
A
So
the
pyrofolks
have
a
number
of
guides
in
order
to
how
to
effectively
run
pyra
as
a
runtime
on
azure.
Really
really,
as
I
said,
didn't
didn't
need
to
do
much
of
anything
with
them
in
terms
of
the
work
that
we
are
doing
with
some
of
the
other
vendors.
So,
for
that
reason
we
won't
be
covering
payara
too
much
going
forward.
A
So
this
is
really
running
these
virtual
machines
in
their
raw
form
on
azure,
as
opposed
to
as
opposed
to
on
your
own
data
center,
is
the
easiest
pathway,
especially
for
lifted
shift
type
of
workloads.
Virtual
machines
are
very
easy,
they're,
very
familiar
in
in
terms
of
their
technology.
Certain
capabilities
to
what
you
may
have
in
your
on-premise
data
center
today,
and
really
the
virtual
machines
are
the
linchpin
of
supporting
jakarta
on
azure
and
even
more
broadly
speaking,
job
on
error.
A
A
Now,
when
you
talk
about
jvmb
solutions
on
azure,
there's
a
couple
of
different
flavors,
so
one
is
what's
called
these
base
virtual
images.
So
that's
is
this
really
nothing
much
more
than
sort
of
that,
let's
say
wildfly
or
jboss,
ap
or
or
linux,
nothing
much
more
than
the
operating
system,
a
basic
working
instance
of
that
stack,
including
the
operating
system,
the
jvm
and
the
application
server.
A
Now
we
do
have
those
base
images
as
well,
we'll
talk
about
that
in
a
second,
but
in
addition
to
that,
another
capability
that
azure
has
that
is
not
very
well
understood,
is
the
concept
of
solution
templates,
and
what
that
is.
Is
that
it's
another
layer
of
abstraction,
that's
not
quite
taz,
but
what
it
allows
you
to
do
is
basically
take
these
base
images
and
do
something
useful
with
them.
So
in
other
words,
create
a
single
working
instance
or
create
a
cluster,
including
load
balancing
integrate
with
measure
various
azure
services.
A
A
A
So
we
have
a
number
of
web
logic
versions,
supported
in
in
in
a
predictable
way,
with
oracle,
linux,
oracle,
jdk
and
weblogic,
but
above
and
beyond
that,
we've
also
invested
in
creating
these
solution
templates
as
well.
So
this
is,
if
you
look
in
into
the
azure
marketplace,
and
you
look
for
weblogic
you'll,
see
all
of
these
solution
tablets
and
base
images,
they're
all
published,
maintained
and
supported
jointly
by
both
microsoft
and
oracle.
A
Now,
other
than
that,
we
are
also
supporting
integrations
out
of
the
box,
so
you'll
see
in
the
in
the
screenshot.
We
have
different
blades,
representing
the
different
integrations
that
we
support.
So
we,
inter
we
support
easy
integration
with
various
databases
so
on
azure,
namely
azure,
post,
azure,
sql,
azure,
azure,
postgresql
and
oracle
db,
either
running
on
virtual
machines
or
even
potentially
running
on
the
oracle
cloud
right.
A
So
if
you
have
a
database
running
on
the
oracle
cloud,
you
can
interconnect
you
can
use,
you
can
use
azure
interconnect
to
basically
again
have
it
as
though
it
is
a
single
data
center.
So
it's
a
very
fast
secure
connection
between
oci
and
and
azure,
and
we
also
have
built-in
integration
with
azure
active
directory.
A
So
the
major
release
for
this
is
is
already
out
we're
essentially
supporting,
as
I
said,
some
other
key
integrations
and
key
use
cases.
We
will
have
more
more
releases.
In
particular,
we
want
to
also
support
elastic
as
a
distributed
logging
solution,
as
well
as
support
coherence.
So
currently
we
do
not
have
built-in
support
for
coherence
and
in
the
solution
template.
So
you
you
have
to.
A
If
you
want
a
coherence
cluster
on
top
of
your
web
watch
cluster,
you
need
to
create
that
yourself,
but
we're
also
thinking
of
baking
that
into
the
solution
template
as
well.
So
we
also
have
similar
support
and
you
can
use
use
basically
the
solution
templates
for
for
container
based
solutions
as
well.
In
the
same
way,
you
know
in
order
to
ease
migration
into
into
the
container
world.
So
that's
what
we're
looking
to
do
right
at
this
moment
as
well,
is
also
support
weblogic
on
the
azure
kubernetes
service.
A
In
the
same
way,
so
for
all
of
these
things,
we
need
feedback
engagement.
We
need
people
to
try
these
things
out.
You
know
if
they're
doing
migrations
we'd
like
to
work
hand-in-hand
with
them
in
terms
of
those
migrations
and
figure
out
what
it,
what
exactly?
How
exactly
could
we
better
support
them?
How
good
are
the
solutions
that
we
are
developing,
how
useful
they
are?
A
So
containers
obviously,
are
all
the
rights.
So
in
fact
you
know,
virtual
machines
are
still
tremendously
popular.
It's
probably
the
most
popular
way
of
moving
to
the
cloud
still
believe
it
or
not,
but
containers
are
catching
up
very,
very
quickly
right.
So
there's
tremendous
amount
of
interest
around
things
like
docker
and
kubernetes
and
azure
provides
very,
very
good
support
for
that,
so
you're
definitely
first
class
citizen
or
in
containerization.
A
A
A
Now
another
very
interesting
thing
above
and
beyond
docker
and
kubernetes
is
actually
the
use
case
where
a
lot
of
people
want
to
just
use,
docker
and
not
necessarily
kubernetes,
so
they
want
to
move
into
containerization,
but
maybe
they
have
a
very
simple
workload
and
it's
not.
They
don't
require
all
of
the
orchestration
capabilities
that
kubernetes
comes
with.
So
azure
has
good
solutions
for
that
as
well.
One
of
the
key
ones
is
something
called
app
service
for
containers
app
service
is
something
we'll
talk
about
in
a
second
a
little
bit
more
as
well.
A
It's
basically
the
generic
pass
platform
for
azure,
but
one
of
the
those
capabilities
in
app
service
is
being
able
to
deploy
a
docker
image
and
be
an
essentially
have
that
be
running
transparently
on
the
cloud
as
well.
It's
very
close
to
a
pass
with
the
abstraction
being
that,
as
opposed
to
deploying
war
files
or
ear
files,
you're
really
deploying
a
docker,
a
docker
image,
so
you've
dockerized
your
your
application
in
one
way
or
the
other
in
general.
A
That
way
right.
So
these
are
the
sort
of
artifacts
that
you
should
look
from
a
cloud
vendor
from
a
from
a
java
chakra
they
vendor
to
provide,
and
in
fact
they
in
general
do
that
right.
So
the
these
artifacts
are
available
for
all
of
the
major
application
servers
servers
already
so
jwa,
cip,
wildfly,
weblogic,
west
europe
and
liberty
paira.
A
Again,
in
this
case,
just
like
vms,
you
know,
one
point
of
view
is
okay,
so
I
have
a
virtual
machine
at
the
operating
system
level,
and
I
have
my
docker
and
kubernetes
and
that's
all
we
all
you
need
well
that's
a
legitimate
way
of
thinking
about
it.
There
are
things
we
can
do
to
improve
those
experiences
as
well,
and
that
is
in
fact
what
we
what
we
have
been
working
on
in
terms
of
the
applications
for
vendors.
A
On
a
case,
it's
it's
reasonably
non-trivial
in
many
of
the
cases,
which
is
why
you
need
you
need
additional
guidance
and
additional
tooling
to
make
that
simpler
and
we've
we've
put
all
of
that
guidance,
scripts
and
samples
right
into
the
weblogic
operator.
So
if
you
go
into
the
web
logic
operator,
you'll
see
those
samples
there
right
at
this
moment
today,
the
samples
are
basically
doing
some
level
of
azure
integration,
so
certainly
integration
with
aks
integration,
with
azure
files
as
persistence,
volume
as
well
as
azure
load
balancing.
A
Just
like
we've
done
for
virtual
machines.
We
also
want
to
further
make
the
the
ease
of
make
the
use
case
as
simple
as
possible.
So
you
should
be
able
to
run
a
solution,
template
and
be
able
to
get
up
and
running
with
a
web
logic
installation
running
on
aks,
potentially
with
some
of
the
integrations
that
we
talked
about.
So
you
know
app
gateway
databases,
elastic
stack,
all
of
these
things
potentially
should
be
passed
like,
and
that
is
actually
what
we're
working
towards
beginning
early
next
year.
A
A
Okay,
so
open
shift
is
started
a
bit
slow
in
terms
of
its
adoption,
but
it
is
warming
up
all
right.
So
what
is
openshift
you
have,
if
you
haven't
heard
it
before
in
a
nutshell:
openshift
is
an
abstraction
above
and
beyond
kubernetes,
so
kubernetes
provides
essentially
basic
infrastructure
and
and
management.
Abstractions
openshift
is
yet
another
abstraction
above
that,
and
so
this
level
of
abstraction
provides
a
little
bit
of
ease
of
use,
but
it
also
enables
some
use
cases
a
bit
better
than
kubernetes
as
it
does
so.
A
It
provides
hybrid
cloud
deployment,
so
you
could
have
part
of
your
deployment
on
premise
and
part
of
it
on
the
cloud
you
could.
It
could
be
an
easy
pathway
from
moving
from
from
on-premise
to
the
cloud,
so
it
enables
a
bunch
of
different
use
cases
with
by
providing
a
uniform
level
of
abstraction
above
and
beyond
kubernetes.
A
So
we
do
we're
one
of
the
actually
first
clouds
outside
of
red
hat,
to
provide
a
managed
managed
openshift
offering.
So
this
is
called
azure
red
hat
openshift.
So
you
know
that
is
also
fully
enabled
and
has
been
mature
for
some
time
again.
You
could,
in
theory,
run
application
servers
that
provide
kubernetes-based
artifacts
on
openshift.
A
But
again
there
are
cases
where
we
really
could
help
out
by
providing
additional
guidance
and
tooling,
and
that
is
basically
what
we're
working
on
now
over
here
where
we
are
leading
with,
is
webster
liberty
and
open
liberty,
we're
very,
very
close
to
actually
having
our
first
release
of
guidance
on
how
to
run
western
liberty
and
open
liberty
on
openshift.
I
was
hoping
we
were
going
to
be
done
with
that.
A
You
know
in
time
for
this
talk,
but
not
the
case.
Unfortunately,
we're
still
a
few
weeks
out
before
we
can
really
test
and
validate
and
make
sure
that
that
offering
is
solid
and
before
we
can
announce
it.
So
please
stay
tuned.
That
is
something
where
we're
going
to
be
offering
very,
very
soon,
probably
again
in
in
just
a
few
weeks.
A
A
So
this
is
like
most
of
the
work
that
we
are
doing
we're
doing
this
in
in
in
as
a
partnership,
so
in
this
time,
where
partnership,
partnership
with
red
hat
and
microsoft,
to
make
this
offering
so
right
now.
This
is
essentially
stateless.
So
it
will
not
support
clustering
at
the
moment,
or
rather
jboss
ap
native
clustering
at
the
moment,
but
it
will
do
load
balancing
it
will
auto
deploy
across
multiple
jboss
ap
instances.
A
It
is
auto
scaled
so,
based
on
demand,
you
can
increase
or
decrease
the
size
of
your
jbr
cap.
Instances
per
deployment
it
is
monitored.
So
essentially
the
control
plane
is,
is
a
jboss
ap.
You
can
think
of
it
again
as
sort
of
a
replacement
of
the
domain
manager.
Functionality
provided
by
azure
in
this
case,
so
it
does
use
standalone
configuration
by
default
and
adds
the
jbossy
ap
on
app
service
management
plane
on
top
of
that.
A
So
this
will
go
ga
or
production
ready
fairly
soon,
probably
early
next
sometime
early
next
year,
but
this
is
a
really
good
time
to
get
engaged
with
it
right,
because
if
you
get
engaged
with
it
right
get
engaged
with
this,
offering
right
now
you're
able
to
take
advantage
of
the
engineering
team.
That's
working
on
the
solution,
so
you
don't
you're,
not
just
another
customer,
that's
anonymous!
You
can
actually,
in
a
very
direct
fashion,
work
with
the
exact
engineering
team
at
microsoft
that
is
working
on
the
solution
right
at
this
moment.
A
So
I
do
have
a
link
there.
If
you,
if
you're
interested
in
trying
that
out
and
and
giving
us
some
feedback
on
the
jboss
ap
on
app
server
software,
okay,
so
another
interesting
one
for
jakarta,
developers
is
jakartha
messaging
or
jms
support
for
azure
service
bus.
Now,
a
lot
of
people
aren't
familiar
with
azure
service
bus,
they're,
more
familiar
with
activemq
or
mq
series,
or
what
have
you?
A
service
azure
service
bus
actually
has
been
around
for
a
little
while
as
well,
and
it
provides
essentially
equivalent
functionality
for
message
oriented
middleware.
A
Now,
traditionally,
it's
been
more
focused
on
the.net
ecosystem,
but
what
we've
seen
is
that
there's
a
tremendous
amount
of
demand
for
a
managed
managed
jms
solution
on
azure.
So
what
we've
done
here
is
basically
provide
a
jms
interoperability
support
with
with
service
bus
right,
so
you
can
use
the
jca
adapters
and
most
of
that,
most
of
with
most
of
the
application
servers
and
be
able
to
make
it
work,
make
azure
service
bus,
your
jms
provider,
external
jms
provider,
for
your
application
server.
A
The
way
this
is
possible
actually
and
actually
has
been
possible
for
some
time
is
because
azure
service
was
actually
implements
the
amqp
protocol
and
there's
a
library
out
there
called
keep
it
for
jms
that
provides
a
rich
bridge
between
amqp
and
jms
right
so,
but
the
gap
that
had
been
there
for
some
time
is
that
service
was
actually
did
not
fully
support
jms
right.
So
what
we're
doing
now
is
making
sure
that
we
pass
the
jakarta
messaging
tck
and
that
the
service
fully
implements
all
of
the
capabilities
within
jms
right.
A
A
There
are
java
java
based
client
libraries,
you
can
use
those
and
if
you're,
using
azure
functions
and
azure
functions
is
basically
the
the
serverless
solution
for
azure,
which
also
provides
java
bindings.
You
can
also
use
azure
service
bus
through
the
azure
functions
way
as
well
of
directly
communicating
with
other
services.
That
way
again,
that's
not
that's
a
non-gms
way
of
interacting
with
a
service
bus
as
a
java
developer.
A
Okay,
so
I'm
gonna
do
a
little
bit
of
a
of
a
demo
here,
so
this
is
sort
of
a
lowest
common
denominator,
not
very
complex,
but
a
representative
sample
of
how
you
could
run
azure.
I
I
do
this
with
customers
and
they're,
always
sort
of
surprised
that
azure
can
even
do
this
sort
of
thing.
So
let
me
show
you
what
what
this
is.
So
it's
a
it's
a
very
simple
demo,
but
the
key
part
of
this
demo
is
that
all
of
it
is
available
on
github
right.
A
A
In
this
case,
the
example
is
running
wildfly
on
the
azure
kubernetes
service,
fairly
popular
combination
and
we're
using
a
simple
managed
database
in
this
case
of
manageable
stress,
postcards
instance
and
we're
using
azure
devops
pipelines,
and
that
is
a
sort
of
a
an
azure
native
version
of
jenkins.
If
you
will
so,
it
provides
ci
cd
capabilities
and
also
application
insights,
putting
in
that
sort
of
a
azure
flavored
equivalent
of
elastic
capabilities
and
I'll
show
you
these
things
in
just
a
moment
as
well.
So
you
can
do
the
setup
by
yourself.
A
So
all
you
need
is
a
github
account.
You'll
need
an
azure
subscription
to
do
this
because
you're
using
azure,
you
can
get
get
that
for
one
year
for
free.
If
you
don't
have
one
and
you'll
need
a
few
other
things
to
get
to
get
started.
All
of
it.
You
can
get
started
for
free,
basically,
so
other
than
that.
A
There's
step-by-step
instructions
on
how
to
start
a
managed
postgresql
instance
on
azure
I'll
show
you
that
in
action
once
I
log
on
into
the
azure
portal
I'll
show
you
how
that
looks
like
once.
It's
all
set
up
we're
going
to
use
a
azure,
kubernetes
service,
cluster
and
you're,
going
to
connect
to
the
kubernetes
tooling,
namely
keep
control
to
to
control
that
kubernetes,
backplane
and
access.
It
I'll
show
you
that
in
a
demo
in
a
moment
as
well,
there's
also
app
azure
application.
A
A
Okay,
so
the
reality
is
that
jpms
has
not
really
taken
up
that
much
right.
So
this
is
something
that
we
keep
talking
about
in
in
the
jakarta
e
space,
but
the
reality
is.
What
has
happened
is
that
java
application
servers
have
actually
superseded
what
jm,
what
jpms
provides
because
they've
long
supported
things
like
glossfish
have
natively
supported
osgi,
which
is
a
much
more
powerful
modularized
capability
solution
as
compared
to
jpms.
A
So,
there's
a
small
possibility
that
probably
some
incremental
work
will
be
done
in
jakarta,
e9
and
10,
namely
to
just
provide
module
info
for
each
other
each
of
the
specifications
and
for
people
that
are
really
insistent
on
using
jpms.
They
could
use
follow
that
path
and
sort
of
build
their
own
runtime.
A
For
the
application
servers
themselves,
it
would
be
a
step
backward
actually.
So
if
you
look
at
some
other
capabilities
in
wildfly
or
gloss
fish
or
probably
open
liberty
and
western
liberty
is
the
poster
child
for
this
they've
gone
much
farther
than
that
right.
So
you
can
really
build
up,
for
example,
open
liberty
from
scratch.
You
can
start
from
open
liberty
core,
which
is
really
nothing
much
more
than
just
the
I
tcp
available
protocol
layer
and
you
can
build
up
and
you
can
add
in
whatever
java
e
apis.
A
A
There
are
similar
capabilities
again
in
gloss
fish
and
similar
capabilities
in
wildfly
through
the
jbus
module
system,
so
it
is
in
fact
already
there.
So
it's
a
little
bit
of
a
misconception
in
my
opinion
that
you
know
somehow
the
java
ecosystem
hasn't
enabled
more
has
an
embrace
modularity
when
in
fact
it
has-
and
in
fact,
if
you
look
into
things
like
in
the
even
in
the
microprofile
space,
they've
gone
even
a
step
further
right
and
towards
the
modularity.
They
they
don't
even
have
a
profiling
profile
capability.
A
A
Do
you
think
so?
Another
question
from
ferry
is:
do
you
think
java
servers
will
eventually
mutate
into
lightweight
frameworks?
In
my
opinion,
java
is
already
a
lightweight
framework.
You
know,
so
you
know,
there's
no
other
technology
where
you're
you're
able
to
write
extremely
thin
wires
and
have
very,
very
fast
deployments.
A
So,
even
if
you
look
at
something
like
weblogic,
which
is
probably
the
you
know
the
extreme
edge
case
of
not
supporting
modularity,
you
know
even
if
you're
using
weblogic,
it
still
plays
extremely
well
with
things
like
containerization
and
you'll,
see
that
when
you
look
at
the
aks
examples,
we
have
logic
and
aks
examples
that
were
put
out
in
no
other
technology.
Will
you
will
you
be
so
easily
be
able
to
deploy,
have
fast
deployments
based
on
based
on
containerization
technology
because
it
allows
for
that
thin
water
capability?
A
Okay,
so
furry
reza,
I'm
sure
would
have
his
own
take
on
this,
and
so
this
is
a
comment
from
scott
cruz
of
ibm
from
ibm.
I'm
sure
having
one
take
on
this.
In
the
meantime,
I
think
it
is
fair
to
say
that
the
idea
of
standardization
other
profiles
has
come
up,
but
I
think
it
remains
to
be
seen
if
this
will
be
prioritized
from
a
jakarta
aspect
perspective
also.
I
do
work
for
ibm
and
open
liberty,
western
liberty,
so
we'll
know
that
liberty
configuration
model,
allows
you
to
pick
and
choose
to
only
start.
A
A
We
should
really
start
calling
it
jakarta,
yeah
yeah.
I
agree.
I
think
java
e
is
now
I
think,
of
the
past
official.
You
know
it's
been
officially
superseded
by
jakarta,
so
we
definitely
need
the
awareness
of
that
fact
right
that
java
e
is
no
more
we're
really
all
moving
into
a
different
different
technology
that
is
much
more
open
and
much
more
collaborative
than
java
used.
A
Okay,
any
other
questions
before
I
moving
into
so
actually
we're
running
a
little
bit
short
of
time,
so
I'm
going
to
actually
skip
the
demo
and
because
I
have
some
other
important
things
that
I
do
want
to
talk
to
you
about
in
in
the
next
15
minutes.
But
I
definitely
don't
want
to
stop
the
dialogue
right.
So
if
this,
if
anybody
has
any
other
anything
else,
they
want
to
talk
about.
You
know
I'm
happy
to
talk
about
that.
Also.
I
was
like
not
so
not
so
far.
A
So
in
the
interest
of
time
I'm
going
to
skip
over
the
demo,
I
think
feel
free
to
take
a
look
at
the
demo.
I
think
it's
it's
a
reasonably
interesting
enough,
especially
if
you
haven't
used
azure
before
it
will
give
you
a
flavor
of
of
how
to
deal
with
the
azure
resource
allocations
and
configuration,
but
I
think
I'm
gonna
jump
back
up
into
the
presentation,
since
we
don't
have
actually
a
lot
of
time.
A
But
if
you
want
to
take
a
look
at
the
demo
and
you
want
to
try
it
out
yourself,
you
know
the
the
github
repository
link
is
posted
in
the
in
in
the
slide
deck
as
well.
Okay.
So
let's
talk
about
roadmap,
so
I've
already
said:
there's
some
areas
where
we've
made
very
good
progress,
so
web
logic
on
virtual
machines,
I
think,
is
in
reasonably
good
shape.
A
Our
our
jboss
eap
on
app
service
capability,
I
think,
is
going
to
be
a
very
key
one
for
jakarta
for
empowering
jakarta
developers
on
azure,
and
that
is
also
in
reasonably
good
shape.
Again,
it
will
probably
go
generally
available
early
sometime
early
next
year
and
then,
meanwhile,
this
is
a
good
time
to
engage
with
with
the
team.
A
If
you
want
to
work
on
that,
and
similarly
the
jms
support
for
azure
service
bus
is
actually
in
very
good
shape,
also,
probably
by
the
end
of
this
year,
will
be
announcing
that
yes,
service
was
fully
compatible
with
jakarta
messaging.
So
there's
some
other
areas
where
we're
working
on
still
so
jvos
eip
on
virtual
machines.
Wildfly
on
virtual
machines,
is
something
we're
working
on
I'll
talk
about
that
in
just
a
moment,
we're
beginning
to
work
with
ibm
to
enable
webster
traditional
nd
on
on
virtual
machines
as
well.
A
Obviously,
we'll
be
beefing
that
up
and
bringing
that
up
to
the
level
where
we
have
for
the
solution
templates
for
azure
virtual
machines
and
there's
a
few
areas
where
there's
identified
gaps
that
we
know
that
is
in
our
is
on
our
horizon,
and
we
will
we
will
work
to
to
essentially
and
to
make
that
not
be
gaps
as
soon
as
possible,
so
that
would
be
enabling
website
liberty
on
aks
again.
This
is
this
is
a
short
time
horizon.
A
We've
already
begin
to
talk
with
our
partners
at
ibm
to
enable
just
this,
and
also
enabling
jbossy
ap
on
aks.
So
there
is
a
fair
amount
of
use
cases
where
that
that
also
happens
and
finally
enabling
redis
so
enabling
all
those
use
cases
that
I
talked
about
using
it
as
a
hibernate
or
jps
second
level
cache
using
it
in
application
server
level
cache.
For
example,
open
liberty
would
support
this
very
very
easily
and
also
using
azure
redis,
just
as
a
j
cache
provider
inside
of
your
java
applications.
A
So
those
are
areas
that
we
want
to
unblock
as
well.
Okay,
so
briefly,
I
want
to
talk
about
where
we
are
just
one
level
deeper
with
our
azure.
Well
logical,
natural
virtual
machines
roadmap,
so
we
nav
have
enabled
a
number
of
integrations,
so
this
would
be
databases
single
cluster,
a
single
instance
or
cluster
use
cases,
integration
with
azure
wrap
gateway
as
a
load,
balancer
integration
with
the
azure
active
directory,
but
there
are
a
few
things
missing,
so
we
want
to
enable
coherence,
as
we
mentioned
through
the
solution
templates.
A
We
also
want
to
enable
connectivity
with
azure
manage
elastic
service
for
distributed
logging
for
for
web
logic.
This
is
a
very
common
use
case
for
for
logic
and
also
pro
see
if
we
can
provide,
above
and
beyond
the
solution
templates,
some
very
simplistic
migration
tools
where
you
take
a
an
existing
deployment
and
sort
of
auto
magically
try
to
port
it
over
to
to
azure
is
so
that
is
also
something
we
are
looking
to
enable
in
the
near
future,
okay,
so
weblogic.
A
Obviously,
we
want
to
enable
the
full
host
of
solutions
there
as
well
similar
to
what
we're
planning
to
do
for
for
the
solution
templates
for
for
web
logic,
on
on
vms,
so
again
in
our
website
for
webster,
open
liberty,
openshift
roadmap,
we're
very
close
to
getting
the
the
cluster
guidance
up
and
running
so
that
it's
usable
very
easily
by
you
both
for
western
liberty
and
open
liberty.
We've
also
done
some
initial
work
to
to
enable
the
azure
active
directory
integration
with
western
liberty
and
open
liberty.
A
I
believe
I
put
a
blog
entry
out
there.
Some
of
you
might
have
noticed
that
already
but
again
in
our
general
pipeline.
We
want
to
enable
all
of
these
integrations,
probably
through
a
solution
to
marketplace,
solution,
template
mechanism
above
and
beyond,
providing
a
simple
guidance.
All
of
these
other
integrations.
We
want
to
make
sure
it's
as
easy
as
possible.
A
So
here's
where
we
are
with
the
jbl,
cip
and
wildfly
on
virtual
machines
work.
So
this
is
also
a
work
in
progress.
So
there
is
a
number
of
use
cases
being
supported
right
now,
so
these
would
be
a
standalone
virtual
machine
cluster
of
jboss
ap
and
a
cluster
of
java
sap
on
what's
called
virtual
machine
scale
sets
so
it's
similar.
A
So
currently,
these
are
community
quick,
start
templates,
so
they're
a
step
below
what
you
would
have
in
terms
of
a
solution
template,
but
you
can
begin
to
use
them
and
begin
to
engage
the
team
to
see
you
know
what,
if
it's
useful
or
not,
and
what
type
of
use
cases
would
you
like
to
see
out
of
it?
But
hopefully,
by
the
end
of
this
year
these
will
also
become
jointly
supported,
marketplace
solution,
template
offerings
by
join
jointly
published
by
or
by
microsoft
and
and
red
hat.
A
So
hopefully
that
will
come
about,
but
in
the
meanwhile
you
can
use
the
community
quickstart
templates,
there's
a
there's,
a
link
to
those
okay.
So
I
do
want
to
finish
up.
We
have
about
10
minutes.
I
do
want
to
leave
some
time
for
q,
a
if
not
I'll,
show
you
the
demo
in
in
the
last
10
minutes
or
so.
So.
To
summarize,
there
is
a
dedicated
team
working
to
on
your
behalf
to
make
jakarta
e
developers
successful
on
azure.
A
We
do
want
to
make
sure
you
are
first-class
citizens
and-
and
azure
is
a
very
good
home
for
you,
but
frankly
we
need
your
help
to
do
that
right.
So
the
more
engagements
we
have,
the
more
we
have
people
trying
out
these
solutions
and
giving
us
feedback
on
our
roadmap
on
what's
working
and
what
isn't
and
what
they
would
like
to
see.
A
That's
what's
going
to
accelerate
this
work,
so
please
consider
doing
that.
So
the
way
you
do
that
is
very
simple.
It
is
just
this
survey,
you
fill
out
the
survey
we
get
in
touch
with
you
and
we
begin
to
work
with
you
in
terms
of
enabling
all
these
solutions.
So
again,
the
objective
here
is
to
provide
a
robust
guidance
and
tooling
for
migrating
jakarta
applications
to
azure,
using
either
containers
or
virtual
machines
for
the
major
application
servers.
A
So
this
would
be
weblogic
western
liberty,
j,
boss,
cap
wildfly,
so
we
already
have
a
patent
pairs
well
on
the
way,
I
think
that
is
really
speaks
to
chakarte
developers
being
first
class
citizens
on
azure,
so
jboss,
cip,
on
app
service
and
we'll
also
through
all
of
this
work
and
beyond
enable
more
and
more
of
these
integrations.
So
a
good
example
of
that
again
is
the
azure
service
bus
support
for
jms.
A
Similarly,
we
want
to
meet
all
of
the
common
use
cases
for
jakarta
developers,
whether
it's
directory
server
database
caching
distributed
logging
messaging
whatever
it
is
right.
So,
ultimately,
my
major,
if
you,
if
you
take
away
one
thing,
please
consider
doing
this-
you
or
your
friends
or
your
colleagues
engage
with
us
fill
out.
The
survey
tell
us
what
kind
of
thing
you
would
like
us
to
work
on
through
that
survey
and
potentially
also
work
with
us
one-on-one
to
enable
these
use
cases.
That
is
the
most
effective
thing.
That
is
the
most
effective
way.
A
A
So
you
can
compare
each
of
those
approaches.
So
that's
another
github,
another
github
repository
on
my
on
my
personal
account.
It's
a
loss
for
click
there
so
feel
free
to
take
a
look
at
that.
Okay,
so
I
have
about
five
or
six
minutes.
So
let
me
stop
here
and
see
if
there's
any
questions,
if
not
I'll,
try
to
quickly
show
you
the
at
least
a
little
bit
portion
of
the.
A
A
Okay,
so
this
is
the
same
question
from
free,
so
free
the.
I
think
we
should
take
this
offline,
so
there's
really
nothing
wrong
with
the
model
that
java
application
servers
have
been
using.
In
fact,
if
you
look
at
things
like
spring
boot,
in
fact,
spring
boot
is
following
that
approach.
Now
of
of
introducing
the
concept
of
layering,
you
know
within
java
application
servers
and
again
things
like
open
liberty
and
wildfly.
They
already
support
quantum
organization
right.
So,
if
you're
specifically
talking
about
fat
jar
based
deployment,
even
that
is
supported
right.
A
So,
if
you
look
at
open
liberty-
or
you
know
the
the
recent
support
for
deployable
jar
files
in
in
wildfly
or
paera
micro,
all
of
those
actually
support,
I
think
what
what
you're
really
talking
about
is
the
is
embedding
the
application
and
the
application
server
together.
So
I
would
ask
that
you
investigate
a
little
bit
more.
In
fact,
a
lot
of
the
things
you're
talking
about
may
already
be
possible
in
the
jakarta
ecosystem.
A
This
is
this:
is
your
last
opportunity,
folks,
you
can
obviously
email
me
later
or
find
me
on
on
twitter
or
what
have
you?
But
if
you
have
any
questions,
this
is
a
good
good
time
for
us
to
chat.
One
on
one
would
be
nice
to
see
microsoft.
Jakarta,
compatible
application
server,
definitely
right.
So
that
is
something
we.
A
We
are
obviously
considering
right,
but
at
this
at
this
moment
I
think
it's
a
little
bit
premature
right.
So
I
think
we
first
need
to
do
our
homework
in
terms
of
enabling
the
existing
runtimes
to
run
well
on
azure,
first
of
all,
and
also
make
sure
that
we
are
serving
the
customers
that
are
using
those
runtimes
before
we
we
did
our
own.
If
you
will,
I
think
once
we
did
that,
and
we
have
a
good
cohort
of
real
jakarta
developers
on
azure.
A
A
A
A
Let
me
go
back
and
look
here
and
we
also
have
a
database,
so
this
is
postgres
running
azure
database
repository
server,
as
you
can
see,
and
also
we
have
application
insights
all
right.
So
I
did
a
little
bit
of
of
of
testing
and
lift
earlier.
So
I'll
show
you
the
output
of
that.
So
I
need
to
go
to
logs
and
go
through
logs
here.
A
My
screen
a
bit
okay.
So
if
you
look
closely
here,
these
are
all
of
the
log
messages
that
have
come
out
of
my
applications.
Finding
all
coffees
removing
a
coffee
number
two,
so
these
are
all
of
the
log
level
messages
it's
coming
from
log
back,
as
you
can
see
all
of
those
details
in
here
so
again
the
database,
the
azure
community
service,
as
well
as
as
you
can
see,
application
insights.
A
A
So
if
you
look
at
services,
I
have
kubernetes
itself
running.
I
also
have
a
load
dancer
running
for
azure
cafe.
There
is
an
external
ip
for
this.
If
I
just
log
in
this
external
ip
enter
my
browser,
there's
wildfly
up
and
running
on
aks
on
an
aks
instance,
I
can
actually
access
the
application
itself.
It's
super
simple.
You
can
take
a
look
at
it.
Look
at
it
a
bit
later.
A
And
there's
the
article:
it's
a
simple
card
application.
It's
just
you
know
you
can
delete
an
entry
and
recreate
recreate
it
here.
Okay,
so
there
you
have
it
it's
a
there.
You
have
a
java
you
running
on
azure
kubernetes
service
on
on
azure,
okay,
so
I
think
I'm
right
at
the
top
of
the
hour
I'll,
just
one
take
one
last
opportunity
to
see
if
there's
any
questions.
Otherwise
I
thank
you
for
for
attending
this
talk
and
hopefully
hope
to
see
you
on
azure.
A
Awesome
well,
thank
you
for
that
presentation.
At
this
point
yeah
we
are
just
at
the
top
of
the
hour.
So
great
timing
on
that.
Thank
you.
Everyone
for
joining
today.
If
you
are
on
your
way
out,
please
consider
filling
out
the
call
to
action
at
the
bottom
that
green
button
that
says
help
us
improve
by
completing
the
post
event
survey.
It
would
be
great
to
get
some
feedback
and
see
how
we
can
continue
to
grow.
The
chicago
tech
talk
series
moving
forward
enjoy
the
rest
here
today.