►
From YouTube: Sponsored Keynote: The Next Epoch of Technology: Wasm & Actors - Liam Randall, Founder, Cosmonic
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. 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: The Next Epoch of Technology: Wasm & Actors - Liam Randall, Founder, Cosmonic
The last 20 years of technology have been defined by the rise of dominant abstractions of technology. Virtual machines freed us from the constraints of a specific computer with portable machine images, containers freed us from a specific Linux distribution giving us portable environments, and Kubernetes frees us from a specific cloud giving us portable workload orchestration. The next great abstraction is the application library - freeing us from the constraints of a specific implementation and services. In this talk we will highlight the emerging opportunity and advantages of abstracting away from specific cloud capabilities to actor models.
A
Well,
good
morning,
everyone
and
thank
you
for
attending
the
2021
cncf
kubecon
north
america
cloud
native
wasm
day,
which
is
quite
the
mouthful
on
behalf
of
both
the
program
committee
and
all
of
our
gender
sponsors.
It's
my
sincere
pleasure
to
welcome
you
to
those
of
you
that
are
here
in
los
angeles,
and
certainly
all
of
you
that
are
watching
on
home
or
later
online.
A
My
name
is
liam
randall,
I'm
the
founder
of
cosmonic
and
a
long
time
cloud
native
participant
and
enthusiast.
I've
worked
with
a
number
of
large
organizations
to
put
different
technologies
into
the
cncf,
I'm
a
big
believer
in
the
power
of
open
source
and
the
power
of
community.
To
make
a
difference
and
to
echo
ralph's
theme.
Today's
story
is
really
about
us
all,
working
together
to
make
the
future
better
together.
A
So
let
us
begin
with
where
cloud
native
development
is
today.
This
is
by
some
measure,
the
third
great
epic
of
computing
in
the
last
20
years
in
the
first
organizations
race
to
digitize
their
cores
and
business
processes.
In
this
age,
dominated
by
vendors,
such
as
sun
dell
and
microsoft,
applications
were
tightly
coupled
with
a
specific
piece
of
hardware.
I'm
sure
many
of
us
are
old
enough
to
remember
specking
out
a
specific
perc
6
raid
controller
to
run
our
applications.
A
Innovations
in
both
cpu
architecture
virtualization
and
a
desire
for
more
efficient
utilization
led
us
to
the
second
epic.
The
virtual
machine
rose
to
prominence
prominence
to
bring
elasticity
and
optimization
to
the
utilization
of
the
underlying
hardware
and
is
first
dominated
by
vmware
and
later
by
the
public
cloud.
A
The
second
epic
of
computing
began
and
the
security
boundary
was
moved
from
the
physical
boundary
of
the
machine
up
to
the
shared
cpu,
and
while
different
public
clouds
emerged
with
their
own
unique
approaches
to
the
segmentation
and
boundary
the
elasticity
of
the
cloud
accelerated
this
transformation
and
in
building
and
managing
these
applications.
The
the
literal
pain
of
managing
unique
individual
hosts
drove
the
creation
of
the
third
major
epic
of
computing.
A
A
So
let
us
consider
for
a
moment
what
this
modern
cloud
native
computing
environment
looks
like
if
we
find
this
ever
expanding
elastic
edge
or
this
new
cloud,
as
ralph
just
mentioned,
redefining
both
how
we
need
to
build
our
applications
and
where
they
will
need
to
run
the
crisp
boundaries
between
clients
and
servers
are
fading
to
peer-to-peer,
and
probably
the
largest
question
is,
is
where
will
the
execution
need
to
live?
Can
all
the
things
in
the
far
left
of
this
image
be
dumb
terminals
and
all
the
things
on
the
right
hold
our
logic
and
execution.
A
The
client
server
approach
is
somewhat
dominant
way
of
thinking
about
computing,
and
this
entire
week
is
full
of
approaches
to
this
problem,
to
take
what
we
do
in
a
cloud-native
way
and
to
simply
pull
it
towards
some
lower
bound
and
this
works
and
will
work,
but
only
to
some
lower
bound
as
our
desire
to
move
execution
close
to
the
user
transcends
the
traditional
boundaries
that
define
cloud
native
itself.
We
find
environments
and
assumptions
where
the
dependence
on
both
linux
and
kubernetes
just
no
longer
hold,
certainly
in
the
web.
A
Browser
itself
or
in
the
venerable
iphone
will
not
run
either
kubernetes
or
containers
and
now,
just
as
I've
said
that
I'm
sure
some
stunt
hacker
is
going
to
figure
out
a
way
to
run
kubernetes
inside
of
your
browser.
But
do
we
really
want
to?
I
think
you
understand
my
point
now,
as
we
consider
where
execution
will
run.
Ralph
mentioned
that
article
that
I
wrote
recently
around
the
webassembly
being
the
future
of
distributed
computing.
A
A
Large
data
processing
means
that
we
want
to
put
the
computing
as
close
to
the
users
and
the
edge
and
the
data
as
possible
for
privacy
and
security
reasons
in
cases
where
we
want
limited
or
deliberate
autonomy,
drones
manufacturing
my
refrigerator
if
it's
disconnected
from
the
core,
it
better
still
work
as
intended.
And
finally,
I
think
the
sleeper
reason
will
be
regulatory
governance,
compliance
those
reasons
when
you
think
about
ccpa
and
gdpr.
A
So
if
we
accept
that
in
the
future,
if
that
the
future
is
distributed,
then
we
are
faced
with
a
plethora
of
distributed.
Computing
challenges,
the
diverse
cpu
system,
architecture
rising
not
only
across
the
edge,
but
in
the
core
of
the
public
cloud
itself
and
in
a
world
where
everything
has
capabilities
and
we
face
new
application,
architectures
such
as
peer-to-peer
and
locality-based
computing.
A
A
This
entire
stack
needs
to
involve
it
to
evolve.
So,
let's
walk
through
these
three
great
challenges
that
are
facing
the
modern
distributed
computing
landscape,
so
the
first
is
pretty
straightforward.
This
is
portability
with,
as
ralph
mentioned,
with
an
estimated
30
billion
internet
connected
devices.
This
is
part
of
the
hyper
theme
that
will
define
both
the
challenges
and
the
opportunities
we
face
over
the
next
20
years,
with
dozens
of
manufacturers
and
hundreds
of
cpu
os
and
microcode
options.
We
see
clear
opportunities
for
webassembly
here.
A
What
may
not
be
as
self-evident,
but
is
probably
more
important,
is
that
the
diversity
of
cpu
architecture
is
rising
not
just
on
the
elastic
edge,
but
in
the
core
of
the
public
cloud
itself.
Individual
companies
like
excuse
me
aws
and
apple
rolling
their
own
silicon
is
the
heartbringer
of
things
to
come,
as
nation
states
and
other
companies
continue
to
recognize
the
power
and
security
risks
associated
with
the
digitization
of
our
lives.
I
strongly
expect
us
to
continue
to
see
the
balkanization
of
the
computing
landscape,
expect
more
companies
and
more
countries
to
follow
suit.
A
This
is
not
a
new
concept.
My
fellow
linux
security
nerds
will
no
doubt
remember
pseudo
pseudo
setcap
for
granting
privileges
at
the
command
line,
but
web
assembly
strong
capability
driven
security
is
certainly
a
good
approach
for
us
moving
forward
for
the
so.
For
the
second
grade
challenge
we
have
another
great
fit
with
web
assembly.
A
A
A
These
are
examples
like
a
specific
database
that
might
bind
you
to
a
specific
cloud
provider
at
a
specific
time
or
specific
device
on
the
edge
or
a
message
queue
or
a
key
value
store.
Now
the
real
dirty
secret
of
modern
cloud
native
development,
it's
that
enterprise
apps
are
primarily
composed
of
non-functional
requirements.
A
The
private
analysis
that
I've
seen
at
data
at
large
scale
of
applications
is
is
that
in
many
cases,
95
of
an
application's
code
satisfies
the
non-functional
requirements,
and
this
is
a
pernicious
risk
to
operating
applications,
never
mind
operating
applications
across
a
distributed
edge
because
the
consequence
is
painfully
emerged
throughout
the
life
cycle
of
creating
building
operating
and
maintaining
these
applications
from
design
to
deployment
to
management
to
scale
in
the
most
painful.
To
maintain
all
of
those
non-functional
requirements
across
a
distributed.
A
A
So
if
we're
to
take
flight
and
to
dance
across
this
distributed
landscape,
then
we
need
to
solve
this
final
opportunity
now.
Those
of
you
that
know
me
know
that
I've
been
working
on
a
project
with
kevin
hoffman
called
wasmcloud
for
the
last
few
years.
This
is
both
compatible
with
the
current
cloud
native
stack,
but
not
dependent
upon
as
wasmcloud
combines
an
actor
model
with
wasm
to
run
everywhere
securely,
but
there
are
other
approaches
to
this
model
as
well.
Microsoft's
dapper
project,
which
they've
put
into
the
cncf,
also
embraces
this
sort
of
abstraction.
A
So
the
difference
is
primarily
that
we're
solving
similar
problems
with
different
opinions,
but
the
idea
remains
true
that
we
need
to
break
the
tight
coupling
of
applications
to
libraries
now
in
the
wasm
cloud
context,
we
really
want
to
flip
the
model
we
want
it.
We
give
you
this
actor
construct.
That
gives
you
the
ability
to
build
applications
that
are
95
application
logic
and
only
5
non-functional
requirements,
letting
you
defer.
The
binding
of
those
capabilities
to
runtime
and
dapper
offers
a
similar
approach
in
computing.
A
A
That's
the
world
that
we
live
in
now
so
by
working
together
to
solve
the
great
challenges
facing
cloud
native
computing
today
around
portability,
security
and
capabilities,
I'm
confident
that
we
can
make
progress
together.
Thank
you
very
much
for
your
time
and
for
more
information
about
enterprise
offerings
in
this
space.
Please
visit
us
at
cosmonic.com.