►
Description
This talk was part of AsyncAPI Online Conference:
- AsyncAPI Initiative website - https://www.asyncapi.com/
- You can also watch this talk as part of full conference recording with audience questions in the LiveChat - https://youtu.be/oMSzGc5bDr4?t=21147
TALK ABSTRACT
In this talk, Fran will tell us about the early days of AsyncAPI, how it all started, and will also offer his insights and plans for the near future. Exciting announcements ahead, don't miss it!
SLIDES
https://speakerdeck.com/fmvilas/past-present-and-future-of-asyncapi
A
A
We
just
got
crazy
and
said
like
we
have
to
organize
this
and
make
it
happen.
So
here
we
are,
and
thanks
for
for
joining
us
today,
I'd
like
to
introduce
a
little
bit
to
those
who
are
not
very
aware
of
the
past
of
async
API,
where
it's
coming
from
right,
not
just
what
we're
doing
or
what
we're
gonna
do,
but
understanding
the
past
is
also
it's
also
nice
right.
A
So
yes,
as
I
said,
my
name
is
from
Mendez
and
you
can
follow
me
on
Twitter
and
or
just
send
me
an
email
if
you
have
any
requests.
That's
my
beautiful
me
when
I
was
still
beautiful
and
had
some
hair
got
crying
and
and
yeah.
So
let
me
go
a
little
bit
back
in
time
and
explain
where
is
it
coming
where
I
think
it
is
coming
from
right?
So,
a
few
years
ago
I
think
it
was
to
2017.
I
was
working
at
a
company
with
a
friend
of
mine,
Bruno
Peter.
A
We
were
working
at
a
company
called
he
or
it's
also
known
as
API
change
love.
You
know
that
was
the
name
of
the
company
and
the
feature
said
we
were
an
API
chase,
lock
school
that
evolved
over
time
into
a
full
API
documentation
and
API
support
product,
and
that
was
actually
it's
super
cool
to
build
that.
A
But
to
the
point
today
is
that,
as
you
can
imagine,
building
a
chain
lock
itself,
the
chase
lock
is
that
it
says
system
and
event
in
an
invented
system
right.
So
it
consists
of
different
events
like
an
endpoint
has
been
created
or
something
has
been
changed
sides.
It's
always
talking
about
events,
so
our
architecture
as
well
was
consistent
on
event-driven
architecture.
At
the
time
we
were
using,
but
thank
you
and
if
you
go
back
to
version
1
of
async
API,
you
will
notice
that
there
was
a
strong
bias
towards
mqp
c19
1.
This.
A
You
know
the
protocol
power
in
problem
queue
and
and
yeah
it
was
like
it
was
enough
for
a
sprite
to
do
the
job
for
us,
so
so
yeah
the
cool
thing
about
the
cool
thing
about
working
at
each
and
with
a
friend
of
mine
and
working
on
this.
This
architecture
was
that
an
architecture
and
the
kind
of
product
was
that
we
were
building
a
product
on
top
of
open
API
right
for
those
who
don't
know,
swagger
swagger
specification
or
open
a
gate
specification,
and
we
were
call
it
like
that.
A
If
you
want,
we
were
kind
of
experts
on
open,
API
and
and
swagger.
So
we
were
very
used
to
automate
lots
of
things
like
creating
documentation,
generating
code,
bootstrapping
child
for
your
services
or
NPI's.
So
we
were
very
used
to
that
tooling
right
and
to
the
to
that
ecosystem,
and
suddenly
we
got
did
we
get
the
the
the
beauty
of
creating
an
event-driven
architecture?
And
there
was
nothing
similar,
it
was
like
I
can't
believe,
I
think.
A
The
third
time
I
was
copying
and
pasting
the
code
from
one
place
to
another
and
modifying
a
few
things
and
and
uploading
the
documentation
I
said
really
and
get
a
creeper
and
trying
to
have
the
documentation
reflect
what
actually
was
in
the
killed,
the
mom
and
I
I.
Faced
that
it
was
like
we
should
be
able
to
making
this
like
we'd,
open,
API
right
and
with
rested
guys
so
so
yeah.
We
we
started
drafting
this
crazy
idea
of.
A
The
opening,
a
spec
which
has
a
lot
of
things,
people
don't
know
and
really
cool
things.
I
I
still
recommend
people
go
to
open,
API
and
have
a
look
at
it,
and-
and
the
second
thing
is
that
I
managed
to
abstract
the
design
of
this,
or
at
least
I
try
the
design
of
the
spec
to
sweet,
not
just
my
a
kewpie
services,
but
also
some
entity
services
and
try
to
do
something
that
could
be
useful
for
everyone
right
and
back
I
said,
even
though
it
was.
A
It
was
obvious
that
the
world
is
strong,
biased
towards
nqb,
at
least
it's
right
there,
so
that
was
a
fun
fun
work
as
and
I
just
Pamela's
it
it
and-
and
we
decide
to
go
at
each
and
and
promote
it
right.
So
at
each
we
had
something
called
a
PHS,
and
here
you
can
see
we
a
younger
version
of
myself,
together
with
my
friend
brother
Pedro,
who
actually
inspired
a
lot
of
the
things,
including
the
main
main
c
KP
a
so
so
yeah.
We
presented
this
APH
at
one
day.
A
I,
actually
don't
remember
the
date,
but
it
was
like
around
three
years
ago
and
interviews
days
in
KPI.
So
that's
a
pretty
much
like.
Where
is
it
coming
from
I
hope
you
enjoyed
the
let's
say
the
origins
of
facing
KPI
there's
a
lot
of
more
story
behind
it,
like
I,
just
tried
to
summarize
a
lot
and
but
I
think
it's.
It's
always
cool
to
get
back
and
remember
that
the
finest
stories
the
deal
starts
right.
A
A
Like
to
go
from
past
to
present
and
then
go
to
future
and
explain
what
are
the
plans
for
the
AC
keep
a
mishit,
if
not
just
a
spec,
and
so
today,
I
like
to
say
that
regarding
the
spec
nowadays
I
like
to
remark
that
recently
we
launched
at
version
2
of
the
spec.
Some
of
you
may
already
know
about
it,
specially
there,
the
great
community
that
we
built
around
this
in
KPI
for
sure
you
know
about
it,
but
I'm,
assuming
that
there
are
lots
of
new
people.
A
So
when
we
launched
it
the
version
2
and
started
building
a
lot
of
tooling
and
when
I
say
a
lot
of
tooling
is
a
lot
of
tooling
and
we
set
it
building
code,
generators,
documentation,
generators,
JavaScript,
parser,
async,
API
converters,
so
converters
from
version
one
to
version
two.
So
you
don't
have
to
migrate
them
manually,
lots
of
stuff,
even
the
playground
that
you
can
play
with
right
and
the
cool
thing
is
that
this.
This
tooling
is
maturing
slowly.
A
A
It's
it's
amazing
to
see
that
the
support
that
that
we're
having
lately,
especially
it's
growing
like
Wow
like
hell,
so
it's
it's
amenable
sometimes,
but
we're
very
glad
of
it
right
and
and
yes,
l.
So
that's
pretty
much
where
we
are
now.
We
are
on
version
version
2
of
the
spec
and
we
are
building
tooling
for
to
support
versions
of
the
spec
and
trying
to
make
it
stable.
A
Let
me
share
the
link
to
the
to
the
world
map
where
we
have
everything
described.
What's
the
roadmap
for
2020
right?
That's
again,
that's
a
salary!
Let's
let
me
summarize
this
I
want
to
start
with
the
biggest
for
me
and
to
list.
In
my
opinion,
this
is
the
biggest
change
in
the
whole
initiative.
So
those
who
have
been
around
for
some
time
know
that
this
has
been
my
side
project
for
some
time.
It's
been
growing
until
it
got
out
of
hand
and
I'm
trying
to
make
this.
A
As
less
friend
centric
as
possible,
so
this
year,
we're
committed
to
at
least
try
if
they
want,
of
course,
join
a
new
neutral
home.
So
what
does
it
mean?
We're
gonna
splurge
in
ciencia
for
open
API
initiative
or
Linux
Foundation
or
other
kind
of
foundations.
So
the
project
is
not
my
stuff,
my
personal
stuff,
anymore
right.
It
is
not
anymore,
but
at
least
legally
speaking,
it's
not
my
stuff
anymore
right.
A
So
we
can
build
a
healthier
community
around
them
and
not
only
about
people,
but
companies
around
them
make
it
make
it
grow
so
that
that
that
point
is
actually
part
of
a
bigger
goal
that
that's
what
we
call
it
of
trying
to
make
a
sink
API
the
the
standard
specification
for
event-driven
architecture.
We
want
to
become
the
standard
for
that,
not
the
only
standard.
Of
course
there
are
others.
A
Other
cool
standards
like
like
cloud
events,
for
instance,
who
are
doing
a
great
job
but
I,
think
we
can
work
together
and
offer
a
better
or
a
bigger
solution
in
terms
of
scope.
Right
I
have
my
two
cats
here
around
something
you
hear
them
so
yeah.
It
was
was
saying
that
that's
that's
one
of
the
biggest
goals.
A
Let
me
jump
into
the
next
one,
so
tolling
tolling
is
always
a
priority
for
us,
especially
lately
that
we
have
stable
or
or
or
a
version
of
the
spec
that
we're
happy
with,
which
is
the
procedure
and
tolling
again
needs
to
be
mature,
so
we're
now
building
a
lot
of
calculators
and
and
a
lot
of
documentation,
generators
for
sure
this
is
something
that
needs
to
need
to
improve
and
over
time
as
well
right.
So
what
we
want
to
do
here
is
make
JavaScript
parser
and
generator
stable,
so
people
can
build
on
top
of
that.
A
So
that's
a
top
priority
for
us
as
well.
Also
during
this
year
we
want
to
release
version
2.1
2.1
of
this
bag.
We
might
launch.
We
might
release
also
that
2.0.1,
it's
a
fix
or
a
patched
version,
fixing
some
things
here
and
there
just
which
changes
nothing.
It's
just
a
text
like
type
wasn't
all
this
time,
but
at
least
at
the
end
of
by
the
end
of
the
year,
we'll
be
releasing
the
new
version
of
the
spec.
Would
still
we
don't
know.
A
What's
what's
gonna
contain
exactly
we
have
some
candidates
and
we
will
be
deciding
to
together
with
the
community.
What's
gonna
be
included
there,
so
IT
support
wheels.
Work
on
you
know,
I
mean
the
parameters
we'll
work
on
on
our
favorite,
another
favorite
code
editor,
and
we
would
like
to
work
or
not
abandon
our
editor
to
work
with
async
API
and
to
have
features
like
auto
completion
and
LinkedIn
like,
for
instance,
like
the
tool
that
the
folks
at
stoplight
are
building
so
they're
building
a
don't
know
how
they
call
it
a
spectral.
A
A
A
That's
documentation
is
actually
has
always
been
my
passion
as
well:
I,
I,
assume
and
I
recognized
that
I
didn't
have
enough
time
or
I
didn't
put
enough
love
on
the
current
documentation.
Even
that
was
not
that
bad,
but
we
need
to.
We
need
to
do
better.
If
we
want
people
to
adopt
async
API,
we
need
to
be
building
tutorials,
better
guides
online
courses.
Webinars
we
like
all
kind
of
of
documentation,
even
the
reference
itself
needs
to
be
better
examples.
Like
lots
of
examples.
A
We
are
gonna,
be
targeting
distance
here
and
if
we
are
and
if
we
manage
to
do
it
well,
like
we're
thinking
like
it's
in
our
heads,
this
must
be
a
really
nice
experience
and
a
really
pleasant
experience
to
start
getting
started
with
async
API
and
getting
back
to
speed,
and
until
you
have
something
so
this
is
also
one
of
our
practice
for
this
year
and
last
but
not
least,
is
team
tooling,
what
do
I
mean
by
Tim
tooling?
So
so
far
we've
been
seeing
all
the
generator.
A
You
know
the
condition
right:
the
code
generator,
that's
cool
for
solo
developers
like
you
can
do
stuff,
and
maybe
you
share
it
via
other
mediums,
but
it's
only
for
you,
so
we
would
like
to
create
something.
That's
for
the
teams
for
teams
to
work
with
this
in
KPI,
because
in
the
end
depends
with
architectures,
are
distributed
architectures
and
most
probably,
is
a
distributed
team
who's
managing
their.
So
so
yeah
not
entertaining
more.
A
We
did
it
so
we
did
it
just
to
make
it
clear,
as
as
always
and
following
our
our
passing
for
openers
I
think
API
have
is
gonna,
be
up
in
sirs
as
well.
It's
not
yet
public
we're
gonna
open
source,
it
probably
around
next
month
or
so
next
week
or
in
two
weeks,
so
yeah
stay
tuned
and
let
me
start
with
a
little
bit
of
demo.
Let
me
change
the
screen
that
I'm
sharing.
A
Cool,
so
here's
an
example
of
the
current
the
current
have
basic
API.
Have
you
can
find
it
on
the
async
API?
Also
following
the
signature
that
we
were
using
for
the
playground
and
as
you
can
see
here,
it
looks
pretty
much
like
the
playground,
but
it
has
immense
enhanced
capabilities
like,
for
instance,
instant
elimination
here.
So
whenever
you
use
something
that
you
don't
or
you
mistyped
something
you
do
something
that
it's
not
I,
think
API
valid.
It
tells
you
the
error
here
right
into
the
into
the
editor.
A
A
So
one
of
the
things
that
also
allows
you
to
do
this
is
we
have
a
button
here
that
says
save
what
is
it
going
right,
where's
this
safe
one?
So
let
me
first
show
you
this
step
here
directory.
So
we
have
the
concept
here
of
organization
project
and
async.
Api
is
five
I.
Think
you
get
files
right.
So
the
thing
here
is
that
I
didn't
create
anything
in
advance,
so
you
can
seal
the
whole
process.
I'm
gonna
create
a
new
project
and
my
organization
is
called
smarty
lighting.
A
If,
for
those
who
have
seen
my
example
with
with
streetlights,
this
is
the
name
of
the
fictional
or
the
fake,
the
fake
company.
So
let
me
create
the
name
of
the
project.
Streetlights
create,
and
it
says,
there's
no,
it's
in
kpi's
to
show
yet
we're
filtering
by
street
lights
here
and
there's
nothing.
So
that's
great
more
that's
great,
and
it's
in
KPI
on
the
street
lights
project
and
I'm
gonna
call
this
strip
lights,
API!
Okay,
so
you
create
a
street
lights
API
and
it
goes
straight
back
to
the
editor.
A
But
this
time
you
can
see
that
path
here.
That
program
will
straight
with
the
street
like
API,
open
I
have
something
here
to
share
as
well,
which
is
the
content
of
the
straight
line
API,
as
you
can
see
this,
this
trick
this
API
here
this
async
API
five
here
is
not
the
example
street,
like
the
street,
like
example.
So
let
me
import
one
file
from
our
examples
on
the
repo
I'll
take
it
everywhere,
and
today
we
got
the
async
API
they
strictly
suite
likes
API.
A
Let
me
save
it
so
Cole
says
damn
cool
fail.
You
can
do
as
with
as
with
the
playground,
you
can
always
download
these
HTML
talks
on
the
right
side
and
or
you
can
download
test
mark
down.
We
will
add
more
stuff
here,
like
code,
generators
and
stuff,
and
the
cool
thing
here
is
that
you
can
see
now
on
your
director
that
you
have
a
strict
like
API.
A
So
that
means
that
you
can.
You
can
use
this.
You
can
use
this
platform
this
product
to
be
to
store
your
async
API
files.
If
you
play
with
and
you
can
typically
R,
you
will
see
that
your
organization
has
members
and
in
in
my
case,
I
invited
ever
to
join
my
organization,
so
Emma
will
also,
if
ever
joins
the
the
project
it
is
in
KPI
have
C
will
be
able
to
see
my
the
street
like
API,
that
I
just
created,
so
we
can
collaborate.
A
Both
of
us
can
collaborate
on
that
and
also
you
can
send
invitations
to
other
people.
So
that's
pretty
much
the
the
demo
for
that's
pretty
much.
The
different
work
for
the
for
the
missing
KP
I
have
today
I
hope
that
you
are
as
excited
as
I
am
for
for
this
new
addition
to
the
today's
in
KPI
tooling.
That's
what
I
like
to
call
it
right
and
and
I
think
that's
it.