►
From YouTube: WebAssembly as a cloud-native runtime for serverless functions - Michael Yuan, Second State
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
WebAssembly as a cloud-native runtime for serverless functions - Michael Yuan, Second State
Serverless function-as-a-service is popular among developers. Public clouds use hypervisor VMs or containers (e.g., Docker) to run serverless functions. But they are slow and resource-intensive. In this talk, Michael will discuss the Wasm VM as a lightweight cloud-native runtime. It allows serverless functions to be embedded in edge & IoT devices, as well as in SaaS platforms. It also enables developers to deploy serverless functions on legacy systems without changing any code. Topics include: * How to create a function-as-a-service with Node.js & Wasm * How public clouds like Tencent Cloud utilized Wasm in serverless environments * How to use K8s and cloud-native tools to deploy & manage Wasm VMs Developers will get hands-on experience to create & deploy high-performance serverless functions in Rust.
A
A
Well,
before
we
start,
let's
look
at
what
is
the
serverless
function?
Serverless
function,
you
know
the
first
serverless
function,
that's
well
known
is
adapts.
Lambda
right,
you
know.
That's
it's
a
new
paradigm
of
developing.
You
know!
That's
you
just
upload
your
code
and
you
don't
need
to
know
where
it's
running
and
what's
operating
system
is
running
and
and
any
detail
about
the
server.
The
public
cloud
will
just
run
it
and
ap
a
url
or
something
else
that
for
you
to
call
this
function
and
get
a
result
right.
A
So
that's
what
we
call
no
infrastructure
and
it's
because
the
developer
don't
see
the
server
we
we
call
it
serverless,
although
obviously
there's
still
server
on
the
back
and
just
serverless,
just
making
servers
great
again
right.
You
know!
So
that's
if
you
look
at
this
survey
that
from
datadog
you
know
the
lambda
adoption
of
aws
users
has
gone
really
sky
high.
I'm
I'm
actually
surprised
to
see
this
half
of
aws
users
have
adopted
lambda.
A
It's
the
same
for
the
other
clouds
as
well.
So
let's
look
at
the
leading
cloud
in
china.
You
know
aws.
Is
it's
leading
color
in
america?
So
just
I
translated
this.
The
paragraph
of
chinese
words
for
you.
So
you
know,
tencent
cloud
is
a
leading
cloud.
Is
a
leading
cloud
provider
in
china?
Has
over
1
million
developers
provide
services
to
10
000
businesses,
including
500
large
enterprises?
A
How
many
serverless
function
cost
seats
per
day,
10
billion
costs
per
day?
You
know,
there's
people
are
writing
a
large
number
of
you
know:
high
traffic
heavily
used
applications
using
tencent
cloud
serverless
as
the
back
that
as
a
back-end
service
right.
So
that's,
it
shows
us,
that's
really
popular
and
the
developers
really
want
to
use
it
right,
and
so
what
are
the
most
programming
languages
in
those
you
know?
What's
what
the
developers
use
when
they
write
serverless
functions
and
they
use?
You
know
python.
Node.Js,
no
surprise
here.
A
Those
are,
I
wouldn't
call
them
easy
languages,
but
those
are
high
productivity
languages
right.
You
know
it's
easy
to
write
applications
in
those
languages,
but
they
are
also
heavyweight
languages,
meaning
that
they
have
a
heavy
runtime
and
has
somewhat
slow
performance
right.
So
you
know
so
that's
developers
write
those
applications
and
then
you
in
python
node.js,
probably
without
thinking
a
lot
about
the
application
about
the
performance
and
that
shows
the
duration
of
lambda
functions.
You
know
the
the
this
figure
said
it
in
a
way
that
is
glass
of
four
right.
A
Half
of
the
lambda
functions
was
less
than
800
milliseconds.
My
reaction
is:
oh,
my
gosh
half
of
the
laminar
functions
run
more
than
800
milliseconds,
meaning.
So,
if
you
think
about
you
know
how
high
performance
internet
works,
how
hyper
one's
website
works?
If
you
consider
you
know
the
the
time
need
for
the
data
to
travel
through
the
network
to
to
reach
the
customer
and
then
to
go
from
the
client
to
the
server
and
then
back.
A
You
know
to
spend
800
0.8
seconds
on
the
server
it's
a
very
very
long
time,
especially
if
you
have
a
application
that
makes
10
20
or
even
hundreds
of
back-end
services
costs.
You
know
that
could
really
add
up.
So
you
know
so
that's
actually
that's
actually
one
of
the
other
things
that
someone
surprised
me
is
that
you
know
the
way
that
people
use
serverless
functions
are
tends
to
be.
That's,
I
think,
that's
on
the
next
stage,
so
the
most
common
serverless
function
use
cases
to
run
a
simple
function
on
a
heavy
stack.
A
So
the
stack
you
know,
node
python
node.js
are
slow.
It
takes
a
long
time
and
that
in
turn
only
allows
people
to
run
simple
functions.
You
know
you
can
only
run
a
fairly
simple
function
and
it's
gonna
take
800
milliseconds.
So
that
translates
to
what
you
know.
That's
translates
to
there's
only
limited
number
of
use
cases
that
we
can
actually
use
service
functions,
meaning
you
know
in
aw
in
most
public
clouds
it
used
as
the
glue
code.
You
know
when
you
need
to
move
something
from
aws
s3
to
the
aws
message
queue.
A
You
know
something
like
that.
The
best
way
to
do
it
is
to
use
servers
function
because
it's
it's
sitting
in
the
message,
queue
and
it's
not
very
time
sensitive
and
it's
there's
no
one
else
that
waiting
for
a
real-time
response
from
it.
So,
in
those
cases
where
you
know
you
can
write,
you
know
python
and
node.js
applications
and
not
really
care
about
their
performance,
and
you
know
each
function
called
takes.
Maybe
a
second
right,
you
know
or
more
so
that's
that's.
Today's
most
common
use
case
of
serverless.
A
However,
as
we
can
imagine
you
know,
because
serverless
is
such
a
powerful
paradigm
and
a
lot
of
developers
would
love
to
use
it
and
a
lot
of
developers
actually
want
to
write
four
applications
in
serverless.
You
know,
there's
a
there's
a
new.
You
know
new
way
of
developing
web
applications,
called
the
gem
stack
and
jm
stack
right.
If
you
haven't
heard
of
it,
you've
probably
already
done
it.
You
know
that's
because
I
think
most
new
web
applications
today,
I
see
actually
what's
doing
what's
done
in
that
fashion.
A
You
know
so
it's
so
on
when,
on
the
front
end,
there
is
a
static
website
generator.
So
you
have
frameworks
like
view
or
next
js
or
hugo.
Something
like
that.
So
I
took
the
content
that
you
wrote
in
some
kind
of
markup
and
generate
a
static
website
with
javascript
in
it,
and
that
static
website
can
be
deployed
anywhere.
You
want.
This
can
be
deployed
on
the
local
host,
for
instance,
it
can
be
deployed
on
cdn
or
it
can
be
deployed
you
on
blockchain
right.
A
You
know,
that's,
you
know
you
can
deploy
it
anywhere.
You
want
because
it
was
just
a
bunch
of
html
files
and
javascript
and
then
javascript
contact
the
backend
service
to
provide
functions
for
this.
For
this
starting
ui
right,
you
know,
so
you
have
a
webpage
and
then
javascript
goes
to
call
some
back-end
function
to
do
things
like
you
know,
image,
recognition
or
you
know,
saving
data
to
the
database.
You
know
things
of
that
nature
and
that
back-end
function
is
typically
a
serverless
function
right.
You
know,
so
that's
if
we
see
it
from
that
lens.
A
You
know.
That's
you
want.
We
want
to
use
serverless
as
as
a
universal
back-end
service.
We
would
want
it
to
be
much
faster
and
much
lighter
and
basically
it
needs
to
have
a
different
performance
characteristics
than
what
serverless
is
today
right.
It's
it
shouldn't,
take
800
milliseconds,
it
shouldn't
even
take
80
milliseconds.
It
should
be
a
lot
more
faster
10
times,
100
times
faster
than
that
right.
So
you
know
so
that's
where
we
think
you
know.
A
That's
the
current
model
or
the
current
paradigm
of
serverless
can
really
get
some
help.
You
know,
that's
you
know.
That's
where
we
think
cloud
native
web
assembly
could
have
will
have
an
impact.
Okay.
What
could
contribute
to
to
this
whole
thing
so
before
as
we
get
into?
However,
somebody
could
help.
Let's
take
some
time
to
review.
What
are
the
serverless
strong
texts,
popular
serverless
contacts.
A
A
You
know
it
provides
a
high
level
of
isolation
for
each
of
the
serverless
instances,
and
you
know
so.
The
serverless
is
contained
within
the
vm
and
that,
but
that
is
very
inefficient
because
you
start
a
whole
operating
system
just
and
then
the
the
software
stack
on
the
operating
system
just
run
a
single
function
and
then
shut
it
down
right.
A
You
know,
that's
to
start,
it
up
may
take
a
second
and
then
the
the
function
when
it
takes
10
milliseconds
and
then
you
know,
99
of
the
work
in
this
process
is
wasted
or
it's
it's
infrastructure
busy
work.
So,
although
that
provides
safety
and
security,
that's
not
very
efficient,
so
some
people
start
to
use
application.
Containers
like
docker
to
do
that
and
docker
is
a
lot
faster
than
the
hardware
vm,
but
it's
also
provide
less
isolation
and
and
also
although
the
docker
runs
on
top
of
operating
system.
A
It
also
has
a
guest
operating
system
inside
it,
so
it
takes.
It
still
takes
time
to
get
up
the
operating
system
and
the
software
stack.
So
it's
so,
although
it's
faster
than
hardware
vm,
it
still
takes
time
to
prepare
the
environment.
Then
the
third
level,
the
highest
abstraction
level,
is
to
run
high-level
language
vms
in
a
thread.
So
the
most
classic
example
is
the
jvm,
and
you
know
the
java
virtual
machine,
but
it's
also
the
python
runtimes,
the
v8
for
node.js
and,
of
course,
web
assembly.
A
A
You
know
it's
hard
to
believe
two.
You
know
more
than
two
years
ago
now,
the
founder
of
docker
and
the
cto
of
you
know
the
first
cto
of
docker
said:
if
web
assembly
wasn't
wasn't
stand
for
web
assembly,
if
web
assembly
plus
was
existed
in
2008,
we
wouldn't
have
needed
to
create
a
docker.
You
know,
that's
how
important
it
is
web
assembly
on
the
server
is
the
future
of
computing.
That's
how
important
it
is.
That's
I
thought
that's
very
strong
words
right.
You
know.
That's
a
standardized
system.
A
Interface
was
a
missing
piece,
so,
let's
hope
boss
is
up
to
the
task,
we'll
talk
about
what
was
is
in
a
minute,
so
we
have
made
the
claim
that
web
assembly
is
faster
than
darker.
Docker
is
faster
than
hardware
vm
and
micro
vm,
where
you
know,
there's
lots
of
research
and
lots
of
data.
That
shows
that
we
we
don't
want
going.
You
know,
that's
you
know,
that's
we'll
just
take
that
as
fact,
but
the
comparison
between
webassembly
and
docker
is
interesting.
You
know,
that's
that's
a
study
that
we
did.
A
A
The
blue
bars
are
ssvm,
which
is
our
implementation
of
webassembly,
our
open
source
implementation
web
assembly
and
we're
going
to
talk
about
ssvm
in
a
minute
in
a
minute
as
well,
and
the
orange
bar
is
docker
plus
native
meaning.
That's
it's
a
dark.
It's
a
variable
darker
image,
and
then
we
run
a
native
application
on
top
of
that
image,
the
native
applications
written
c
and
compile
to
to
run
whatever
the
guest
operating
system
docker
has
and
then
the
green
bar
is
dockercut.
Node.Js,
it's
docker
runs
a
high
level.
A
Programming
language
and
high
runs
a
heavy
stack
right
to
perform
this
exact
same
functions.
So
the
note
is
the
note.
Function
is
to
just
start
and
shut
down
to
measure
startup
time
and
the
blue
bar
is
actually
invisible,
so
we
have
to
multiply
it
by
50..
You
know
so
in
order
to
just
for
it
show
up
on
the
on
the
on
the
block
so
from
here
we
can
see
in
in
terms
of
startup
time,
although
docker
improves
significantly
from
micro
vms,
it's
a
thousand
times
slower
than
web
assembly.
A
You
know
we
have
assembly
just
can
start
and
stop
in
very
very
quickly.
Without
you
know,
that's
it
hardly
consumes
any
time,
but
with
docker
you
know,
that's
you're
still
talking
about
tens
of
milliseconds
just
to
start
up
the
just
to
start
the
container,
and
then
you
have
to
run
the
application.
That's
that's
written
in
a
slow
language
on
top
of
it
right.
A
So
from
there
that's
that's
already.
You
know,
I
think,
over
over
100
times
you
know
performance
scans
right
there
and
then
for
the
application.
That's
actually
the
cpu
intensive
application
that
actually
runs
inside
the
containers
we
could
see.
Unsurprisingly,
node.js
performs
worse
because
you
know
this
it's
written
in
javascript.
What
do
you
expect
right?
Docker
plus
native,
is
comparable
to
ssvm,
but
ssvm
is
still
faster,
so
even
for
for
runtime
tasks,
you
know
webassembly
container
plus
it's
you
know
it's
sandbox
bytecode.
A
It's
still
about
10
20,
faster
than
docker
plus
fully
native
code.
You
know
so
that's
means,
you
know
if
we
do
a
performance
comparison,
whether
somebody
is
you
know
faster
than
darker
across
board
and
that
solves
the
dilemma
that
we
that
we
raised
in
the
beginning
of
our
talk
is
to
say
how
do
we
make
serverless
functions,
start
up
faster
and
run
faster
so
that
it
can
be
more
versatile
so
that
it's
not
just
the
glucose
to
connect
different
systems.
We
make
it
a
universal
back
end
for
for
gm
stack
applications
right.
A
So
you
know
that's
here.
We
show
that
whether
somebody
at
least
have
the
potential,
because
it
is
fast
so
cloud
native
web
are
some
of
the
use
cases,
and
so
those
are
the
partners
that
we
work
with.
You
know
at
second
stage.
Obviously
there
are
other
use
cases,
but
I
can
only
talk
about
things
that
I
actually
know
right.
You
know,
so
those
are
our
customers
and
partners,
and
the
first
category,
of
course,
is
jam
stack
up
web
applications.
A
The
web
assembly
helps
here
by
providing
a
universal
runtime
that
we
can
deploy
not
only
on
the
cloud,
but
also
on
the
edge
in
a
cdn
network
as
a
compute
node
right
that
allows
gems
gem
stack
application.
The
serverless-based
gem
stack
applications
to
have
to
reach
high
performance.
You
know,
then
we
have
sas
and
pass.
A
also
interesting
use
case
is
because
you
know
one
of
the
common
thing
about
sas.
Application
is
the
need
to
customize
and
extend
it
for
different
customers
right
and
today.
A
People
do
that
with
the
api
with
callback
apis,
meaning
that's
the
the
events
that
happen
in
the
sas.
Someone
did
something
on
sas
platform
could
be
sent
to
a
external
server
and
then
developer
runs
that
server,
and
then
the
developer
provides
response
from
that
server
and
goes
back
to
the
source.
Interface.
Just
imagine
say
a
chat
bot
right.
You
know
a
messaging
application.
You
know
how
do
you?
How
do
you
create
a
chat
box
for
messaging
sas
application?
A
You
know
you
have
you
have
an
api
based
approach
where
you
know
when
a
message
was
sent
to
a
user.
Something
happened
in
that
inside
that
messaging
system.
The
messaging
system
will
forward
this
message
to
the
server
to
external
server
that
you
run
and
then
the
developer,
the
the
application
runs
on
the
server,
sees
this
message
and
generates
some
kind
of
response
and
sends
it
back
into
into
the
messaging
application,
and
then
the
messaging
application
translates
that
into
a
message
and
send
it
back
to
the
to
the
user.
It
responds
to
it
right.
A
So
in
that
scenario,
you
know
we
have
a
chat
box,
but
we
also
have
external
server
side
application
that
runs
side
to
side
with
the
sas
and
isn't
it
let's
reimagine
how
this
might
be
wrong
in
a
serverless
environment?
Why
do
we
need
the
developer
to
set
up
a
server
that
on
the
side,
you
know?
That's,
it's
tedious
works,
it's
expensive,
it's
tedious
and
it's
it's
also
an
error
prone,
because
you
know
the
server
might
be
done
and
all
that.
A
Why
can't
the
developer
just
submit
a
piece
of
code
just
to
submit
a
function
into
the
source
platform
and
say
this
function
responds
to
an
incoming
message
right.
You
know
so
if
anyone
send
the
message
to
to
any
to
my
users
call
this
call
this
function,
and
this
function
takes
a
string
as
input
and
returns
a
string
at
output.
So
something
like
to
apply
the
serverless
model
into
a
source
application.
You
would
be
able
to
get
rid
of
most
of
the
callback
apis
and
most
of
the
api
complexities
when
people
extend
those
sas
applications.
A
So
that's
that's.
That's
something
we're
also
very
excited.
You
know
that
we
work
with
some
sas
providers.
That's
for
for
for
this
very
purpose
right.
You
know,
of
course,
there's
iot
devices
and
cars.
You
know,
there's
you
know.
I
mean
automobile
operating
system,
there's
lots
of
places
where
you
know
the
the
sub
module
subsystem
is
developed
by
someone
else,
it's
by
a
supplier
or
by
a
by
a
part
supplier
or
by
integrator,
and
then
it
needs
to
be
integrated
together
in
a
system.
That's
that's!
A
That's
that
can
run
together
without
interfering
with
each
other
and
one
of
the
ways
to
do.
That,
of
course,
is
to
use
docker.
You
know.
That's
so
you
know,
say
you
have
a
you,
have
a
electric
car
and
it
has
a.
It
has
a
subsystem
that
come
from
a
different
manufacturer
that
controls
the
window,
for
instance
the
power
window
that
goes
up
and
down.
A
You
know
the
logic
of
how
the
window
goes
up
and
down
could
needs
to
be
run
inside
a
container
because
it
cannot
be
allowed
to
interfere
with
the
drive
training
system
or
the
autonomous
driving
system
or
the
braking
system
or
whatever
right.
You
know
that's
when
the
window
with
the
software
that
comes
through
the
window
crashes,
it
cannot
crash
the
car.
So
in
that
scenario
you
need
something.
That's
like
docker
right.
You
know.
A
That's
a
software
container
and
web
assembly
being
able
to
run
a
variety
of
different
hardware
and
operating
systems,
including
real-time
operating
system,
provide
a
very
good
candidate.
For
that
you
know,
that's
it
allows
those
those
the
integrated
system
inside
of
the
car
to
function
together
right.
You
know,
of
course,
there's
there
are.
There
are
blockchains
and
smart
contracts,
which
is
another
way
of
you
know
the
way
we
look
at
blockchain.
Smart
contracts
are
decentralized.
The
serverless
right.
A
You
know
it's
ver,
it's
the
development
paradigm,
exactly
like
serverless,
you
submit
a
piece
of
code
and
you
don't
care
where
it
is
wrong.
You
don't
care
who
the
machine
is
running
out,
but
it's
give
you
the
results
right.
You
know
that's
like
and
you
pay
for
the
result
and
they
accept
this.
In
this
case,
the
servers
are
not
run
by
a
cloud
provider
but
by
a
network
of
nodes,
decentralized,
node
right,
you
know,
so
so
all
those
use
case
scenarios.
A
Probably
not,
but
would
it
replace
docker
where
docker
cannot
go
today,
for
instance
on
the
edge
cloud
or
on
constrained
device
or
on
a
source
environment?
I
think
absolutely
you
know,
that's
there's
lots
of
use
cases
for
that,
as
we
see
here
so
the
benefits
of
webassembly
vm.
You
know
that's
because
here
so
it's
a
one
day
today,
so
I
assume
everybody
are
fairly
familiar
with
those.
You
know
first,
of
course,
there's
security,
especially
if
you
put
them
untrusted
code
like
we
talked
about.
A
You
know
if
you,
if
you
have
a
system
where
you
allow
people
to
upload
code,
and
you
run
it
on
their
behalf,
then
you
need
something.
You
need
a
sandbox
right.
That's
where
somebody
is
that's
what
a
web
server
is
for,
and
code
that
needs
to
access
hardware.
You
know,
that's,
you
know
the
iot
setting
or
you
know,
artificial
intelligence,
and
you
know
ai
inference,
setting
where
code
needs
to
access
specialized
chips.
That's
you
know,
that's
that
handles
air
work.
A
You
know
those
things
have
to
be
sandboxed,
so
you
can't
have
it
unrestricted
access.
That
would
you
know
that's
what
have
a
higher
probability
of
crashing
the
system.
You
know
it's
very
efficient
and
lightweight.
That's
what
it
designed
for
you
know
it's.
It
has
very
it.
It
actually
does
very
little.
It's
it's
a
it's
a
security
sandbox
and,
as
we
can
see
from
our
previous
and
you
know
the
performance
charts,
it's
has
near
native
performance.
It's
just.
A
It's
runs
as
fast
as
as
compiled
to
the
native
code
without
the
sandbox,
so
it
has
neonated
performance
and
due
to
its
dynamic,
perform
compiler
optimizers
such
as
aot
sometimes
can
even
exceed
native
performance.
You
know
that's
a
interesting
point.
I
wouldn't
expect
it
here,
but
if
you
read
our
paper
on
our
attribute
software,
you
see
a
discussion
of
it
why
the
aot
compilation
could
generate
code.
That
is
faster
than
native
code.
You
know
and
the
runtime
safety
you
know.
That's,
I
I
think
still
think.
Security
and
safety
are
different
things.
A
You
know
security
are
other
people
want
to
attack
you
safety
is,
you
know
the
bugs?
You
have
in
your
own
code
that
are
going
to
crash
the
system
right
in
the
portability
and
platform
independence.
Those
are
the
old
benefits
of
java.
You
know
the
benefits
of
it,
but
basically
any
software
vm
right,
you
know
that's,
you
know
it
allows
you
to
develop.
A
You
know
to
to
develop
one
machine
deploying
on
another
machine
of
a
different
operating
system
in
the
architecture
and
it's
especially
important
in
edge
computing,
where
there
are
so
many
devices
and
cpus
these
days.
You
know
it
used
to
be
the
x86,
it's
the
dominant
cpu,
on
the
server
side
right,
but
now
you
have
arm,
you
have
all
kinds
of
in
edge
environments.
A
You
have
all
kinds
of
chips,
so
you
know
so
it's
important
for
a
live
feed,
vm
web
assembly
to
run
all
those
those
hardware
configurations-
and
you
know,
and
and
and
it
allows
code
to
be-
to
be
written
on
a
developer's
machine
and
then
deploy
it
everywhere
across
the
edge
cloud
and
the
manageability.
You
know
that's
because
it's
a
container,
so
it
should
be
managed
and
orchestrated,
like
other
containers
by
things
like
kubernetes
and
or
cube
edge
on
in
in
the
edge
computing
work.
A
So
it's
automated
deployment
and
ops
you
know
needs
to
support
over-the-air
deployments.
You
know
hotspotting
with
zero
downtime.
So
you
know
that's.
If
you
update
the
software,
you
should
be
able
to
hotspot
it
in
and
out
of
the
software
module
with
no
downtime,
so
the
web
assembly
system
interface
is
called
wazi
and
that's
what
solomon
hack
is
talking
about
in
his
tweets,
and
this
allows
webassembly
not
only
to
interface
with
the
with
the
browser,
whereas
its
web
browser
it's
originally
designed,
but
also
with
the
operating
system
itself.
A
So
awesome
edge
is
open
source
project
that
we
donated
to
cnc.
It's
used.
The
commercial
version
is
called
ssvm,
second
state
vm,
and
it's
it's
completely
open
source
project.
We
developed
open
source
from
day
one
and
we
wrote
it
specially
optimized
for
server-side
and
you
know
edge
computing
use
cases
if
you
are
interested
check
it
out,
and
you
know
like
it
focus
and
you
know,
discuss
issues
with
us
on
github.
A
This
is
the
paper
that
we
published
on
itube
software.
That
shows
the
ssvm
is
is
already
one
of
the
fastest
web
assembly
runtimes
that's
available
in
the
market,
so
we
there's.
One
particular
thing
that
we
like
to
add
to
the
ssvm
in
context
of
serverless
functions.
Is
that
we
we
want
to
build
powerful
was
like
extensions.
You
know,
onesie
provide
access
to
the
host
operating
system
and
we
think
you
know
why
stop
has
left
c
and
I
and
the
the
operating
system
level
function
cost.
A
Why
don't
we
make
it
make
all
the
native
functions
available
to
wazi
and
through
a
very
organized
and
very
polished
api,
that's
available
as
a
rust
sdk
as
well,
so
we
can
do
tensorflow
inference,
which
I
wish
I
talked
about
in
another
talk
and
we
can
do
storage,
we
can
do
blockchain
stuff.
That's
you
know
access
instead
of
the
file
system,
the
blockchain
account
system
through
our
webassembly
runtime.
A
A
Well,
so
you
know
a
service
function.
Writing
web
assembly
is
really
simple.
You
know
here
is
a
here's,
a
complete
function.
You
know
it's
to
say
hello,
you
know,
let's
take
a
string
and
then,
if
you
read
a
little
bit
of
rust,
it's
it's
append
hello
in
front
of
the
string
and
it
returns
it
back
right.
The
one
I've
just
shown
is
a
service
function.
Where
you
can
you
can
access
your
url
right?
A
You
know
it's
a
service
function,
that's
on
the
back
end
of
the
jam
stack
application-
and
here
is
another
here-
is
another
example
that
that's
that
we
talked
about.
It's
a
is
a
chatbot
example
in
a
messaging
application
where
you
have
a
serverless
mode.
You
upload
a
piece
of
code
like
this
to
the
to
the
messaging
application
platform
and
then
specify
a
hook
to
say.
A
If
I
received
any
message,
call
this
function
and
it
will
tell
you
what
the
the
message
is
received
from
which
user
it's
come
from
and
they
ask
you
to
provide
a
response
right.
You
can't
you
provide
a
response
and
then
uploading
and
running
this
function.
You
don't
have
to
you
no
longer
have
to
run
your
own
server
and
do
the
api
calls
to
the
api
callbacks
for
to
extend
sas
applications.