►
From YouTube: AsyncAPI SIG meeting 42 (February 16, 2021)
Description
This is the recording for the AsyncAPI Special Interest Group (SIG) meeting #42.
Attendees:
We had 11 guests, sorry but didn't have time to write down all names.
Agenda & Notes: https://github.com/asyncapi/asyncapi/issues/497
Chat:
00:15:19 Fran Méndez: https://hub.asyncapi.io
00:41:53 Fran Méndez: https://github.com/vadimdemedes/ink
00:50:46 Lukasz Gornicki: https://www.asyncapi.com/blog/january-2021-at-asyncapi
00:55:50 Fran Méndez: https://github.com/asyncapi/bindings/issues/40
00:55:57 Fran Méndez: https://github.com/asyncapi/bindings/issues/41
00:56:10 Fran Méndez: https://gist.github.com/dalelane/3931c17b14c51fa4a1cf25496237d188
00:56:38 Dale Lane: the link covers it
00:56:41 Dale Lane: thanks!
A
A
And
I'm
not
sure
even
how
to
start
so,
maybe
let's
I'm
gonna
start
as
usual,
so
we
have
few
new
people.
So
if
if
you
would
like
to
like
say
something
like
say,
hi
or
even
say
something
more
about,
you
feel
free
to
do
it
you're
not
obliged
to
do
it,
I'm
just
giving
you
a
space
to
do
it
so
and
I'm
not
gonna
pick
the
names
so
just
who's
first
and
then
that's
the
lucky
person.
B
D
Yeah,
I
guess
I
have
to
say
something
because
I
joined
yesterday-
the
async
api
awesome
team,
so
yeah
I'm
sergio
moya,
I'm
based
in
barcelona,
I'm
born
and
raised
here
and
basically
well
more
about
me.
I
have
a
daughter
that
is
turning
it.
It's
gonna
turn
too
soon.
She's
shouting
some
were
there.
So
if
you
hear
a
wonderful
boys,
they're
singing
and
so
on,
so
it's
it's
her.
So
I
have
two
cats
rosie
and
miguelito,
which
they
used
to
scratch
my
door
whenever
I'm
working
here.
So
everything
is
fine.
D
A
E
I
think
I'm
on
one
of
the
other
new
faces
here.
My
name
is
jorge
and
I'm
from
the
culinary
islands
and
I'm
here
because
I
was
on
our
team.
We
are
working
with
a
sink
api
specification
and
a
few
weeks
ago
it
was
a
little
bit
messy
to
work
with
the
playground,
because
the
errors
weren't
shown-
and
from
that
point
I
decided
to
do
a
client,
a
cla
by
my
own,
and
you
guys
mentioned
that
you
would
like
to
to
do
a
more
complex
or
more
with
more
features
cli.
A
A
G
A
If,
if
we're
done
with
introductions,
then
let's
let's
jump
into
the
topic
suggested
by
andre,
so
there's
a
lot
of
description
already
in
the
in
the
meeting
notes.
I
hope
you
had
a
chance
to
to
familiarize
with
it
but
andre,
I
think
you're,
the
best
person
to
like
yeah
feature
the
topic
you
want
to
discuss.
B
B
Has
a
good
design
so
so
they're
things
that
I'm
quite
passionate
about,
and
I
see
that
I
mean
you
could
say:
well
it's
subjective,
but
what's
out
there,
I
see
that
sync
api
is
designed
quite
nicely
like
the
playground
and
everything,
but
there's
a
lot
left
to
be
desired
in
the
api
space
in
terms
of
like
creating
excellent
user
experiences,
so
so
really
yeah
the
project
that
I'm
working
on.
I
want
to.
B
Use
the
sync
a
sync
api
and
integrate
it
into
as
a
integrate
into
the
project
as
a
core
part
of
it.
So
so
as
to
why
I'm
here,
I
I
suppose
it's
mostly
to
see
how
I
can
contribute
to
the
project
in
some
way
contribute
back
as
I
see
to
use
it
heavily
for
something
that
I'm
not
sure
of
of
its
success
but
I'll
find
out
sooner
or
later,
but
also
to
get
some
feedback
on
the
idea.
B
F
So
andre,
I
guess
I
shared
a
link
with
all
of
you
on
the
chat.
I
think
you
mean
something
like
this
like
we've
been
working,
something
like
this
in
the
past
with
stop
development,
so
I
will
open
source
this
soon
p.m.
Right
and
that's
probably
what
you
mean
right
like
it's
a
when
you
have
to
sign
up
to
see
it,
but
it's
not
possible
to
sign
up
anymore,
but
it
has
a
directory.
I
can
probably
share
my
screen.
I
think
it's
going
to
be
easier,
so
you
can
see
how
it
is.
F
F
Okay,
so
I
guess
you
can
see
it
right,
so
this
is
like
the
playground
that
we
have
so
far,
but
we
decided
to
go
a
little
bit
forward
a
little
bit
beyond
that
and
we
created
this
directory
that
is
based
on
an
organization's.
Basically
like
mostly
what
you
were
mentioning
about,
swagger
have
and
as
you
can
see,
you
have
you
know
things
organized
by
organization
by
project
pretty
much
like
like
stronger
have
right
and
then
you
can
create
new
projects
in
your
organizations,
mobile,
using
kpa
files
and
and
yeah.
F
B
Yeah,
it's
yeah
yeah.
It's
definitely
like
the
basis
of
this
building,
but
my
goal
is
really
to
sort
of
take
it
further,
with
sort
of
real-time
collaboration,
features
sort
of
looking
into
how
it
can
integrate
with
your
real
server,
your
real
implementations
and
sort
of
catch,
versioning
issues
and
sort
of
give
you
hints
and
sort
of
integrate
nicely
with
like
the
workflows
and
things
like
that.
F
That
was
really
the
the
basic
version
of
the
what
you're
mentioning
right
like
we
were
thinking
and
going
in
this
direction
as
well,
and
we
stopped
like
for
now
or
not
stopped
that
we
we
positive-
it's
not
a
priority
for
us
right
now,
but
but
yeah
like
definitely
interested
one
of
the
things
that
I
will
have
to
do
myself,
because
this
is
private
in
my
github
account
still,
I
need
to
have
fun.
I
need
to
find
time
and
open
source
it
appropriately
and
yeah
and
share
with
the
community.
F
So
probably
you
can
continue
the
work
from
here
this.
This
is
open
source.
This
is
gonna,
be
open
source
right
and
we
wanted
to
continue
being
open
source,
not
sure
if
you
want
to
develop
this
in
the
open
source
or
as
a
proprietary
solution.
That's
up
to
you,
of
course,
but
but
yeah
like
most.
Probably,
I
think
most
probably
we
will
get
back
to
this
at
some
point
like
this
year
or
early
next
year
like
to
have
like
a
we
call.
F
The
testing
kpi
have,
but
it's
most
probably
going
to
be
renamed
to
a
think
api
studio,
something
similar
because
we
want
people
to
create
visually,
create
apis,
not
just
async
api
files,
but
visually
create
apis,
any
kind
of
apis,
not
just
even
driven
or
asynchronous
apis,
and
to
be
possible
for
you
to
manually,
create
them
right
and
to
see
how
are
they
interconnected,
like
this?
One
is
balanced
into
this
channel,
but
this
in
this
other
three
are
subscribing
to
the
same
channel.
F
F
If
we
want
people
to
be
able
to
more,
let's
say
easily
create
it's
increasing
guys
right
that
we're
asking
ebay
files
in
this
case,
because
if
we,
if
we
just
give
people
the
the
code
based
approach,
let's
say
like
like
the
left
side
of
the
screen
that
I
was
sharing
right
like
like
in
the
playground,
then
you
have
to
type.
I
think
you
pay
by
hand
and
it's
super.
F
H
F
F
H
F
F
F
This
will
find
it,
but
it's
usually
faster
than
typing.
All
of
that
yourself
by
hand
right
so
yeah.
It's
usually
it's
actually
useful,
but
yeah
be
careful
with
that
with
the
data,
because
one
of
the
reasons
I
wanted
to
have
async
api
after
documentation
after
we
realized
that
the
conclusion
is
like
okay,
this
is
a
a
use
case.
F
F
Which
was
good
like,
like
I
would
say,
maybe
it's
a
good
way
to
capture
an
initial
document,
and
then
you
review
it
and
yeah,
but
yeah.
I
guess
this
is
like
the
we're
always
trying
to
evangelize,
let's
say
for
the
design
first
approach,
always
as
weak
as
much
as
we
can
right.
We
know
the
code
first
and
in
this
case
data
first
I
just
I'm
just
inviting
inventing
this
work.
F
H
It's
one
of
our
hub
codes,
so
it'll
all
be.
It
is
all
open
and
all
planned
to
be
open.
Okay,
so,
like
it
came
out,
we
have
a
series
of
open
source
and
gestures
now
which
basically
take
async
api
files
and
then
just
ingest,
mqtt
or
other
things,
and
then
turn
them
in
and
then
spit
out
and,
like
sync,
api
verified
a
code
at
the
other
end,
which
is
also
like
amputee
as
well,
because
it
supports
both.
H
But
like
the
idea
was
this
one
was
exactly
because
we
often
ended
up
taking
open
api
specs
in
to
turn
them
async
and
because
we'd
then
have
this
pole
loop
inside
and
it
would
pull
out
data.
It
would
then
become
of
that
data
how
to
generate
an
open
api,
an
async
api
spec,
there's
too
many
words
or
something
an
async
spec
from
an
open
spec.
But
we
wanted
to
guarantee
that
there
was
actually
data
and
to
make
a
spec,
which
was
immediately
testable.
So
it
was
effectively.
H
The
same
thing
because,
like
this
whole
data
exploration
problem,
is
actually
just
the
critical
problem
with
that
it
probably
always
run
into
with
this
kind
of
data
in
motion
thing.
Is
that
because
it's
now
there's
no
static
point,
you
can't
just
go
query
and
hope
right
you,
it's
very
hard
to
actually
explore
the
data
and
it
suddenly
becomes
a
real
problem,
particularly
any
of
these
like
tools
which
kind
of
host
up
all
these
apis.
It's.
What
is
that?
What
what?
Actually?
What
does
this
api
even
do?
H
F
Or
even
testing
it,
so
I'm
just
I'm
just
curious
because
I
think
so
this
is
actually
related
to
what
I
was
talking
about,
like
the
visualization
of
relationship
between
exactly
yeah.
That's
why
it's
like,
but
yeah
that
I
mean
I
didn't
want
to
hijack
your
time,
andre!
So
sorry
for
that.
Maybe
you
wanted
to.
F
H
It's
on
the
it's
purely
a
time
matter.
It
is
literally
on
the
roadmap
to
the
open
source.
Okay,
like
everything
like
we
do,
async
base
will
be
open,
so
there's
now
a
get
or
called
ably
labs
where
everything
we
have
async
is
based
there
anyway,
awesome
and
all
our
open
source
stuff
just
lives
there
by
default
now,
so
we
just
keep
dumping
things
out
there.
The
main
problem,
two
big
blockers,
are
convincing.
Some
people
actually
write
the
article
to
go
with.
It
is
actually
one
of.
F
H
F
H
H
H
F
H
H
I
F
G
Yay
yeah,
I
think,
there's
some
some
having
had
a
quick
look
at
your
data
streams,
but
obviously
not
ready
to
integrate
kafka.
Yet
at
our
side
and
there's
a
bunch
of
cool
stuff
there,
and
I
would
love
to
see
those
examples
in
the
kind
of
async
api
stories
and
the
stuff
that
we're
creating.
I
think
there's
a
lot
of
kind
of
joined
up
thinking
in
in
in
the
room
as
it
were.
H
Yeah,
but
that's
exactly
at
cause
like
the
whole
idea
of
having
the
specs
on
there.
Was
everyone
just
test
this
stuff
with
it,
because
we
think
the
specs
are
important,
possibly
more
than
the
data
itself
right
now,
but
also
like.
If
you
have
data
you
want
to
put
up
so
it
can
be
hosted
for
free
but
we'll
we'll
pay
the
hosting
and
like
the
pr
and
the
transportation
costs
for
it.
As
long
as
we
can
put
specs
against
it
and
have
it
there.
F
F
This
is
going
to
be
amazing,
because
the
idea
is
to
have
like,
like
a
proxy
think
about
this,
like
like
nginx
or
something
like
this,
but
for
messaging
protocols,
not
for
http
right
and
it
will
be
able
to
to
capture,
for
instance,
kafka
or
mkttt,
to
be
able
to
understand
that
the
tcp
stream
that
it's
receiving
it's
a
kafka
message.
It's
actually
a
kafka
message
and
parse
it
and
get
the
the
content
and
then
validate
it
against
the
the.
I
think,
api
definition
and
then
let
it
pass
or
not
depending
on.
F
F
Is
to
validate
it
sounds
like
a
gateway.
I
don't
want
to
call
it
gateway
because
yeah
I
don't
know,
because
gateways
are
usually
that,
for
I
mean
for
http,
the
gateways
are
also
aggregators.
Somehow
you
know,
like
you,
make
a
request
and
then
it
makes
three
other
requests
to
other
three
apis
aggregate
the
result,
and
then
you
put
it
back
in
the
response
right.
F
So
that's
also
that's
something
that
gateways
do,
and
so
that's
why
I'm
calling
it
proxy
like
it's
just
a
like
literally
approximately
it
does
nothing
to
the
message
at
least
for
now
right.
It
does
nothing
to
the
message.
Just
let
it
pass
or
not
right
or
or
let
it
pass,
but
it
triggers
an
alarm
somewhere
make
a
dog
new,
relic
or
slack
or
whatever
right.
So
so
yeah,
that's
the
the
whole
idea,
and,
and
ideally
it
will
be,
we
should
be
able
to
deploy.
F
So
it's
gonna
be
also
api.
First,
most
probably
it's
not
gonna
be
so
it's
gonna.
That's
not
gonna.
Have
it's
not
going
to
have
a
ui?
It's
just
going
to
be
an
api
for
you
to
interact
with
it.
So
there's
no.
I
mean
unless
someone
wants
to
jump
in
and
create
a
basic
ui,
that's
fine,
but
yeah.
The
idea
is
that
then,
for
instance,
ably
could
be
using
it
to
buy.
H
H
Access
so
then
for
egress
with
messages
going
out
of
this
system.
It's
suddenly
like
hey.
I
now
need
to
egress
all
this
stuff
to
you
know
10
000
subscribers
rather
than
20.,
and
you
don't
have
to
deal
with
a
simple
fact
of
the
inevitable
scaling
socket.
I
o
type
problem
when
you
end
up
having
hundreds
and
hundreds
and
hundreds
of
servers
managing
your
front,
end
presence
points,
but
even
in
the
other
way,
I'd
love
to
have
it
and
receive
daily
messages.
H
F
F
H
F
F
F
F
A
A
So
the
idea
we
had
with
the
cli
is
that,
like
basically
people
of
I
mean,
let's,
let's
make
it
like
a
shallow
reasoning.
Maybe
that's
a
good
word
in
in
english,
so
basically
want
to
have
cli,
because
people
love
cli
and
they
are
cool.
So
we
need
to
have
one,
but
it's
not
the
only
reason.
Of
course
cli
start
useful
for
automation,
but
basically
we
would
like
to
have
a
single
cli.
A
A
So
that's
what
we
meant
when
we,
when
you
showed
the
diwali
validator
validation,
cli,
that
we
would
like
to
have
a
something
single,
there's,
no
repo
for
it,
yet
no
design.
Even
we
only
know
that
we
I
mean,
you
probably
noticed
that
we
are
pretty
in
favor
with
react,
because
we
have
like
the
next
js
is
used
for
the
website.
Then
the
generator
render
engine
new
render
engine
is
react.
Then
the
code
generate
the
the
model
generation
is
based
on
react,
and
we
of
course
know
that.
A
A
So
that's
the
foundation,
and
now
it
also
depends
on
you
how,
when
you
wanted
to
jump
and
help
out
here,
because
we
also
have
other
priorities
and
not
sure
how
much
we
should
rush
here
and
and
kick
off
with
some
design
dogs,
or
maybe
you
would
like
to
do
it
and
jump
in
and
create
some
dock
under
asking
api,
where
we
will
already
start
drafting
and
and
working
on
something.
So
what
were
your
thoughts.
E
A
So
we're,
I
think,
we're
pretty
flexible
again
so
again,
because
we
want
to
to
make
everything
we
work
on
a
work
of
community,
not
just
a
few
lots
from
postman
that
are
pushing
forward.
So
if,
if
you
already
have
some
experience
there
and
would
like
to
start
scratching
something
some
doc,
just
let
us
know
think
it
through.
A
A
F
F
Yeah,
like
we
can
start
iterating
on
the
issue
or
something
like
I
mean
whatever,
whatever
works,
we
like,
he
said
like
lucas,
said
we're
pretty
flexible
and
it
would
be
great
to
see
more
community
members
taking
the
lead
on
on
the
tools
or
on
parts
of
the
spec
or
like,
for
instance,
said
dale
who's
here
today
on
the
call
they'll
decide
to
take
the
lead
a
little
bit
on
the
on
the
kafka
binding
for
the
spec.
So
I
think
this
is
great
like
this.
F
F
Also
because
of
the
reason
luka
says
like
we
don't
want
this
to
be
a
a
the
possible
false,
false
game
right
where
all
of
everything
is
managed
by
ourselves,
of
course,
we're
working
on
this
full-time,
so
you
can
expect
us
to
to
do
more
stuff,
but
yeah
I
mean
I
mean
that's
it.
It
should
be
a
community
work
right,
it
should
be
a
community
effort
and
when
we
say
effort
is
not
that
we
we
decide
a
new
work.
F
Actually,
yes,
we
work.
We
are
the
only
ones
working
hard
here,
full
time
so
yeah
so
yeah.
It's
like
we
want
it
to
be
a
little
bit
more
like
hey,
so
people
take
the
leadership
on
areas
of
the
project
can
be
a
tool
can
be
a
feature
it
can
be.
It
can
be
a
feature
of
the
spec
I
don't
know
like
and
when
I
say
taking,
the
leadership
doesn't
have
to
be
like
you
have
to
be
there
forever
being
the
leader
and
taking
responsibility.
F
No,
it
can
be
just
temporarily
like
just
want
this
to
make
it.
You
just
want
to
make
it
happen
like
having
a
cli
and
then
after
it's
done,
you
may
be
okay.
I
don't
care
about
anything
api
anymore,
that's
fine.
At
least
you
did
something
during
some
time
and
that's
great
right.
So
I
mean
we.
We
hope
you
stay
forced,
but
but
yeah
it's
like
it
doesn't
have
to
right.
G
A
F
Then
you
start
creating
issues
right
for
for
each
of
the
points
or
implementations
that
need
to
be
done,
and
then
maybe
you
find
out
that
you're,
not
the
only
one
there's
in
this
and
someone
jumps
in
and
help
you
implement
the
other
features,
while
you're
working
on
some
of
them
and
yeah.
That's,
hopefully
what
this
will
happen.
A
Possible,
okay,
awesome:
I
think
we
can,
after
the
call
created
the
cli
repo,
as
we
said,
and
then
just
whenever
you
have
time
create
a
a
first
issue
where
you
describe
like
foundation
and
by
design.
We
don't
think
like
design
document
that
it's
because
sometimes
design
document
sounds
like
it's
pretty
scary,
but
it
doesn't
have
to
be
like
full
architecture
design
with,
like
all
edge
cases,
whatever
future
look
into
the
future,
it's
more
just
a
a
foundation.
A
F
Yeah,
I
think
graphql
calls
it
the
stroman
proposal.
I
think
strowman
proposal,
which
is
like
you
just
dump
your
thoughts
there
and
see
what
happens
right
and
then
from
there
we
iterate
and
make
even
the
design
will
be
iterated
iterative
right.
So
it
will
become
better
over
time
and
then
at
some
point
it's
just
a
matter
of
okay.
Let's
just
jump
into
the
implementation
right,
so
yeah.
A
A
A
Increases
okay,
so
the
also,
as
mentioned
in
the
in
the
status
update
last
few
meetings.
We
were
always
talking
about
this
open
governance
and
and
foundation,
so
just
an
update
from
from
our
side
that
we
are
really
actively
working
on
it.
So
it's
like
me
and
fran
we're
meeting
regularly
and
and
thinking
about
it.
A
It's
just
the
thing
that
we
we
are
ambitious,
like
with
other
topics
at
the
same
api,
and
we
don't
want
to
just
copy
templates
from
others
and
and
apply,
but
we
really
want
to
design
a
charter
where
we
have
a
kind
of
democracy
and
really
whoever
contributes
have,
as
has
a
vote
and
and
it's
just
harder,
because
we
try
to
write
it
in
the
lawyer's
language
which
is
not
fun.
I
mean
france
says
it's
fun,
I'm
I'm
super
honest
here.
That's
not
fun
at
all,
but.
G
F
I
would
say
so
yeah,
it's
actually.
I
mean
it's
true
for
me,
like
it's
kind
of
fun.
Of
course
it's
it's
like
studying
right
like
when
you
have
to
study
a
lot
and
then
it's
like
in
the
beginning.
It's
like
girl
and
I
have
to
sit
down
and
study
and
then
once
you're
studying
it's
like.
Oh,
this
is
actually
you.
F
F
You
can
get
crazy
with
all
these
details,
trying
to
be
as
precise
as
possible
trying
to
avoid
the
problem
of
using
they.
You
know
like
pronouns
as
a
subject
where
it
might
not
be
clear
who's.
They
or
you
know
it's
like,
even
though
it's
pretty
clear
when
you're
in
it,
but
it's
like
yeah,
let's
not
give
any
chance
to
doubts
here,
right,
so
misinterpretation,
so
so
yeah,
it's
fun,
it's
fun
and
we're
kind
of
mixing.
I
mean
not
the
language
but
we're
kind
of
mixing.
F
C
A
A
B
A
J
G
Me
please
please
be
pleased.
I
have
some
kafka.
I
don't
really.
I've
done
a
little
bit
of
async
api
with
mqtt.
I
do
a
lot
of
other
things
as
well,
but
I'm
super
interested
in
in
this
and
because
I'm
working
a
lot
with
kafka
over
time,
I
will
be
moving
this
forward.
So
I'd
love
to
read
what
you
have
dale
and
maybe
scale
myself
up
to
the
point
where
I
can
at
least
review,
if
not
collaborate.
J
J
A
K
F
Yes,
I
I
picture
some
links
in
the
chat,
so
the
two,
the
two
the
first
two
are:
you
know
the
issues
that
are
already
existing
in
the
violence
repository
and
the
third
one.
The
gist
is
a
dale
established
jesus
on
different
cases
to
cover
around
different
scenarios
where
kafka
bindings
will
be
helpful
and
could
be
helpful
but
yeah
only
if
we
change
it
only
if
we
evolve
it
first.