►
Description
https://github.com/asyncapi/community/issues/404
- Overview of some public EDA APIs in real products for different industries
A
B
B
I
can
see
the
live
stream
started
on
youtube
again.
Just
remember
during
the
live
stream
like
the
live
stream,
goes
to
different
channels
like
asking
api
official
channels
like
twitter,
linkedin,
twitch
and
youtube,
but
I
mean
it's
complex
enough
to
follow
up
with
with
zoom
chat.
If
somebody
joins
on
zoom
and
then
so
we
we
choose
a
tasking
api
to
follow.
A
A
B
Can
you
folks
confirm
that
you
can
see
my
firefox
with
with
something
on
github,
okay,
yeah?
I
think
thank
you
pedro
and
also
like.
If
anyone
is
there
watching
on
socials,
then
as
well,
please
say
hello,
so
we
we
know
it
we're
not
alone,
although
again
it's
an
onboarding.
That
is
a
live
stream
so
automatically
it's
recorded.
B
B
That's
why
the
first
part
of
this,
like,
first
of
all,
like
all
the
three
parts,
are
based
on
this
script,
from
that
I'm
storing
on
github.
So
let
me
send
a
link
on
youtube
now,
the
part
number
one
that
is
on
our
massing
api
youtube
channel
in
this
part.
I
was
talking
about
basically
apis
in
theory,
so
just
to
recap
quickly
what
we,
what
we
discussed
was
that,
like
we
talked
in
really
general,
what
apis
are
difference
between
synchronous
and
asynchronous
apis.
B
And
we
also
talked
a
bit
the
the
specifications
like
what
they're
for
and
what
specifications
we
know
for
different
protocols
and
then
yeah
talked
about
even
driven
architectures
with
some
examples,
like
theory
theoretical
examples,
but
also
like
real
life
example
from
the
browser
perspective
and
the
most
important
like,
I
don't
think
the
most
important
was
when
I
was
scaring
people
that
ida
is
the
most
complex.
But
I
think
the
most
important
was
the
the
examples
like
this
theoretical
examples.
B
So
there's
one
in
this
case,
websocket
server
that
sends
and
receives
messages,
extreme
of
messages
from
different
clients,
and
we
also
talked
about
the
the
architecture
where
there's
a
a
message
broker
in
the
middle.
So
basically,
let's
just
look
on
this
most
complex
final
diagram.
So
basically
we
talked
about
the
architecture
where,
for
even
german
architectures,
where
there's
something
some
kind
of
message
broker
in
the
middle.
B
That
makes
sure
that,
like
it's
responsible
for
delivering
and
orchestrating
messages
in
the
in
the
architecture,
so
it's
receiving
and
sending
messages
to
receiving
from
publishers
and
sending
to
subscribers.
So
that's
what
we
were
talking
about
in
part,
one
in
case
somebody
wants
to
follow
up
first
now.
The
part
two
is
is
about
seeing
these
apis,
this
even
driven
architecture
apis
in
real
life,
in
what
industry,
they're
used
and
they're
being
used.
B
So
you
can
like
the
idea
is
that
you
can
somehow
map
this
theoretical
explanation
with
the
real
live
explanation
like
at
least
that's
the
idea.
Of
course.
If
you
remember
what
I
was
talking
the
last
time,
then
we
will
do
some
hands-on.
So
luckily,
there
is
one
api
in
the
world.
I
found
only
one
that
you
can
use
that
it's
asynchronous
and
you
don't
have
to
log
in
you,
don't
have
to
subscribe
to
get
some
authorization
key.
B
It's
it's
open
to
public,
so
it's
super
easy
to
to
play
with
it,
and
I
will
encourage
you
to
also
play
with
it
on
your
on
your
own
and
and
if
there
will
be
enough
time
might
be
that
there
will
be
enough
time
and
then
I
will
do
like
an
initial
intro
to
asking
api
before
part
two
of
the
onboarding
that
will
take
place
next
wednesday,
where
we
actually
will
create
a
real
async
api
document.
I
will
create
it
during
the
meeting.
B
We'll
explain
every
part
of
it
I'll
explain
things
that
I
did
not
cover
in
the
document
and
then
we
will
do
something
useful
for
with
the
asking
api
document
to
also
show
like.
What's
the
point
basically
but
yeah,
let's,
let's,
let's
start,
I
hope.
That's
fine.
The
most
important
lesson
from
last
part
was
I'm
almost
asking
if
you
prefer
slides
or
if
it's
okay,
that
we're
basically
skipping
through
a
script,
nobody
shared
a
feedback
that
we
should
do
slides.
So
that's
why
I
still
continue
with
the
script.
B
So
the
the
real
life
examples
there
are
like
there
are
not
there's,
not
a
lot
of
them,
but
there
are
there
are
and,
as
you
can
see,
they're
pretty
focused
on
a
specific
protocol
if
it
comes
to
a
publicly
available
apis
for
different
for
different
services
but
yeah,
let's,
let's
zoom
a
bit
to
not
overwhelm
you
with
this
huge
table,
and
I
will
just
skip
through
some
of
the
categories.
Some
of
the
examples
too.
So
you
could
get
some
feeling
about
the
the
real
life
examples.
B
So
the
first
example
of
of
apis
of
communication,
where
even
driven
architecture
is
pretty
critical,
is
internet
of
things.
So,
basically,
when
you
have
a,
I
don't
know
like
a
hitter
at
home,
you're
going
going
coming
back
from
from
office
to
coming
back
from
office
to
home,
and
you
want
to
have
a
home
heated
to
a
proper
temperature.
So
it's
not
super
cold
at
your
home.
B
So
that's
that's
internet
of
things
so,
basically
managing
a
lot
of
devices.
Anything
you
can
imagine
so
the
first
one
I
picked,
because
we
know
that
they
are
using
asking
api
and
also
the
the
members
of
the
of
the
developer
team
at
zorobots.
They
also
supported
us
in
the
api
during
the
asean
dpi
conference,
and
they
were
talking
about
asking
api
and
iot
so
so
yeah
the
the
use
case.
So
basically
what
they're
doing
is
they're
putting
a
an
api
into
in
your
robots.
B
So
you
can,
like
you,
can
imagine
many
different
robots
that
the
family
is
pretty
big,
like
you
have
some
robots
that
make
coffee
and
robots
that
do
other
stuff,
I'm
not
an
expert
in
robots.
I
think
me
personally.
I
will
avoid
having
robot
at
home
as
much
as
possible,
because
I
watch
too
much
science
fiction,
but
you
can
imagine
like
these
different
robots
that
automate
stuff
can
automate
stuff
at
home.
They
do
many
things
they
communicate
between
each
other
between
different
systems
and
the
things
that
they
do.
B
Every
single
move.
Every
single
operation
is
an
update
in
the
system.
It's
every
single
thing
that
they
do.
They
generate
a
message,
so
there's
a
huge
amount
of
messages
that
are
floating
in
the
in
the
in
the
whole
system
and
that's
why
they
need
even
driven
architectures
the
robot
to
to
do
a
move,
needs
to
have
a
message
about
the
possibility
to
do
a
move
without
asking
for
it
like
it's.
Basically,
it
has
to
be
smooth.
You
should
not
ask
if
I
can
move.
B
You
should
know
that
you
can
move
because
of
the
circumstances
that
occur
in
the
in
the
system.
So
what
you
need,
let's
say,
developer
when
you,
when
you're,
allowing
people
to
to
control
robots,
for
example
and
you're,
allowing
to
build
extensions
like
you,
want
to
programmatically,
create
some
your
own
custom
applications
to
to
to
manage
the
robots
at
home.
B
For
example,
you
need
to
ex
expose
the
api
to
the
developers,
so
developers
basically
need
to
know
what
kind
of
messages
run
in
the
system
and
what
they
can
basically
do
with
them,
and
what
are
the
options
so
zorobots
was
is
an
example,
and
you
can
see
the
docs
that
they're
generating
so
like
the
like.
There's
that
there's
there
are
many
different
messages
that
can
happen.
Many
different
things
that
can
happen
in
the
in
the
system.
B
Like
you
can
imagine
like
emotion,
so
you
need
to
basically
have
a
a
a
place
where
you
can
report
from
every
robot
that
there's
a
there's
a
motion
happening,
so
you
can,
for
example,
figure
out
that
okay,
this
particular
robot
is
now,
for
example,
moving
and
it's
moving
with
this
speed
or
it's
moving
or
it
stopped
moving
or
it's
where
it's
located,
etc.
So
all
these
information
is
like
you
want
to
read
them
when
you're
building
your
own
application.
B
That,
for
example,
alerts
you
when
robots
stopped
moving,
so
you
as
a
creator
of
of
additional
application
using
the
api
of
zarabots,
you
can
say
okay
like
for
this
particular
robot.
I
want
to
get
an
sms
message
whenever
robot
stops
working,
so
that's
the
the
use
case,
one
of
the
use
cases
in
iot
and
why
documentation
is
needed
like
why
you
need
to
know
all
this
particular
specific
information
about
everything
that
happens
in
the
in
the
entire
ecosystem
of
robots.
B
In
this
case
now,
there
are
also
iot
platforms
that
expose
yeah,
usually
again
mqtt
protocol.
So
I
think
you
can
already
assume-
and
that's
what
I
always
assume
when
somebody
comes
in
to
asking
api
and
asks
about
like
how
to
use
mqtt
with
using
dpi,
always
behind
my
head,
I'm
already
like
having
this
assumption.
Yeah,
probably
somebody's
doing
some
iot
stuff,
and
and
that's
why
mqtt
is
there
but
yeah?
B
Let's
I'm
gonna
skip
a
few,
because
that
will
take
ages
if
we
go
through
every
example,
but
yeah
tracking,
like
so
there's
this
company
called
cevio
and
they
they
do
some
like
tracking
in
warehouses,
like
real-time
information
about
location
of
different
devices,
if
they're
used,
if
they're
being
used
etc.
So
you
can
imagine
again,
like
real-time
location.
Information
like
this
asynchronous
communication
is
super
important
in
managing
the
the
warehouse
like
you
can
imagine
like.
B
Let's
say
you
have
a
a
group
of
forklifts
right
to
move
boxes
around
the
the
warehouse
so
as
a
manager
that
wants
to
have
as
efficient
warehouse
as
possible.
You
can
imagine
a
use
case
where
you
you
want
to
track.
How
often
your
forklifts
are
moving
like
you,
wanna
see
a
chart
that,
for
example,
you
have
five
forklifts,
but
only
three
of
them
are
moving,
or
only
only
four
of
them
are
moving.
B
So
you
want
to
dig
out
an
information
like
why,
at
the
current
current
time,
we
don't
have
all
the
equipment
operational.
Why?
For
a
few
months,
one
of
the
forklifts
was
not
moving
like
how
to
investigate
how
to
optimize
work
and
at
the
warehouse
you.
You
can
of
course
rely
on
humans
that
they
will
report
how
stuff
works
in
warehouse,
but
yeah.
B
B
You
can
collect
this
information
and
have
a
like
build
diagrams
or
any
other
way
of
consuming
data
to
to
read
from
it
like
analyze
the
data
and
learn
from
it
and
yeah.
Last
but
not
least
in
iot,
I
think
the
best
example
is
drones,
don't
want
to.
I
don't
want
to
relate
to
the
war
at
ukraine,
but
x
again,
like
drones,
are
useful
in
many
different
locations,
and
so
yeah
there's
a
there's,
a
company
that
produces
drones
and
again
what
what
is
nice
is
that
for
their
customers.
B
Let
me
close
this
unneeded
stops
for
the
customers,
they
don't
only
say.
Okay,
you
can
take
the
drone,
but
you
can
actually
program
it.
You
get
like
the
drone
exposes
an
api
that
you
can
use
to
also
yeah.
Do
some
operations
with
the
with
the
drone
and
very
interesting
here
to
see
is
something
that
you're
gonna.
See
with
other
examples.
Is
that
it's
very
common
that
you
built
a
mix
api?
B
So
that's
one
of
the
that's
why
I
also
put
it
first.
I
think
it's
the
for
me.
It's
because
iot
is
pretty
it's
not
so
fresh
anymore.
I
think
it's
pretty
pretty
good
use
case
for
for
us
in
api
and
especially
that
we
know
that
is.
It
is
used
in
using
api
and
also
when
you,
when
you
try
to
read
more
about
us
in
dpi
and
one
of
the
most
reused
examples
of
asking
api
is
a
street
light.
B
We
always
call
like
yeah,
show
me
streetlight
example,
and
it's
like
perfect
iot
example
like
it's,
because
you
want
to
have
like
iot
in
in
on
your
streets
with
street
lights.
You
want
to
know
how
given
street
light
is
performing,
if
the
I'm
not
sure,
what's
the
english
word
for
it,
so
this
the
stuff
that
bulb
that
gives
you
light
right.
Basically,
so
the
led
bulbs,
they
have
some
brightness
levels.
So
you
want
to
know
like
what's
happening
with
the
with
the
with
the
bulb,
I'm
not
sure.
B
A
B
You
so
yeah
another
use
case
messaging,
chats
so
again
like
in
in
different
systems,
and
I
will
pick
my
two
of
my
favorites
from
the
list.
One.
Like
slack
yeah,
I
mean
everybody
knows
slack,
and
we
know
that
slack
is
using
us
in
dpi.
We
know
they're
still
using
like
officially
1-0,
but
unofficially
at
least
I've
heard
some
rumors
that
they
of
course
plan
to
migrate
to
higher
version,
but
it's
always
difficult,
but
yeah
slack.
B
B
That's
it
you're
not
interested
in
anything
else,
but
when
there's
a
messaging
happening
happening
in
the
system
like
you
want
to
build
a
a
bot
that
will
always
check
the
message
that
is
sent
in
the
channel.
So,
for
example,
you
want
to
you
want
to
use
a
semantic,
not
semantic
and
and
how
you
call
it
sensitive
like
you
want
to
check.
B
You
want
to
drop
a
message
in
the
channel,
but
then
there's
a
bot
that
takes
your
message:
checks
it
in
a
knowledge
base
and
gives
you
alternatives,
like
that,
there's
some
articles
on
github
or
other
resources
that
could
answer
your
question
and
you're
being
asked
like.
Are
you
sure
you
want
to
ques
like
ask
a
question,
or
maybe
the
other
resources
already
answered
it?
B
Personally,
it's
a
ukrainian
company
and
the
second
one
that
they
support
us
big
time,
because
actually
this
whole
live
stream
is
supported
by
restroom.
I
o,
like
we
are
able
to
have
a
meeting
on
zoom
and
show
it
on
different
on
different
channels.
Thanks
to
restream
that
is
basically
sending
stream
to
different
channels.
B
B
You
can
write
a
code
that
will
actually
listen
to
all
the
messages
real
time
and
then
again
react
like
if,
if
one
of
the
message
says
that
the
stream
is
unstable,
like
I
don't
know,
I
could
have
a
like
a
message
somewhere
like
for
my
privately
some
script.
That
will
ping
me
hey,
like
we're,
noticing
some
some
issues
with
some
some
stream,
like
you,
better
check
the
connection
or
and
as
far
as
I
was
checking,
you
can
also
do
a
some
smart
checks
like
some
like.
B
That's
a
huge
that's
a
huge
industry
now
actually
like
when
I
was
leaving
my
previous
company.
Many
people
were
just
living
to
fintech
startups,
so
I
think
it's
pretty
hype,
but
if
you
don't
don't
follow
that
much
of
the
high
product
products
hype
technology
changes,
then
let
me
just
show
you
two
examples.
So
the
ones
that
I
examined
last
year
will
be
the
ones
that
I
will
show
you
as
an
example.
B
They
are
based
on
websockets,
so
that's
the
trend.
You
can
definitely
notice
in
fintech
like
if
it
comes
to
public
apis.
Of
course,
we
don't
know
what
they're
doing
internally,
but
basically
public
apis
when
they
want
to
expose
information
about
market
data,
all
the
currency,
value
and
trading.
It's
all
exposed
over
the
websocket,
because
you
really
need,
like
I
mean
you
know
like
how
the
market
and
stock
options
work
and
in
crypto
I
think
it's
even
more
unstable.
So
you
want
to
know
like
really
real
time.
B
What's
the
value
quickly
calculate
it
and
decide
if
you
should
sell
or
buy,
and
you
can't
base
it
on
synchronous
communication,
because
then
it
means
everyone
every
single.
Second,
you
have
to
ask
the
server.
What's
the
value
of
this
currency
at
the
moment?
What's
the
value
of
this
currency
at
the
moment
and
again
and
again
and
again-
and
you
can't
have
delay
if
you
don't
want
to
lose
your
money
so
so
yeah?
B
Let's,
let's
look
at
on
kraken
kraken,
because
when
I
was
writing
one
article,
I
was
actually
using
them
as
an
example,
because
when
I
look
at
this
old
school
ui,
it
reminds
me
of
it
basically
reminds
me
of
the
of
the
different
open
source
tools
for
generating
documentation.
So
they
are
either
using
async
api
one
zero.
I
think
and
that's
my
suspicion,
but
I
never
managed
to
contact
anyone
from
kraken
or
they
are
just
using
open
api
like
like
cracking
open
api
spec
to
generate
documentation
but
yeah.
A
B
Like
the
kraken,
it's
a
trading
platform
you
can
like.
Basically,
you
create
an
account
like
you,
create
an
account
in
a
bank
and
you
let's
say
you
want
to
buy
bitcoins
or
you
want
to
buy
a
polka
dot,
and
you
want
to
basically
be
a
better
trader
so
trades
not
only
from
time
to
time,
but
really
real
time
operate
on
the
market
information,
especially
if
you
invest
a
lot
in
bitcoin
I
can.
I
can
imagine
you
want
to
have
real-time
information,
so
so
they
exposed
the
websocket
api.
B
After
having
a
websocket
connection
with
the
server
in
your
client
from
your
client,
you
can
send
a
a
message
that
you
want
to
subscribe
to
information
about
xbt,
not
sure,
really
what
that
is,
if
it's
bitcoin
or
whatever
and
and
versus
dollars
and
versus
euro
value
and
and
what
kind
of
subscription
it
is.
And
then
you
start
receiving
a
stream
of
messages
basically
and
the
current
information
about
the
about
the
value
and
then,
of
course,
basing
on
the
value
of
the
message
that
you
get
in
response.
B
It's
basically
the
same,
and
it's
the
same
with
all
these
platforms
like
the
the
idea
is
like.
First
of
all,
we
have
huge
amount
of
messages
that
we
need
to
share
real
time,
the
most
the
best
way
to
do
it
is
websocket
asynchronous
and
but
some
things
again
they
need
synchronous
operations
like
like
the
best
example
like
you're,
getting
a
stream
of
information
about
the
value
of
the
currency,
and
at
some
point
of
time
you
say:
okay,
it's
a
good
value.
B
I
wanna
make
an
order,
so
you're
not
gonna,
send
an
sms
message
to
yourself
that
you
have
to
make
an
order,
because
it's
again
like
you're
gonna,
be
delayed
before
you
do
it
manually,
so
you
the
api.
What
that
they
give!
You
is
like
you
have
a
real-time
stream
of
information
like
what
you
can
do
in
the
system,
but
then
you
can
do
a
synchronous
call.
B
B
But
then
the
the
messages
like
you
could
see
in
the
in
case
of
kraken
there's
just
custom
message
where
you
can
subscribe
and
then
you
receive
messages
and
you
can
unsubscribe
and
stop
receiving
messages,
but
still
having
the
connection
open,
and
these
things
are
basically
so-called
sub
protocols.
So
some
kind
of
agreed
way
of
how
you
actually,
after
getting
a
connection
with
a
subject,
exchange
information.
B
So
basically
the
websocket
becomes
a
a
message
broker,
but
yeah.
Let's
not
complicate
our
lives
too
much
now
yeah,
the
next
one
is
yeah,
the
most
secret
one,
the
so
something
that
I
talked
about
last
time
like
it's
like
again
like
typical
broker-centric,
you
have
a
kafka
broker
somewhere
in
the
middle
in
your
microservice
architecture,
like
hundreds
of
micro
services,
connect
like
communicating
with
each
other
over
a
over
kafka
broker,
and
this
is
the
biggest
like
we
have
like.
We
know
we
there's
a
huge
adoption.
B
B
B
B
People
can
even
create,
like
event
portals
where
event
catalogs,
where
you
can
basically
browse
through
catalogue
of
the
messages,
so
you're
you're,
just
interested
to
know
like
what
kind
of
messages
are
floating
in
the
system
and
that's
what
async
api
is
needed
for,
and
that's
the
most
common
use
case,
but
again
like
as
you
can
see,
the
problem
is,
I
can't
show
you.
I
will
link.
B
You
can
at
least
see
the
talks
from
us
in
api
conference
2021.
and
sports
yeah.
It's
this
one
is
actually
super
interesting.
I'm
not
gonna
go
there,
because
I
think
it's
the
the
point
was
made,
but
I'll
just
tell
you
like
again,
like
another
use
case
for
real-time
information
that
you
want
to
get
from
the
system
like
there's
a
service
that
you
can
buy
so
you're
not
actually
buying
any
application
you're
buying
access
to
api.
That
gives
you
an
update
from
every
sport.
B
Every
possible
sport
out
there
in
the
world.
You
just
buy
access
to
it.
You
can
use
the
api
that
they
expose
and
you
can
build
your
own
application.
That,
for
example,
is
focused
only
on
football
soccer,
but
yeah
I
mean
football,
european
football,
for
example,
and
and
like
football
from
poland
for
example.
B
I
think
that
we
can
basically
summarize
this
whole
round
about
the
use
case
for
eda
is
again:
it's
like
it's
whenever
you're
building
a
system
that
you
where
you
need
a
real-time
information
and
the
amount
of
information
that
is
in
the
system
is
so
huge,
and
so
many
different
entities
consume
and
produce
that
synchronous
communication
is
a
terrible
overhead
and
super
expensive.
That's
why
you
need
asynchronous.
B
B
B
B
B
Unfortunately,
I'm
I'm
promoting
kind
of
postman
being
postman
employee,
but
I'm
doing
it
even
though
there
are
alternatives,
because
it
makes
me
much
easier
to
share
with
you
workspaces
and
you
can
actually
much
easier
play
with
the
api
than
with
other
existing
tools
that
I
that
I
know
so,
yeah
websocket
installation.
You
don't
have
to
install
it
now,
because
it's
yeah
you're,
just
gonna,
have
to
go
through
installation
unless
you
want
to
do
it.
So
now
we
will
just
play
with
with
postman
as
well.
B
There
are
some
installations
needed.
First
of
all,
yeah
you
need
to
access
postman.
I
think
you
have
to
create
an
account,
I'm
not
sure
if
you
can
fork
a
workspace
and
use
the
workspace
without
logging
in
logging
in
but
anyway,
because
in
in
the
browser,
we're
going
to
do
some
websocket
communication,
and
you
have
to
also
install
additional
postman
desktop
agent
to
actually
be
able
to
use
websocket
api
inside
postman.
B
B
A
B
B
It's
just
a
terminal
tool,
so
I'm
using
pretty
old
version,
one
six,
but
it's
it's
enough.
So
first
of
all,
yeah
from
the
documentation
like
I'm
not
gonna
go
there.
But
if
you
recall,
when
I
was
showing
the
kraken
documentation
again
like
the
first
information
you
need
to
get
from,
docs
is
like
how
to
connect
to
the
server.
B
B
B
I
need
to
know
what
kind
of
messages
happen
in
the
system
and
I
need
to
know
that
there's
an
event
called
system
status
which
allows
me
to
basically,
first
of
all,
when
I
start
coding
a
real
application
that
listens
to
how
to
crack
an
api.
I
can
be
always
sure.
Okay,
like
so
on,
establishing
the
connection.
I
always
receive
the
status
information.
B
I
need
to
know
what
fields
are
there,
the
connection
id
the
event
the
status,
and
I
know
so.
Okay,
whenever
the
message
event
is
system
status,
I'm
checking
the
status
information
and,
and
if
it's
online,
then
everything
is
okay.
So
when
I'm
starting
my
my
service
that
listens
to
kraken
api,
I
can
say:
okay,
I
can
drop
a
message
in
the
console.
Look
like
yeah,
the
connection
so
far
is
pretty
stable,
like
it's
going
a
good
direction.
B
Let's
see
now,
let's
make
now,
let's
the
next
stuff,
is
that
this
api
documents
that
they
allow
allow
me,
as
an
api
consumer,
to
actually
produce
some
messages
to
communicate
with
the
with
the
server.
So
I
can
again
like
in
my
application.
I
can
have
some
interval
so
like
every
some.
Every
sometime
send
a
message
like
a
pink
message
to
the
server
to
check
if
it's
still
actually
alive-
and
I
have
to
know
that
I
can
send
a
ping-
oh
and
it
failed.
B
B
Also,
okay,
it's
already
disconnected
so,
but
no
worries,
so
we're
gonna
send
a
message
where
we
want
to
subscribe
to
information
about
the
about
the
the
currency
value
and
now
praise
yourself,
because
once
I
sent
this
message,
you're
gonna
actually
see
the
you're
gonna
see
this
this
feeling
of
why
why
the
asynchronous
is
needed?
Why
we
need
real
time
what
I
meant?
What
I
mean
by
saying
that
there's
a
lot
of
messages
in
the
system,
so,
let's
send
okay.
B
So
we
can
see
that
now
I
told
the
system
that
me
as
a
client.
I
want
to
get
information
about
whenever
there's
a
change
in
the
value
of
the
currency,
for
this
particular
crypto
and
the
value
in
the
in
the
normal
currency
and
I'm
receiving
two
types
of
messages.
So
one
is
the
information
about
the
value
and
also
regular
heartbeat.
B
That
lets
me
know
that
like
yeah,
it's
it's
actually,
it's
you're
not
receiving
messages,
not
because
we
disconnected
you
but
like
everything
is
fine,
like
the
heartbeat
of
the
server
indicates
that
it's
running
and
again
like.
If
you
can
see
these
messages,
they're
super
cryptic
and
again
like
that's
what
you
have
to
specify
the
user
of
actually
the
the
owner
of
the
kraken
api.
They
need
to
be
super
precise
and
they
are
actually
in
their
api,
but
I
think
they
do
it
manually.
You
need
to
explain
like
okay
in
the
response.
B
You're
gonna
get
an
a
message,
but
it's
as
minimalistic
as
possible.
So
it's
as
lightweight
as
possible,
so
the
keys
you
can
see:
they're
they're
just
one
letter,
so
it's
it's
as
small
as
possible.
So
it's
the
the
size
of
the
message
is
as
small
as
possible,
so
it
doesn't
overload
the
the
wire
that
it's
running
over,
so
you
need
to
have
good
docs
and
the
schema
information
of
the
message
that
you
will
receive
and
what
value
is
hidden
under
what
key
and
how
you
should
calculate
these
numbers
like.
B
How
do
you
should
what
operations
you
should
do
in
your
service
to
actually
calculate?
What's
the
value
of
the
of
the
currency
and
then
again
like
during
the
running
connection,
I
can
say:
okay,
I
want
to
unsubscribe
from
information
about
us
dollars.
I
only
want
to
receive
messages
about
euro
because,
as
you
can
see
for
now,
it's
it's
usd
it's
it's
euro!
B
B
B
B
Show
in
postman,
because,
like
my
plan,
is
that
at
least
ambitious
plan
is
that
long
term
would
be
nice
to
have
such
a
workspace
in
postman,
where
we
showcase
different
apis
as
again
like
to
showcase
like
different
examples
of
ada
apis,
especially
that
now
websocket
is
supported
so
kraken
api.
I
provided
here
in
this
workspace
and
an
example
like
so
much
easier.
You
don't
have
to
have
cli,
so
basically
yeah.
B
B
B
B
And
that's
the
hands-on.
I
definitely
encourage
you
to
have
play
with
it
and
get
this
experience
of
actually
like
seeing
like
what
the
hell
is
happening
like
I
subscribe,
and
all
these
messages
start
coming
in
like
try
to
subscribe
to
many
different
currencies,
not
just
two
and
you're
gonna,
see
like
the
feeling
of
this
real
time
and
and
bazillion
of
different
messages
that
happen
in
the
system,
and
you
want
to
know
sometimes
about
all
of
them,
sometimes
about
your
specific
one.
B
That's
why
you
need
this
pops
up
feeling
you're
just
subscribing
to
some
specific
information.
Sometimes
you
unsubscribe,
etc,
etc,
but
also
you
need
some
additional
information
from
the
system,
also
in
real
time
so
yeah.
To
summarize,
we
it's
55
past,
so
we
will
finish
with
this
so
summarizing
what
we
managed
to
discuss
with
part
one.
We
talked
about
apis
in
theory.