►
From YouTube: AsyncAPI SIG meeting 27 (July 7, 2020)
Description
This is the recording for the AsyncAPI Special Interest Group (SIG) meeting #27.
Attendees:
- Fran Mendez
- Francesco Nobilia
- Łukasz Gornicki
- Paul Taylor
Moderation:
- Łukasz Gornicki
Agenda & Notes:
https://github.com/asyncapi/asyncapi/issues/401
Chat Dump:
00:23:16 Fran Méndez: https://deploy-preview-108--asyncapi-website.netlify.app/docs/specifications/2.0.0#serverObject
00:49:43 Fran Méndez: https://github.com/asyncapi/asyncapi/tree/master/versions/2.0.0
A
A
So
today
we
don't
have
any
specific
written
agenda
because
at
the
end
it
say
anything
for
you
not
for
from
me
and
from
the
tip
out
our
our
voices,
but
I
can
just
quickly
show
you
because
I
think
it's
interesting
to
share
those
most
important
things
that
are
happening
at
the
moment
and
the
initiative.
So
let
me
just
get
the
link
I
want
to
share
you
with
with
you
an
update
on
the
on
the
parser
development.
A
You
see
it
up,
yes,
yes,
so
the
good
news
is
that
we
have
I
think
it's
pretty
close
to
once.
You
are
released
because
the
five
issues
that
we
have
here
they
are
all
actually
actually
all
of
them
have
APR
opened
already,
because
also
a
one
guy
from
the
community
joined
the
efforts
and
created
ready
to
be
ours
yesterday
for
those
two
issues.
A
So
that's
it
if
it
comes
to
two
community
tools
for
asking
API
and
the
other
one
is
the
web
site
that
it's
almost
almost
merged,
so
the
new
website
that
Fran
is
working
on,
but
we
also
wrote
about
it
on
Twitter,
so
you
should
be
aware
of
the
of
what
it's
the
work
on
at
the
moment
and
I
can
share
the
the
the
website
may
be
sure
I
saw
before
I
love.
You
I
just
wanted
to
share
if
someone
didn't
notice.
A
If
you
don't
know
yet,
we
are
I
hope
you
know
that
every
two
weeks
since
few
months
we
are
releasing
a
newsletter
about
what's
happening
in
API,
but
we
to
get
a
wider
audience,
not
everyone
likes
to
read
emails,
and
now
we
will
also
release
the
same
as
a
blog
post
and
last
week
was
the
first
time
we
did
it
so
we'd
say
so.
This
blog
post
also
contains
the
updates
on
what
we're
working
on
currently
if
it
comes
to
the
core
team.
A
B
Whole
point
here,
I
think,
is
to
reach
a
wider
audience.
We
don't
want
to
collect
emails
just
for
the
sake
of
collecting
emails
right.
We
want
people
to
subscribe
to
the
newsletter,
so
they
don't
have
to
remind
to
come
and
check
every
time
right
about
about
the
new
another
new
about
a
new
information
right
and
not.
Everybody
is
using
an
RSS
tool
right,
so
so
yeah.
So
that's
why
we
started
a
newsletter
and
but
yeah.
B
Like
look
I
said
if,
if
you
don't
want
to
subscribe
for
whatever
reason
you
don't
want
to
get
too
much
noise
on
your
and
your
email,
not
because
we're
making
too
much
noise
but
yeah
our
newsletters
other
people
newsletter
other
people's
instead
they're
you
know,
sometimes
it
becomes
too
noisy.
So
if
you
prefer
other
ways
yeah,
you
can
just
read
it
here
in
the
blog
and
on
the
new
website,
which
will
have
RSS
from
the
website
for
that
blog.
So
it
should
be.
B
B
B
B
B
The
idea
was
to
make
a
to
make
an
easy
way
for
people
to
understand
what
we're
talking
about
right,
because
not
everybody
is
familiar
with
specs
and
and
not
everybody's
familiar
with
event-driven
architectures.
So
first
thing
we
thought
is
yeah.
Let's
do
a
demo
here
all
right
right
on
your
face.
Whenever
you
enter
the
website,
you
get
a
Dem
up
there
and
you
see
a
demo
on
that
side.
Like
you're.
Writing
you
type
in
the
syncopate
document
and
on
the
right
side.
You
see
it
the
documentation
like
it's
a
fake
documentation.
B
B
So
this
is
the
useful
for
the
newsletter
sponsors
we
wanted
to
make
the
community
channels
or
the
communication
channels
more
visible.
So
we
added
this
on
the
home
page
as
well,
like
you
can
join
slack
and
during
the
public
meetings
like
this
public
meetings
right
so
so
yeah
and,
as
you
can
see,
we
have
bouquets
as
usual,
saying
good
morning
on
the
channel
and
and
all
the
reactions
and
like
only
Jonas,
like
any
reacting
with
the
sleeping
pirate
here
so
yeah,
it's
actually
very
accurate
of
what's
happening
every
day,
almost
every
day
and
and
yeah.
B
So
as
I
was
saying,
although
you
know
buttons
here
to
add
to
the
to
add
a
reminder
or
Google
an
event
to
your
Google
Calendar
or
during
the
mail
list,
or
you
know,
or
the
channel
youtube
channel
or
watching
the
recordings
of
these
mittens
today
and
the
and
the
upcoming
ones
right.
This
should
be
yeah.
This
would
be
accurate,
accurate.
So
this
is
being
calculated
at
all
time.
So
far
is
a
calculation.
As
you
can
see,
this
is
6:00
p.m.
next
one
is
6:00
p.m.
B
B
We
wanted
to
tell
that
this
is
not
a
crazy
idea
by
a
few
guys,
which
is
also
the
case,
but
not
just
that
so
say.
We
wanted
to
show
the
world
that
some
companies
are
already
using
it's
in
KPI.
At
some
point,
we
will
link
these
logos
to
specific
use
cases
or,
let's
say
demonstrations
that
is,
companies
are
using
some
KPI
but
yeah
in
the
beginning.
It's
gonna
be
just
logos,
I
guess
in
the
meantime
right,
but
it
will
be
cool
that
more
companies
contact
ads
like
hey,
we
are
using
it
in
KPI.
B
We
want
to
be
there
on
this
logo
clouds
right.
So,
as
you
can
see,
there
is
a
link
here,
and
you
can
let
us
know
here.
This
will
create
an
issue
on
the
websites,
creeper
and,
and
there
you
can
explain
like
hey,
so
my
company
is
company
X
and
we
want
to
get
listed
there,
and
this
is
how
we're
using
missing,
API
so
yeah
and
to
continue
with
the
previous
website.
We
have
some
quotes
here
from
different
people,
some
testimonials
right
and
and
the
latest
the
latest
from
our
blog.
B
So
so
yeah,
that's
the
the
main.
This
is
the
main
homepage,
I'm
still
working
that
might
change,
but
I,
don't
think
it's
gonna
change
so
much
the
main,
the
homepage
and
what's
being
improved
as
well
as
the
its
navigation.
So
you
can
see
that
getting
started,
tutorials
specification
and
we
added
a
new
section
which
is
called
use
cases.
B
This
is
pretty
much
related
to
what
we
what
I
was
talking
before
about
this
loggers
and
we
would
love
to
have
more
real
use
cases,
companies
and
people
using
missing,
KPI
and
other
companies
and
just
to
show
people
what
could
you
be
using
async
api
for
so
people
get
a
better
grasp
of
what
it
is
right
and
again.
This
is
not
done
yet,
but
yeah,
let's
go
into
the
documentation,
for
instance,
so
documentation.
In
my
opinion,
this
has
got
an
upgrade.
B
B
Okay,
so
yeah
you,
you
see
you
can
you
can
you
can
see
the
the
table
of
content,
but
in
this
case
there's
only
one
section
so
there's
no
that
that's
a
bad
example
to
to
show
cave,
but,
as
you
can
see,
you
have
that
in
this
case
you
can
have
a
table
from
content
here.
The
navigation
on
the
right
side.
B
Don't
remember,
it
happened
to
me
and
I
specification,
so
yeah,
so
I
can't
imagine
people
trying
to
find
some
things
right
so
in
case
in
case
you're,
reading
in
the
middle
of
somewhere
in
the
spec
right,
like
I,
don't
know
you
here
and
you
want
to
go
to
a
server
object.
Yes
right!
So
that's
to
me,
that's
I
mean
I,
don't
have
to
explain
the
table
of
content
value
right,
but
I
think
it's
really
valuable
and
thanks
you
guys
for
suggesting
this,
because
it's
really
valuable
and
I
think
the
next
step.
B
Maybe
your
next
iteration
will
be
adding
search
to
the
to
the
whole,
not
just
to
the
to
this
page,
but
to
the
whole
website
right
to
the
whole
documentation,
specifically,
maybe
including
also
blog
post,
so
so
it's
easier
to
find
content,
basically
its
life.
Yet
it
is,
but
it's
a
URL
is
a
deploy
preview.
You
can,
let
me
share
it
here
in
the
out.
Why
send?
B
B
You
see
that
the
tap
now
on
the
you
see
the
github
pull
request:
yeah,
okay,
so
it's
this
pull
request.
Actually
it's
a
preview
of
this
pull
request
so,
as
I
keep
working
on
this
pull
on
this
pull
request,
you
will
see
updating
this
sale
URL
the
URL
will
not
change.
So,
oh
yeah,
that's
that's
super
useful.
That's
thanks
to
nettle!
If
I
deployed
preview
and
yeah,
let.
E
B
C
B
B
Connecting
basic
people
with
the
website,
so
whenever
someone
changes
something
on
the
repo
on
this
under
specification
right,
it
gets
somehow
pushed
to
the
website.
It
might
be
push
or
it
might
be
the
other
way
around.
It
might
be
fetch
it
from
your
side,
but
yeah
synchronize,
let's
say
so.
We
don't
have
to
store
the
specification
in
two
places
right
and
we
don't
have
to
maintain
it
in
two
places
and
also
at
some
point.
E
B
Is
this
is
not
part
of
this
effort
to
improve
the
documentation?
This
initially
was
just
a
way
to
rewrite
to
move
from
Hugo
to
next
year's,
so
different
finger
and
I
just
took
the
opportunity
to
really
sign
this
a
little
bit
but-
and
there
are
some
improvements
but
yeah
so
now
we
will
have
to
sit
together
and
and
think
about
how
to
improve
the
documentation
and
how
to
actually
improve
the
whole.
B
The
whole
website
experience
as
well
right,
so
people
learn
people
it's
easier
for
people
to
learn
faster
about
the
spec
and
get
more
tutorials
and
yeah.
So
this
this
needs
to
be
done.
Yet
this
is
just
a
small
improvement
that
I
did
while
I
was
migrating,
but
not
really.
The
the
purpose
of
these
posters.
B
B
Okay,
so
generator
finally
got
its
place
on
the
website
right.
It
has
a
landing
page
for
itself
and
I
think
this
is
cool.
This
is
something
you
can
interact
with
and
play
with
it
like
I
want
to
generate
code
and,
oh,
yes,
you
have
a
spring
boot
using
docker.
You
can
copy
it
here
so
yeah
and
by
the
way
this
is
embeddable
on
the
documentation.
So
this
is
ready
to
be
embedded
on
the
documentation
whenever
we
want.
So
that's
that's
gonna
be
useful,
get
our
actions,
something
what
you
get
right.
B
So
it's
like
it's
just
a
new
website,
I
think
it's
looking
much
better.
I
think
also
one
of
the
things
one
of
the
key
things
we
did
here
is
there
is
now
a
single,
a
single
drop
down.
Let's
say
if
we
want
for
community
resources
right,
so
we
we
have
some
tools
here,
but
we
also
want
to
feature
some
tools
from
the
community.
B
Right
like
like
we've
been
doing
till
now
like
this
is
this
is
nothing
else
than
what
we
already
have
the
list
of
tools
that
people
have
contributed
to
to
work
with
async
API,
not
necessarily
the
tools
that
we
maintain,
but
people
that
tools
that
people
contributed
and
not
just
tools
like
services
as
well
like,
for
instance,
bam.
You
have
bump
here,
and
it
says
software-as-a-service
right
so
so
yeah
same
thing,
more
visibility
again
to
the
github
organization.
B
B
Slow
but
yeah,
it's
definitely
much
better
than
before.
The
images
were
taking
a
lot
of
time,
so
yeah
and
and
yep
so
again,
block
codes
are
marked
down
and
you
can
find
all
this
content
on
the
website.
Repo
and
inside
the
a
syncope
organization
so
feel
free
to
open
an
issue
saying
like
hey
I,
want
to
write
a
blog
post
about
this
or
that
and
and
then
open
a
pull
request,
and
so
oh
yeah
and
the
shop
to
shop.
B
B
This
is
something
that
I
want
to
document
as
well
like
how
to
install
it
in
your
own
computer,
on
your
own
server
and
over
time.
I
hope
people
help
us
to
document
how
to
deploy.
It's
in
KP
I
have
to
AWS
a
sure,
Google
cloud
right,
so
that
will
that
will
be
great
if
we
could
also
automate
somehow,
maybe
with
terraform
or
something
like
this
I
don't
know
so
so
people
can
actually
deploy
this
in
their
favorite.
B
B
And,
for
instance,
in
this
case,
in
this
case,
de-icing
KP
I,
have
is
just
a
place
where
you
can
edit
your
files
and
store
them
right.
But
the
idea
is
to
keep
improving
it.
It's
a
way
to
store
your
developer
portals
as
well,
so
you
can
have
developer
portals
internal
or
external
developer
portal
right.
You
can
share
that
education
with
your
with
your
team
or
with
your
partners
or
with
the
public
audience
and
and
then
also
over
time.
The
idea
is
to
get
into
API
management
right
to
get
into
this
area
of
handling.
B
Let's
say
having
like,
if
you
want,
like
an
API
gateway,
think
about
an
API
gateway
for
events
that
you
can
deploy
on
your
servers
and
that
will
connect
to
a
syncope
I
have
and
yeah.
So
you
don't
want
your
events
to
be
flowing
around
the
internet
right,
because
your
events
might
contain
sensitive
information
and
you
might
want
to
to
have
it
on
your
own
servers.
B
Okay,
thank
you
and
also
yeah.
We
we're
still
not
clear
that
we'll
run
this
software
as
a
service,
because,
that's
you
know,
that's
a
lot
of
work
that
that
sounds
more
like
building
a
company,
alright,
so
so
yeah,
and
we
want
to
keep
this.
This
is
a
community
effort
and
think
about
it
like
Redis.
If
you
want
like
now
that
salvitore
still
step
back,
it
came
to
my
mind
like
you:
can
you
can
think
about
about
it
like
credits
or
like
elasticsearch
or
all
this
project?
You
can
you
install
it
in
your
servers?
B
You
I
mean
you
have
friends
labs.
You
have
relaxed
search
itself,
selling
the
services
as
well,
but
yeah
I,
don't
think.
In
my
whole
life
I've
ever
used
in
their
online
services,
their
cloud
services
I
was
always
installing
it
to
myself
in
my
servers.
So
so
this
should
be
more
or
less
the
same.
Hopefully,.
B
B
So
that
is
it
from
my
side
like
this
is
pretty
much
what
we're
doing
now
we're
working
on
the
new
website
and
they
have
at
the
same
time,
so
we
can
open
source
it
and
we
can
have
the
new
website.
2.2
sync
API
have
but
yeah
for
that.
We
need
to
have
a
sink
API
have
in
shape
first
and
in
public
as
well,
because
not
accept
yet
public
and
and
yeah.
So
that's
pretty
much
what
I'm
doing
there?
B
Hopefully,
as
you
can
see,
we
soon
will
have
the
parser
the
first
parser,
the
first
really
stable
release
of
the
parser
and
also
the
generator
and
yep.
That's
who
that
should
be
fun
to
start
building
new
tools
on
top
of
it
or
do
2-0
releases
of
those
yeah
start
breaking.
But
you
know
and
bumping
the
bursting.
D
You
have
top
of
things
from
me,
so
your
social
are
getting
their
value
for
money
for
sponsoring
the
conference
and
they
made
me
write
a
blog
post
which
will
go
up
on
the
meal
soft
website
this
week,
so
you'll
it
describes
the
community
and
what
I
resent
it.
So,
let's
see
if
we
can
also,
if
you
want
it
post
it
on
the
facing
blog.
That's
one
thing
to
thank
you
for
the
swag
as
well:
swag
wine
for
right,
t-shirt
somewhere
as
well,
so
I
should
wear
it
next
time.
D
And
thirdly,
I
never
had
some
conversations
around
extensions
and
you
were
thinking
about
what
you're
gonna
do
moving
forward.
So
didn't
really
want
to
touch
on
extensions,
but
it's
more.
Are
there
any
areas
that
you
think
I've
been
talking?
Obviously,
I
can
help
with
documentation
or
tutorials
I'm,
not
gonna,
learn
Java
scripts.
I
didn't
go
there
with
that.
D
B
This
arctic
area,
right
now
like
we,
only
have
one
tutorial
and
the
same
tutorial
in
another
version
in
an
intern
interactive
version,
so
it
will
be
great
to
have
like,
even
if
it's
you
know
like
faking
a
real
use
case
and
or
could
be
potential
real
use
case,
it
would
be
great
to
have
some
tutorials
or
yeah
some
yeah
I
think
tutorials
will
be
great,
explaining
I,
don't
know.
It
comes
always
to
my
mind,
like
explaining,
demonstrating
how
you
could
build
microservices
to
communicate
with
in
between
each
other.
B
Each
other
I
already
did
with
streetlights
this
Internet
of
Things
thing
right,
but
yeah,
it's
not
so
much
Internet
of
Things,
because
it's
only
using
a
kiddie
tea,
but
it
will
be
great
to
have
something
I
don't
know
like
if
you
have
more
knowledge
about
C++
or
Java,
or
something
like
this.
It
would
be
great
to
to
show
how
you
can
generate
code
in
these
other
languages
and
yeah.
B
B
Those
that
come
to
my
mind
are
always
there
is
the
Academy
of
publish
and
subscribe,
like
some
people
get
confused
about
the
meaning
of
favorites
and
subscribe
em
and
how
we
can
solve
this
without
yeah
like
I,
don't
know
or
or
for
version
3.
How
can
we
solve
this?
On
version,
3
of
the
spec
and
and
probably
to
me,
this
is
like
this
issue
is
actually
like.
It's
a
smell
of
a
an
underlying
bad
design
on
the
spec.
B
You
know
like
there's
something
bad
in
the
spec
that
is
making
this
easy
pop
pop
pop
out
right
and
and
it's
a
it's
a
code
smell
to
me
so,
probably
and
and
and
I
think
I'm
already
have
an
idea
and
what
it
can
be,
but
yeah
someday
I'll
explain
what
are
my
ideas
and
they
on
this
area,
but
yeah.
That's.
That
will
be
one
great
thing
like
adding
ideas
on
how
we
can
get
rid
of
this
problem
once
and
for
all
and.
B
Also,
there
are
people
suggesting
that
we
should
probably
have
another
verse
like
and
subscribe,
like
a
like
request,
like
reply,
how
to
make
all
this
request
reply
over
messaging
systems
be
defined
on
async
API,
so
we
can
actually
know
that
this
information
come
in
through
this
channel
is
actually
the
reply
of
these
other
coming
from
this
other
channel
just
yeah.
There
are
many
people
doing
this
request
reply
systems
on
over
messaging,
so
so
that
will
be.
That
will
be
interesting
and
that's
enough
ideas
from.
D
I
might
start
with
the
tutorial,
because
I
have
some
use
cases
in
public
sector
around.
How
do
you
tell
government
something's
happened
and
it's?
This
is
a
perennial
thing:
rabbits,
they
have
no
way
of
describing
it.
So
everything
just
custom-build
the
whole
time.
So
maybe
I'll
find
a
use
case
around
there
and
generate
a
tutorial
and
take
it
from
there.
Yeah.
B
A
I
think
the
easiest
would
be
don't
because
the
there's
just
one
tutorial
like
francette
and
there's
no
I
mean
we
still
have
a
backlog
issue
to
think
about
information
architecture
for
the
docs.
So
if
you
would
have
like
it
would
be
difficult
for
you
to
fit
your
content
into
current
structure.
Just
forget
about
dogs
just
think
about
block.
Only
so
your
tutorial
can
still
be
a
block
or
so
and
I
think
it
would
be
even
the
best
because
for
you
you
would
not
have
to
focus
on
D
on
the
on
the
dogs.
A
You
would
only
you
would
be
free
from
the
limitations
or
whatever
we
have
in
in
the
dogs,
and
you
would
just
focus
on
on
writing
a
blog
post
that
would
be
published
in
US
an
API
block
that
future.
Once
we
streamline
the
focus
on
development
focus
on
documentation,
we
can
yeah,
take
your
content
and
fit
into
into
a
you,
don't
create
even.
B
A
Google,
Docs
I
will
say
like
initially.
This
could
be
a
Google
Docs
or
something
someplace
where
we
can
quickly
collaborate
and
I
mean
Google,
Docs
I,
don't
like
Google
Docs,
because
you
know
you
have
to
be
sharing
the
link
and
there's
no
visibility.
It's
it's
always
preferable
a
pull
request.
It
has
more
visibility
right,
but
but
yeah
whatever.
Whatever
works
for
you
to
draft
the
content
and
put
in
some
ideas
there
like
here,
we
do
have
something
interactive
or
whatever
and
then
we'll
make
it
happen
like
we
could
set
on
the
next.
B
Whenever
we
have
the
next
website
and
we
move
the
focus
in
to
improve
improving
the
documentation.
If
you
had
a
comment
there,
like,
we
still
have
a
interactive
widget
here,
doing
blah
blah
blah
whatever
or
other
other.
Whatever
other
things.
We
will
make
this
interactive
content
and
if
we
will
adapt
it,
that's
it
all.
E
B
A
schema
you
mean
of
the
whole
initiative,
like
with
all
the
tools
like
a
diagram
you
mean
just
for
the
for
the
for
the
spec
Jesus
come
on.
You
mean
different,
schema
or
or
a
diagram,
a
diagram.
Okay,
no
so
I,
don't
think,
there's
a
diagram
or
the
for
the
whole
spec
for
this
2008
such
man.
It
would
be
useful.
Oh
yeah,
definitely
but.
A
B
I
think
it's
useful
and
I
think
it
will
be
even
more
useful
to
have
like
what's
Lucas.
There
is
to
have
something
to
generate
it,
because
then
it
will
be
automatically
generated
on
future
versions
right,
so
we
don't
have
to
constantly
be
maintaining
it.
So
this
this
actually
could
be
really
cool.
Even
this
could
be
a
really
cool
use
case
for
the
generator.
Actually,
if
you
think
about
so
the
generator
could
be
the
generator.
The
generator
can
output
anything
right.
B
The
thing
here
is
that
which
you
should
probably
use
an
async
every
file
that
has
all
the
features
all
right,
which
I
think
we
already
have,
which
is
the
dummy.
Is
this
dummy,
async,
API
file
and
from
there
you
can?
Probably
you
know,
generate
all
the
all
the
other
parts
of
the
of
the
spec
and
how
they
connect
with
each
other.
E
E
B
B
B
B
B
Ideally
it
could
be
Avro
whenever
whenever
that
tool
in
supports
it
right,
it
can
be
many
things
not
just
using
schema
right,
so
so
yeah.
This
cannot
be
validated
with
JSON
schema
and
that's
why
we
need
the
second
step
of
going
through
all
the
message,
payloads
and
understanding
which
schema
language.
This
is
written
on
and
applying
the
correct
schema
validator
to
this
message.
Payloads
and
also
actually
Lukas,
is
working
on
that
right
now
and
adding
additional
validations
like,
for
instance,
a
security
scheme.
B
So
there
are,
and-
and
there
are
others
like
validating
that
all
the
parameters
that
you
are
passing
on,
the
channel
name
are
actually
defined
and,
and
you
are
not
defining
any
other
names
or
you're,
not
missing
one
of
them.
This
is
not
being
validated
by
the
distant
schema
definition
yet,
but
as
you
can
see,
these
are
like
little
details
that
will
not
affect
any
diagram
generally
right,
so
yeah.
B
Necessarily
I
mean
this:
you
can
do
whatever
you
think,
it's
a
that's
suitable
for
you.
If
you
do
it
in
JavaScript,
you
get
the
JavaScript
parser
all
right
in
case.
You
need
it,
but
that
you
might
not
need
it.
You
might
only
need
the
JSON
schema
parser,
and
for
that
you
have
you.
Have
it
in
many
languages.