►
From YouTube: Stitch your GraphQL APIs in a declarative way
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
So
in
the
previous
video
we've
exposed
a
rest
API
as
a
graphql
API.
This
was
the
product
page
API
that
was
running
in
the
kubernetes
cluster,
with
the
different
services
for
the
product,
page
reviews
ratings
and
so
on.
Here
we
are
going
to
expose
a
new
API,
but
that's
going
to
be
an
external
service.
So
again
we
create
this
API
doc
to
provide
the
graphql
schema.
But
this
time
you
see
we're
going
to
Define
an
external
service
for
this
open
library.org.
A
And
that
shows
you
that
we
can
expose
through
the
Gateway
as
a
graphql
API,
an
external
rest,
end
point
that
could
be
an
API
provided
by
a
virtual
machine
or
something
like
a
public
API
doesn't
really
matter
and
again
we
create
the
resolver
map
where
we
Define
that
to
resolve
this
schema
we
acquired
before.
We
need
to
send
this
request
on
to
open
library.org
on
this
path.
A
We
need
to
be
providing
some
additional
query
patterns
and
doing
a
transformation
again
with
JQ,
so
I
can
go
ahead
and
create
I
can
create
my
schema
that
will
combine
this
API
Dock
and
the
resolver
map,
and
after
that,
I
can
create
my
route
table
to
expose
this
particular
API.
Now,
if
you
see
this
option,
that's
also
quite
interesting
for
testing
log
sensitive
info.
A
You
can
then
go
into
the
logs
of
the
Gateway
and
see
a
lot
of
debugging
information
showing
you
what
other
rest
calls
that
are
sent
to
the
back
end
and
so
on.
So
if
there's
something
wrong,
you
can
troubleshoot
pretty
easily.
What's
going
on,
we
have
exposed
this
API
and
now
I
can
send
this
query.
I
want
the
product
title
and
I
want
the
different
languages
that
are
available
for
this
book,
which
is
the
same
book
that
is
written
by
the
book
in
info
API.
A
So
you
can
see
in
a
nice
format,
I
get
all
the
different
languages
and
what
we're
going
to
do
now
is
that
we're
going
to
be
stitching
these
elements
together,
it's
a
little
bit
like
how
we
stitch
these
two
apis
when
we
did
the
video
on
the
developer
portal,
if
you
happened
to
watch
that
video,
what
we're
going
to
do
is
we're
going
to
stitch
together
these
apis.
Again,
we
are
going
to
do
this
declara
ly,
which
is
basically
a
game.
A
Declaratively
I
want
to
stitch
together
these
two
apis
and
I
want
to
stitch
them
on
this
title,
so
they
have
the
same
title
for
this
book
and
I
want
to
Stitch
things
together.
So
I
update
my
route
table
now
you
see
I'm
using
this
new
particular
prefix
called
graphql
Stitch
and
I'm,
not
providing
a
graphql
schema,
but
instead
I
am
providing
a
graphql
stitch
schema.
So
I
can
set
this
here
and
now.
A
A
Now
I
have
to
stitch
a
new
API
and
I.
Have
this
products
for
home?
As
you
see
here,
I
have
this
new
Option
language,
which
is
present
so
I
can
run
that
and
I
didn't
put
the
right
end
point
here,
so
this
is
not
going
to
work
if
I
remember,
if
I
remember
this
correctly,
this.
This
is
something
that
has
to
be
updated
to
to
have
stitched.
So
we'll
need
something
that
has
graph
ql-
stitched
with
the
correct
endpoint
URL.
A
If
you
look
at
the
endpoint
URL
you'll
notice
that
it
says
Local
Host,
so
we'll
need
to
update
that
and
change
that.
So,
let's
go
back
over
here
and
what
we'll
do
is
we'll
we'll
copy
this
URL
over
here
and
that
input
looks
a
lot
better
as
an
endpoint
URL.
A
So
this
is
looking
a
lot
better.
It
reads
better
now:
I
can
go
ahead
and
rerun.
This
and
I
can
combine
these
together
so
that
the
first
API
I
was
having
I
didn't.
Have
this
language
option,
I
said:
okay,
these
language
options
is
provided
by
or
these
language
options
are
provided
by
another
graphql
API
if
I
stitch
them
together,
which
I
can
now
in
one
API
I,
can
give
both
information
about
this
book
and
the
languages
that
this
book
is
available.