►
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Lightning Talk: Connect from Browsers Using gRPC-Web - Stanley Cheung, Google
We are delighted to introduce gRPC-Web, a cross-browser javascript library which allows developers to write web applications that connect to gRPC servers. In this lightning talk, we will briefly talk about the gRPC-Web protocol and deployment model. We will also show a quick demo on how easy it is to start writing a browser application with gRPC-Web and Protobuf. With gRPC-Web, you get a very familiar gRPC-style API compared to other languages supported by gRPC. We will also talk about how future holds and what we have planned in the roadmap.
To learn more: https://sched.co/GrVV
A
Hi
everyone,
my
name,
is
Stanley
Shan
I
work
in
Google,
I
work
in
a
JRPG
project
for
last
three
and
a
half
years,
I
used
to
work
in
PHP
and
now
working
I'm
going
to
talk
about
a
PC
web.
So
I
just
want
to
see
a
quick
show
of
hands
how
many
people
are
familiar
with
G
RPC,
very
good,
very
good,
more
than
half
so
good.
So
just
a
brief
overview
of
what
G
RPC
is
a
remote
procedure
calls
RPC
style
library
framework.
A
It's
highly
pure
high
performance,
open-source
general-purpose
standard
based
feature-rich
RPC
framework,
so
it
now
it's
a
CNC
f
project.
A
fun
fact
about
chiaki's
is
that
the
G
actually
doesn't
stand
for
google
so
of
each
release.
G
stand
for
something
different,
so
in
1.0,
oh
gee,
a
Christmas
of
G
RPC,
so
er
pcr
support
a
lot
of
languages
about
ten
now
and
we
are
trying
to
add
more.
This
is
a
very
typical
way
of
architecting
your
your
application.
Where
you
can
string
together
our
services
cause.
A
You
can
have
one
server
to
talk
to
another
in
string
together
and
you
can
reach
your
browser
or
your
laptop
or
like
any
cloud
you
can
deploy
or
certainly
deploy,
GRP
see
in
kubernetes
now.
So
this
is
a
very
typical
way
of
of
how
a
RPC
works.
You
have
a
client,
you
have
a
server,
you
import,
a
library
and
you
can
talk
to
send
each
other's
messages
in
the
G.
Rpc
protocol
is
mostly
based
on
n
th.
A
The
new
HTTP
2
protocol
that
I
can
leverage
a
lot
of
the
new
features
over
the
existing
issue,
one
one
protocol.
So
in
general
you
have
a
product
of
types
of
definitions,
you
don't
have
to.
Usually
you
do,
we
do.
You
can
generate
some
code
into
your
application,
import
it
and
you
can
start
sending
messages
for
sending
RPC
calls.
So
it's
very
a
simple
easy
way
to
think
about
it,
and
you
don't
have
to
worry
too
much
about
like
the
networking
aspect
of
things.
A
So
just
a
quick,
quick
thing
so
in
the
client,
let's
focus
on
the
time
now,
so
you
can
write
in
C
plus,
possibly
in
Brian
Java
in
Python.
You
know,
like
the
ten
other
languages
I
mentioned
in
the
same
thing
in
us
only
on
D
on
the
server
side.
Now
can
we
do
the
same
thing
in
browsers
if
we
swap
the
crime
with
like
Chrome
and
Safari
and
and
and
and
and
Safari
Firefox,
and
can
we
do
the
same
thing
and
talk
to
your
PC
with
your
services?
A
The
answer
is,
unfortunately,
no
right
now
so
are
the
dtt
browser
environment
is
rather
restrictive
to
standard
Web.
Api
that
exposes
to
us
is
like
xhr
and
fetch
don't
kind
of
expose
the
underlying
HTTP
wipe
or
local
teachers.
Like
there's
no
concept
of
a
channel.
We
cannot
control
whether
you
are.
What
have
a
protocol
negotiation?
Is
there
we
can.
We
have
very
little
control
over
the
very
low
level
or
data
stream
underlying
connections
and
and
use
an
info
browser
clients.
A
They
usually
prefer
like
text
data
RPC
RPC
is
mostly
a
binary
protocol,
so
there
are
some
some
difficulty
there.
Pc
protocol
has
relied
a
lot
of
the
response
trailers
to
carry
some
kind
of
metadata
about
your
RPC
back
to
the
client,
and
that
is
not
exposed
to
us
in
the
standard
browser
browser
api's
and
for
browser
client.
A
We
have
to
take
care
of
like
some
web
service,
specific
features
like
coerces
a
greedy
and
all
that,
and
in
a
lot
of
the
cases
where
you
deploy
your
web
application,
you
may
be
behind
some
firewalls,
so
HTTP
2
may
not
be
available
in
in
those
kind
of
situations,
so
the
RPC
web
is
actually
a
auxilary
protocol,
defining
a
kind
of
a
translation
layer
between
browser
requests
and
G
RPC.
So
currently,
the
kind
of
the
translation
is
to
be
implemented
in
envoi,
a
fellow
CN
CF
project.
We
are
trying
to
implement
more.
A
Actually,
we
actually
start
off
implements
and
nginx
module.
So
right
now
is
invoice
all
of
the
boss
support.
You
can
flip
a
switch
and
you
can
use
it
it's
over
standard
HTTP.
It
is
a
custom
content
had
to
specify
that
this
request
is
a
RPC
web
requests.
The
trailers
is
encoded
in
the
stream
itself.
A
The
limitation
right
now
is,
you
can
only
do
you
need
recording
server
stream
and
call
we
are
trying
to
look
into
how
we
can
add
clients
by
that
streaming
streaming
later,
so
this
is
kind
of
the
updated
thing,
updated
architecture,
architect,
architecture
of
your
web
applications
is
that
in
your
browser,
you
do
your
Jo
PC
web,
and
you
talk
to
your
PC
web
with
a
Cavett
envoi
proxy.
You
would
do
the
translation
and
do
that
and
communicate
with
your
in
gr
PC
with
your
back-end.
A
So
from
the
browser
perspective,
it's
just
like
a
normal
client
that
you
write
an
O
or
C++
or
Java.
The
project
is
GA
since
a
couple
months
ago
we
are
trying
to
get
feedback
on
on
your
use
case.
So
please
visit
us
on
pci.
All
the
specs
is
over
there.
The
project
has
been
used
internally
for
2
years
already.
There
are
currently
in
NPM,
and
then
we
have
added
typescript
support.
So
in
the
future
we
are
trying
to
end
more
processor
and
more
support
to
these
curved.