►
From YouTube: Sponsored Keynote: WebAssembly: The future of distributed computing - Liam Randall, Wasmcloud
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.
Sponsored Keynote: WebAssembly: The future of distributed computing - Liam Randall, Founder, Cosmonic & co-Founder, Wasmcloud
Looking forward to the intersection of cloud, 5G, and IoT we are poised on the precipice of the next era of computing. In this talk Liam outlines the opportunities to drive the software and infrastructure of the near future - find out why the CNCF and Wasm are better together!
A
Hello
and
thank
you
for
coming
to
kubecon
eu
2021
wasm
day,
where
we've
been
spending
time
at
the
intersection
of
webassembly
and
everything
cloud
native,
a
tremendous
thank
you
to
chris,
a
elena
vogel,
the
cncf
staff
and
my
fellow
wasmday
program
committee
members
for
putting
on
an
incredible
event.
I'm
liam
randall,
and
for
the
last
couple
of
years
I've
been
working
on
a
distributed
application
framework
for
microservices
that
leverages
webassembly
called
wasmcloud,
and
today
I'm
going
to
share
our
perspective
on
webassembly
as
the
future
of
distributed
computing.
A
Let's
jump
right
in
webassembly
brings
some
powerful
value.
Propositions
to
any
domain
distributed
or
not,
people
are
excited
about.
Web
assembly
sometimes
referred
to
as
wasm
for
a
lot
of
reasons,
and
while
the
future
of
webassembly
is
simply
dazzling
today,
it
already
brings
a
lot
to
the
table.
First,
it's
efficient
and
fast.
It
runs
at
near
native
speed.
Second,
it's
safe
and
secure,
not
just
sandbox,
but
it
operates
in
a
deny
by
default
mode,
where
we
need
to
explicitly
grant
capabilities.
A
Third,
it's
open
and
debuggable.
Fourth
wasm's
polyglot
choose
your
own
language
and
you
can
bring
well-tested
libraries
to
a
new
domain.
Finally,
it's
portable
webassembly
is
a
compilation
target
and
it
runs
on
lots
of
different
things.
Servers,
browsers,
embedded
devices
heck.
You
can
even
put
wasm
inside
of
other
applications.
If
you
wanted
to
next,
let's
introduce
the
modern
distributed
computing
environment.
The
linux
foundation
edge,
has
helped
to
put
together
this
continuum
a
view
of
the
world
we
can
use
as
a
starting
point.
A
There
are
many
different
device
types
with
a
variety
of
system,
architectures
and
capabilities,
but
these
categories
actually
undersell
the
complexity
a
little
bit,
because
if
we
annotate
this
view,
just
ever
so
slightly
to
include
some
additional
context
with
some
of
the
platforms
that
are
both
incumbent
and
common
in
the
ecosystem,
we
get
a
more
complete
and
complicated
world
view
that
we
need
to
account
for,
for
example,
on
the
service
provider
and
public
cloud
edge.
We
of
course
find
kubernetes
in
both
regular
and
micro
sizes
and
we
find
applications
that
are
hosted
on
top
of
kubernetes.
A
So,
let's
pair
up
this
new
environment
with
our
current
evolution
of
technology,
now
over
the
last
30
years,
technology
has
continued
to
evolve
over
two
primary
dimensions:
the
formats
in
which
we
deliver
applications
and
the
orchestration
of
those
formats
into
a
specific
environment.
Now
this
picture,
all
the
green
is
provided
by
the
developer.
A
Building
the
apps
and
the
blue
is
the
platform
layer
and,
while
15
years
ago,
the
launch
of
the
public
cloud
ushered
in
its
own
revolution,
the
launch
of
docker
in
2013
and
kubernetes
in
2014
accelerated
the
pace,
and
now
today
we
find
ourselves
on
the
cusp
of
yet
another
revolution
with
webassembly.
As
we
can
see
over
time.
These
formats
have
gotten
simpler
and
more
decoupled
from
the
underlying
environments.
A
We're
moving
from
a
tightly
coupled
world
on
the
left
to
a
more
declarative
world
on
the
right
and
the
developer.
Responsibilities
continue
to
be
reduced
further
by
decreasing
the
number
of
things
that
they're
responsible
for
maintaining.
Let's
put
up
some
comparisons
and
see
what
really
stands
out.
If
we
start
to
line
these
technologies
up
side
by
side,
we
start
to
uncover
the
patterns
that
emerge
in
the
ecosystem.
A
Each
progressive
wave
has
further
decoupled
applications
from
their
underlying
architectures,
that
is
to
say,
with
each
format.
We've
carried
fewer
and
fewer
assumptions
forward
into
the
landscape,
and
we
see
this
reflected
at
both
the
where
our
formats
can
run
and
in
the
security
boundary
with
security
in
webassembly,
we've
moved
to
an
entirely
sandboxed
approach
and
we'll
review
the
deny,
by
default
explicit,
granting
granting
of
capabilities
shortly
and
the.
Where
is
part
of
the
reason
why
we
believe
that
webassembly
will
come
to
dominate
distributed
computing.
A
In
fact,
let's
take
these
two
world
views
and
put
them
together
by
observing
what
we
are.
We
are
already
seeing
across
today's
ecosystem.
We
have
compelling
evidence
that
wasm
today
is
on
the
path
to
becoming
the
critical
technology
leveraged
to
deploy
software
across
the
distributed
continuum
as
examples
starting
on
the
far
right.
We
see
native
execution
of
microservices
on
servers
with
frameworks
like
wasmcloud
in
research.
We
are,
we
are
already
seeing
webassembly
as
a
native
orchestration
technology
for
kubernetes,
with
microsoft's
crosslit,
the
kubernetes
rust
kubelet.
A
We
see
wasm
inside
embedded
inside
critical
technologies,
for
example,
both
oppa
and
envoy
are
leveraging
wasm
to
execute
untrusted
third-party
plugins,
where
previously
they
might
have
chosen
lua
or
javascript.
On
the
edges,
we
see
organizations
like
fastly
and
shopify,
using
wasm
as
a
deployment
platform
to
run
third
party
untrusted
code.
If
that
pattern
feels
familiar
get
used
to
it,
I
think
a
lot
more
organizations
are
starting
to
recognize
that
all
code
should
be
treated
as
untrusted
code.
A
We
see
thousands
of
examples
of
applications
running
in
browsers
on
mobile
phones,
on
tablets
and
in
web
browsers
everywhere.
Google
earth
uses
wasm
so
does
microsoft.
Flight
simulator
microsoft
even
makes
a
toolkit
that
leverages
web
assembly
in
the
browser
called
blazer.
The
anecdotes
are
one
thing:
what
are
the
real
challenges
of
this
distributed
environment
and
how
well
is
wasm,
actually
stack
stacking
up
now.
This
is
not
an
exhaustive
list,
however.
Today,
I
will
highlight
five
critical
challenges
to
be
solved
in
distributed
computing.
A
First,
the
diversity
of
system
architecture,
which
is
that
as
cloud
native
community,
we
are
no
longer
targeting
just
the
x86
monolith.
Cpu
memory,
functionality,
capability
and
os
are
all
in
variable
now.
The
second
great
challenge
will
be
the
diversity
of
application
architectures.
How
will
these
things
be
connected
in
the
near
future?
What
design
patterns
will
they
use?
How
will
they
speak
to
each
other?
The
third
will
be
our
approach
to
distributed.
Security.
A
Fourth
will
be
offline
use.
This
incredibly
diverse
ecosystem
will
be
running
loads
of
complex
software
and,
finally,
bringing
machine
learning
to
the
end
devices
to
make
them
intelligent.
Okay,
let's
just
make
them
less
dumb.
First,
both
the
number
and
incredible
diversity
of
devices
connected
to
the
internet
continues
to
simply
skyrocket,
as
we
head
towards
an
estimated
50
billion
connected
devices
in
2030
the
enterprise,
the
enterprise
integration
tasks
are
compounded
by
a
dozen
popular
and
incompatible
cpu
architectures,
each
of
which
has
its
own
relatively
unique
operational
life
cycle
from
dozens
of
major
manufacturers.
A
Webassembly
is
already
well
positioned
to
operate
well
in
this
complex
environment.
Wasn't
runtimes
can
even
be
optimized
to
adapt
an
application
for
specific
circumstances.
For
example,
the
bytecode
alliance
is
wasm
time
for
servers
and
their
wasm
micro,
runtime
or
whammer
for
short,
has
been
optimized
for
smaller
embedded
devices.
A
Surely
these
vast
collections
of
distributed
and
connected
ecosystem
systems
will
be
interconnected
in
tremendously
different
ways.
End
tier
applications,
model
view,
controller
pub,
sub
microservices
and
more
today
we
already
see
webassembly
running
on
embedded
into
and
running
around.
Our
software
stacks
wasm
excels
here
as
well.
Its
near
native
performance
makes
it
ideal
for
standalone,
embedded
or
other
types
of
integrations.
As
a
component.
We
already
have
many
large
scale
examples
of
webassembly
running
in
complex
stacks.
A
A
Webassembly
itself
functions
as
a
sandbox
helpful
when
you
want
to
adapt
or
bring
code
to
a
huge
variety
of
complex
systems
and
webassembly
brings
to
the
ecosystem
a
powerful
approach
to
capability-based
security.
If
you
think
back
not
that
long
ago,
when
you
started
a
child
application,
it
usually
inherited
the
rights
of
the
parents.
So
if
I
could
write
or
read
to
disk,
then
so
could
my
child
process.
A
In
more
recent
years,
however,
nearly
every
industry
has
started
to
migrate
to
a
capabilities-based
approach,
where
an
application
must
be
explicitly
granted
access
to
a
capability
in
order
to
use
it
with
webassembly.
The
combination
of
a
sandbox
and
deny
by
default
approach
means
that
it's
more
difficult
to
abuse
and
compromise
your
applications.
A
Real
complex
logic
will
need
to
live
on
the
device
because,
for
a
few
reasons,
first
latency
and
determinism,
for
example,
driverless
cars
need
to
react
instantly.
Second,
large
data
must
first
be
processed
where
the
data
resides
at
the
devices.
Perhaps
an
ml
model
extracting
metadata
to
be
shipped
back
back
to
the
public
cloud.
A
A
Finally,
regulatory
gdpr
and
ccpa
are
the
start
of
things
to
come.
Big
tech
is
going
to
be
further
regulated
in
the
future,
and
this
will
impact
the
where
and
how,
in
the
design
of
our
distributed
software
systems.
What
this
means
is
that
these
50
billion
connected
devices
by
2030
will
amplify
our
workloads.
These
devices
may
be
small,
they
may
be
cheap,
but
they
will
be
increasingly
intelligent
and
complex.
A
For
the
aforementioned
reasons,
web
assemblies
write
once
run
everywhere.
Security
model
and
portability
are
sure
to
come
into
play.
Finally,
one
overarching
theme
of
iot
will
be
making
all
the
dumb
things
in
our
life.
Smart
tuning
and
optimizing
models
is
difficult
enough
without
having
to
worry
about
the
differences
between
hundreds
of
potential
different
deployment
chipsets.
Even
today.
A
Incredibly
compelling
work
is
coming
out
of
the
google
tensorflow.js
team,
where
they
are
compiling
ml
models
for
use
in
the
web
browser
running
and
leveraging
the
speed
and
performance
of
webassembly
in
the
browser
and
andrew
and
sun
over
on
the
intel
team
have
already
ported
their
wazi
nn
machine
learning
framework
to
wasm
time
as
an
experiment.
I
can
imagine
a
near
future
where
these
models
are
run
throughout
the
distributed
continuum.
A
I
hope
you
have
found
today's
talk
about
distributed
systems
interesting
and
informative.
If
you
care
about
these
topics
as
much
as
we
do,
I
hope
you
will
follow
along
as
we
build
an
enterprise
solution
to
help
developers
navigate
these
complex
opportunities,
join
us
working
on
wasm
cloud,
our
open
source,
distributed
application
runtime
for
the
enterprise
or
for
more
information
on
future
enterprise
offerings
sign
up
for
our
early
adopters
program
at
cosmonic.com.