►
Description
APIdays Barcelona 2019
Async API for Event Driven Architecture
Ana Borges, API Specialist @ Sensedia
Speakers slides from the conference:
https://www.slideshare.net/APIdays_official
Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io/
Explore the API ecosystem with the API Landscape:
https://www.apiscene.io/api-landscape/
Deep dive into the API industry with our reports:
https://www.apidays.co/industry-reports
Subscribe to our global newsletter:
https://apidays.typeform.com/to/i1MPEW
A
This
is
the
topic
of
the
lecture
e
issues
about
events,
even
geometry,
I
think
API
at
a
common,
more
and
more
popular.
But
why
now
and
is
always
thought
about.
First
of
all,
this
is
me
I
am
an
Abarth
is
I'm
from
Brazil.
So
please
start
from
English.
I
am
API
specialist
at
Cynthia
and
I
am
a
cat
person
no
I'm
asking.
But
this
is
my
babies,
and
this
is
my
social
media.
How
about
polish
Michaela
I'm
two
persons
and
do
you
know
about
Cynthia
anyone's
heat
nose
in
Cydia.
A
So
Cynthia
is
important.
It
do
is
about
API.
We
offering
a
product.
Api
management
only
offers
also
consulting
services
for
help
our
customer
to
quit
your
digital
experience,
II
and
all
the
stuffs
we
have
presence
in
he
in
European
Latin.
We
have
more
than
100
customers
and
we
host
one
of
the
largest
events
about
API
on
the
world.
They
appeals
API
X
and
we
have
a
recognition
from
the
market
too.
A
So
why
this
all
coming
back.
Events
is
not
a
new
thing
since
I
have
come
from
college.
I
know
about
that
I
hear
about
that,
but
wise
coming
back
right
now.
Now
we
have
a
lot
of
things
with
IOT
streaming
and
this
stuff.
So
with
business
events,
we
can
receive
it
as
information
more
fast
and
analyze
it
with
more
difícil.
A
So
what's
the
venturi
market
a
three
evenings,
even
every
action
that
generates
a
systemic
change,
so
I'm
moving
here
on
this
the
stage
is
a
I
event,
but
when
we
work
with
kita
tree
even
through
a
tree,
we
don't
want
to
know
everything.
We
all
know
what
is
important
for
our
business.
So
we
have
that
business
event.
Are
the
events
they
have
significant
for
us?
A
It's
like
you're
done
for
a
customer,
a
product
change
in
a
bank
payments,
for
example,
so
EDA
even
terrific
d'etre
is
about
producing
the
tech
thing
in
reacting
to
these
events.
So,
like
you
already
that
we
have
is
some
topology
right.
This
is
the
topology
of
event.
We
market
a
tree.
We
have
C,
we
have
the
event
generator.
They
are
responsible
for
make
the
events
st.
the
events
for
someone.
It's
like
a
customer
service
e.
We
can
make
st.
some
events
about
changes
of
the
customer
data
is
like
it.
They
change
the
address.
A
This
is
the
others.
We
have
the
even
consumers.
They
are
the
stakeholders
of
the
events.
In
issuing
scenario,
we
can
say
that
quotation
selves
in
stakeholder,
because
if
the
customer
change
the
address,
we
need
to
recalculate
the
insurance
rate,
because
they
can
make
change
on
the
value
and
we
have
mediator
or
broker.
They
are
responsible
for
receiving
the
event
from
the
generators
and
st.
the
events
from
the
consumers.
He
we
have
both
way
from
the
setter
and
because
they
we
can
do
pull
in
or
push
in
the
event
mediator
or
broke
all
the
paints.
A
How
you
want
to
implement
this
okay,
so
when
use
one
or
when
use
another,
when
I
you
use
mediator
and
when
I
you
use
broken,
let's
see
a
little
more.
This
is
the
mediator.
The
mediator
is
when
we
need
to
do
some
Arco
station
on
on
our
events
right.
It's
like
I
need
to
check
if
something's
happens
in
one
processor,
if
it
does,
I
need
use
something
else,
so
we
have
four
main
components
in
this
topology.
We
have
the
event
queuing.
We
have
the
event
mediator
the
changes
in
the
processor.
A
The
string
of
events
starts
when
the
generator
send
the
events
to
the
event
kiwi.
They
event
mediator,
go
to
the
kiwi
and
gets
this
event
when
he
gets
these
events.
He
no
other
logic
didn't
do
he
no
other
steps?
He
don't
have
any
logic
in
know,
for
example,
in
a
shoe
receive
even
should
see
scenario
we
need
to
do.
We
need
verify
first,
if
the
quotation,
if
the
quotation
was
changed
for
then
we
notify
the
customer
he's.
Like
this
scenario,
we
have
a
change
of
address
here.
A
We
have
a
change
of
address
from
the
user.
The
user
of
the
issuance
company
changed
the
address,
and
now
the
customer
cells
would
send
and
even
for
the
the
queue
after
that,
David
mediator
will
know
about
the
event
they
use
st.
first,
a
notification
for
quotation
service
quotation
says:
will
do
his
job.
He
gonna
look
if
they
have
a
change
of
the
value
of
the
rate.
A
If
it
is
the
if
this
change,
he
was
saying
a
notification
from
event
mediator,
saying:
look:
the
customer
acts
need
to
change
the
value
E
and
then
the
mediator
knows
that
notification
cells
must
act,
so
he
wanna
send
a
notification
from
vegetation
sense.
If
they've
got
the
rate
has
not
changed.
If
the
customer
change
from
place
the
north
impact
on
his
insurance
rate,
we
don't
need
to
change
the
we
don't
need
sent
a
message
to
notification
service,
so
our
processing
will
stop
this
part.
A
A
They
broke,
the
broken
is
when
we
don't
need
to
do
any
large
hole
thing.
We
don't
need
st.
first
prefer
one
process
ordained
for
another
is
like
this
single
we
can
implement.
Do
the
implementation
with
activemq
the
Google
pub
serving
so
we
have,
the
events
will
be
sent
to
event
broken
and
the
event
processors
will
be
listening.
They
can
be
not
fine
or
we
cannot
find
them.
A
It's
all
depends
how
you
implement
them
and
the
event
processor
will
do
his
job
using
the
same
example
that
working
before
we
have
the
customer
change
of
headers,
we
will
send
the
customer
service.
We
send
a
notification
for
quotation.
Kiwi,
the
quotation
service
will
listen
to
the
kiwi
and
we
he
do
his
job.
He
will
see
our
this
customers
change
for
our
more
dangerous
place,
so
the
insurance
hater
of
them
is
gonna
to
hide
us.
He
gonna
pay
it
so
much
more.
Then.
Here
we
go
to
send
a
notification
for
notification.
A
Key,
we
send
a
look.
This
customer
needs
pay
more
and
notification
service
will
send
a
notification
from
our
customer.
If
you,
for
example,
the
quotation
cells
I
realized
that
has
not
changed,
they
will
finish
the
processing
right
here
and
notification
and
we
will
do
not
post
information
on
content
in
quotation
service.
In
quotation,
kiwi,
notification:
Kiwi,
that's
we
okay!
A
A
It's
a
notification.
The
processor
should
always
send
notification
for
the
generator
on
always
a
notification
for
processor.
Not
the
other
way
around.
The
processor
should
not
send
message
for,
for
the
producer
needs
has
spawned
immediately.
Once
the
processor
sent
the
notification,
we
need
to
do
something
when
processor
get
the
message
he
needs
to
know
what
to
do.
For
example,
if
they
don't
need
to
do
anything,
he
need
to
know
they
need
to
do
this,
so
he
need
takes
some
action.
Even
these
actions
means
do
nothing.
A
A
communication
follows
only
one
direction,
since
they
put
the
processor
sends
a
notification
sent
the
message
the
processor
should
before
his
life.
Like
is
nothing
happening,
he's
like
fire
forget
and
the
mediator
a
broker.
Ours
are
responsible
for
Duda
water,
job
guarantee.
The
process
of
you
receive
the
message
and
it's
common
free
and
even
should
not
should
never
same.
The
processor
do
something
he
needs
say.
Our
customers
exchanged
a
address
and
that's
it.
The
processor
should
know
what
to
do
with
the
DES
message.
A
And
when
we
work
with
every
architecture,
we
have
some
standards
and
with
EDA
it's
not
be
different.
We
have
a
bit
modification,
we
have
even
carry
stage
transfer
and
we
have
an
insertion.
We're
gonna
see
a
little
more
about
them
right
now.
So
every
modification
when
a
producer.
Well,
when
we
walk
with
a
notification,
it's
like
the
customer
service.
We
will
send
a
notification
for
another's
and
you
just
say
our
customers
acts
change
the
address,
and
it's
like
this.
We
have
others
change
before
they
think
of
me
of
a
poetical
scenario,
one
star.
A
Let's
start
off,
Snickers
wanna
share
that
data
with
the
market
with
the
partners,
and
so
they
won't
expose
and
if
a
broker
follows
first,
four
people
come
there
and
get
more
information
and
one
of
the
day
interested
is
the
banks,
for
example,
because
it's
more
easy
for
me
change
my
address
when
I
you
know
a
store
of
Snickers,
then
change
my
address
in
the
banking.
So
we
have
this
use
case.
I.
Do
a
change
of
my
address
in
the
customer
steps
of
this
store
and
this
the
customer
selves
will
be
date.
A
The
information
in
the
storage
and
they
will
send
a
notification.
It's
like
customers,
eggs
change,
their
data
to
my
event
broker.
They
stakeholders
will
be
listening
and,
for
example,
the
bank.
He
serves
no
taste
customer,
they
know
their
customers.
Eggs
is
a
customer
from
them,
so
he
gonna
two
hits.
If
he
he
wants
know
more
about
the
changing.
He
goes
to
either
fast
or
interface.
A
A
We
do
they
uncommon
from
a
singer
to
sing
the
signal,
don't
need
to
know
more
about
the
Hasib.
They
don't
need
to
wait
for
processing
and
nothing
like
that,
but
like
combs,
the
producers
may
be
overloaded
because
we
need
to
go
every
time
in
their
own.
Education
came
to
banking,
save
see
if
I
want
to
know
more
I
need
to
go
again
and
again
for
X
Y
in
all
the
customers
own.
So
if
I
have
a
multiple
stakeholders,
they
want
to
know
about,
the
same
notification
may
be,
my
producer
can
be
overlord.
A
A
The
customer
changed
the
address
and
different
from
the
event
notification.
We
say:
customers
acts,
OPA
dates.
The
zip
code
shoe
one
two
three
and
then
the
bank
says
you
can
do
all
the
processing
they
want
without
need
to
go
through
the
customer
saves
and
they
bank
cell
skims
the
bug
cells
can
start
information
for
when
they
need
they
can
get
more
fastly.
They
don't
need
to
go
to
customer
sales
for
more
information.
Why?
Right
so
like
pros?
We
gains
resilience.
A
Since
we
don't
have
to
go
more
to
the
customer
services
they
can
be
out
and
we
can
keep
doing
our
job.
We
don't
need
more
information
from
them
and
we
have
you
ever
noticed.
We
had
losing
the
producers
recognition
overloading.
We
don't
need
to
go
there
anymore,
so
they
can
keep
doing
his
job
without.
A
Are
you
gonna
be
the
information
here
here
and
here,
and
so
we
need
to
care
about
the
consistence
of
the
data
if
this
guy
changed
the
information,
for
example,
in
the
banking
services
and
st.
comes
to
me,
and
you
update
from
the
customer
service,
see
what
Tiny's
consider.
So
it's
a
thing
we
need
to
keep
in
mind
and
even
sourcing
event.
Sourcing
is
when
we
wanna
store
the
events
in
some
place
in
database.
A
hippo
story
for
have
more
information.
It's
like
seven
things
happened
with
our
system
and
we
need
to
hit
building.
A
We
can
use
event
search
for
this.
So
in
the
same
scenario,
we
have
others
change
for
a
customer.
We
have
the
customer
self
super
dating
database
and
we
send
even
call
address
change
for
not
for
our
event
data
source,
for
we,
if
you
wanna
in
the
future,
we
can
history
thing.
A
good
example
of
having
certain
is
geeky.
A
The
github
is
an
example
of
event.
Data
sourcing
insertion.
We
can
have
you
do
everything
from
beginning
to
end
with
information
there
we
are
putting
their
like
pros.
We
have
the
outage
we
when
we
want
to
know
about
something,
that's
happening.
We
can
go
to
the
hippo
story
and
know
about
the
information
and
the
bug
it's
an
issue
when
we
work
with
even
to
even
because
the
the
information
are
distributed.
We
have
a
lot
of
place
of
information.
A
So
when
we
work
with
event
sourcing,
we
can
plug
the
upholstery
of
data,
searching
and
hey
beauty,
our
or
program
or
everything,
with
step
by
step
and
see
what's
happening
in
like
Crohn's.
We
it's
not
a
very
familiar.
When
you
look
for
some
documentation
in
the
internet,
we
don't
have
so
much
because
it's
new
and
the
people
have
heavily
afraid
of
implementing
this
and
you
need
to
define
you
event
schema
what
you're
gonna
put
on
the
even
data
source.
Everything
is
coming
for
you,
you're,
gonna,
put
or
just
a
few.
A
A
So
it's
other
combinations,
the
specification
we
need
to
do
the
unification
of
the
things,
for
we
can
talk
with
everyone.
It's
a
language
of
lesson.
Kpi
is
focus
on
the
application
and
the
other
changes
that
uses
to
communicated
is
a
way
to
help
all
of
our
developers
to
know
what
to
do
when
we
have
to
consuming
in
Kiwi
in
publisher
from
Google
it's
important.
It's
like
he
opieop.
I
spec
it's
important.
A
A
B
A
Is
a
place
for
we
can
put
information
about
servers,
we
can
do
the
address
the
port,
the
security
one,
how
flow
we
will
need
to
follow
and
we
have
also
the
documentation
for
operation.
Specifically,
we
have
the
operation
AME.
We
have
the
description.
What
of
this
operation?
Does
we
have
the
contents?
We
need
to
send,
for
example,
like
payload,
for
this
operation.
We
need
to
send
the
comments
in
the
st.
Ed's.
A
A
We
had
loosed
the
coupling.
We
don't
have
more
are
saying
they're
attached
to
the
receiver.
We
walk
with
the
syncopation,
it's
easy
to
add
a
new
customer
since
we're
follow
the
concept.
Odd,
not
saying
a
common,
yes,
Indian
message
for
us:
adding
new
customers
adding
new
consumers
is
very
easy.
Just
plugging
and
consuming
do
what
you
want
with
the
information,
and
we
are
highly
scalable
in
this
stupid
and
like
cons,
we
can
say
they
may
lead
to
loss
information.
If
it,
there
is
no
one.
A
Listening
to
your
channel
that
information
you
may
be
lost,
it
can
add
more
complexity
if
we
part
implemented,
but
what
architecture
you
cannot
write
and
it's
a
challenge
for
data
and
governance,
because
we,
the
information,
are
distributes.
So
we
don't
know
where
the
information
are
coming
are
from
going.
So
it
can't
be
a
trick
for
this
and
now
first,
you
need
understand.
You
need,
because
it's
not
because
I'm
even
tell
coming
to
hype
right
now.
You
need
to
use
them
if
you
haven't
need.
A
If
you
really
need
to
have
a
problem,
you
need
to
choose
the
basic
two.
Three.
Maybe
if
you
use
a
synchronous
act,
a
tree
is
be
the
best
way.
You
don't
need
to
use
EDA
for
this,
but
you
see
easy
ta
you
need,
so
you
need
to
choose
a
standard,
a
partner.
You
do
have
a
notification
or
you
do
transferring
all
the
information
and
you
need
to
choose
the
best
tool
in
a
mecca
in
the
market.
Refer
do
this
for
it's
like,
we
have
the
Salang
see
we
have
the
Google
and
we
have
since
India.
A
Since
EJ
just
launched
a
new
product
even
stood,
he
is
for
working
with
the
events
and
we
do
push
for
the
subscribers
last,
because
you
put
that
your
information
in
the
customer
will
plug
with
us
and
with
the
other
things
about
security
and
hey,
try
of
information
and
push
for
subscribing.
So
let's
see
thanks
so
much
sorry
from
step
and
sorry
for
my
good
English
and
we
gotta.
C
A
A
Maybe
in
a
restaurant
true,
but
today
we
make
the
accommodation
for
the
custom
their
customers
will
plug
with
us.
We
do
all
the
steps
over
education.
Sandhya
come
back
end
point,
and
then
we
do
the
notification
as
identification
from
partner
and
we
say
don't
forget,
but
for
the
customer
do
they
pull
the
pulling?
We
may
problem
II
not
know.
Okay,.