►
Description
Wasm Beyond the Browser: Use Cases at Scale - Colin Murphy & Sean Isom, Adobe
Adobe makes use of Wasm in its flagship web browser-based products including Photoshop, Lightroom, and Acrobat. This past year it has explored potential use cases for Wasm in edge compute and in the datacenter with wasmCloud. Of particular interest were the potential performance, cost, security, and compliance benefits. Wasm and WASI have many potential advantages over Docker and standard web frameworks in these areas, but what needs to be done to realize those benefits at Adobe? This presentation begins with a summary of Adobe's current use cases, including the toolchains employed and major implementation challenges. It then proceeds to an exploration of CDN edge compute and Wasm/WASI platforms, compelling application and platform features for Adobe, and a demonstration of proofs of concept. It concludes with future looking platform requirements and how Adobe expects to take advantage of this technology at scale moving forward.
A
This
is
a
this
is
a
customer
story
and
it's
it's
a
little
different
because
I've
given
this
sort
of
talk
to
a
lot
of
people
at
adobe,
and
I
have
to
kind
of
talk
for
20
minutes
about
what
web
assembly
is
and
so
kind
of
trying
to
invert
it.
I've
also
like
been
aggressively
pruning
as
the
day
goes,
and
people
cover
things
that
I
would
have
covered.
I
also
want
to
set
your
expectations
low
and
I
don't
want
to
do
too
good
of
a
job
because
ranu
he
gets
really
stressed
out.
A
A
It's
not
like
you
know,
microsoft
or
something,
but
there's
a
lot
of
there's
a
lot
to
it
and
it's
hard
to
kind
of
come
at
people
with
how
application
what
application
should
look
like
how
we're
going
to
compose
applications,
because,
where
they're,
where
they're
coming
from,
if
they're
front
end
right,
then
they're
thinking,
oh,
I
know
web
assembly
and
and
they
don't
right
not
in
the
context
of
wazi
and
all
that,
their
back
end
and
they're
like
well.
I
know
docker
and
you
know
I
don't
want
to
you
know.
A
Don't
don't
bother
me
right.
I
just
want
to
write
my
javascript,
my
java,
my
you
know
my
spring
boot
apps,
so
it's
kind
of
like
docker
and
it's
like
it's
not
really
like
docker
and
then
edge
computes
still
really
early
on,
and
so
but
but
I
think,
that's
kind
of
the
whole
point
is
that
you
have
to
kind
of
consider
it
as
a
way
of
composing
an
application
really
from
beginning
to
end
so
yeah.
A
I
actually
was
responsible
for
document
clouds,
infrastructure
and
developer
experience
for
the
microservices,
so
adobe
sign
acrobat
kind
of
how
kubernetes
was
laid
out
how
people
did
see
icd
what
their
spring
boot
apps
looked
like
all.
That
kind
of
there
was
a
lot
to
it
and
I
I
recently
switched
over
to
creative
cloud
web
kind
of
a
career
limiting
move,
perhaps,
but
I'm
I'm
now
just
like
a
sub
average
javascript
developer
and
sorry.
So
so
there
is
a
lot
going
on
surplus
plus,
there's
there's.
A
Performance,
optimized,
storage
from
origin,
private
file
system.
There
was
a
lot
of
work
done
in
order
to
get
photoshop
working
in
the
browser.
So
I
don't
know
if
you
all
are
aware,
but
there's
photoshop
in
the
browser
now
acrobat
has.
If
you
use
the
web
version
of
acrobat,
then
you'll
see
there
there's
well,
you
would
there's
a
lot
of
web
assembly
there
as
well
and
but
really
the
whole
purpose
of
webassembly
in
the
front
end
for
adobe.
Is
we
have
a
lot
of
c
plus
plus
code?
A
We've
had
a
lot
of
c
plus
plus
code
for
decades,
and
we
want
to
use
that
in
the
browser
right.
We
want
to
have
good
browser
experiences,
but
that's
not
really
applicable,
because
none
of
that
stuff's
going
to
work
right.
You
know
in
wazi
none
of
that
stuff's
going
to
work
without
without
that
javascript
calling
the
making
the
system
calls
but
kind
of
the
nice
thing
is
at
adobe.
We
have
a
really
positive
appreciation
for
webassembly.
If
you
say
webassembly,
you
know
that
that
gives
really
high
high
high
marks.
A
Any
of
any
rating
had
to
be
reported
to
our
sponsor,
and
so
I
don't
know,
if
you
don't
know
if
anybody
here's
run
kubernetes,
but
you
end
up
using
a
lot
of
third-party
images
and
if
you're
fairly
sophisticated,
you
have
lots
of
controllers,
and
you
know
you've
you've,
you
think
you've
done
a
great
job
covered.
All
your
bases-
and
you
end
up
with
thousands
of
cves
and
you'll-
have
one
lib
c
vulnerability
from
you
know,
2013
that
nobody
thinks
is
important.
A
That'll
get
flagged
in
ubuntu,
red
hat
and
maybe
alpine
so
they've
got
that's
three
cvs
right
there
that
no
one
has
ever
any
intention
of
ever
fixing.
So
so
you're
going
it's
going
to
be
difficult
for
you
to
get
through
a
fedramp
audit.
If
you
use
lots
of
docker
images,
you
actually
have
three
options:
one.
You
can
start
paying
people
money.
So
if
you
use
istio,
you
can
start
paying
a
solo.
A
I
o
a
bunch
of
money
or
maybe
not
too
much,
but
it
can
get
pricey
and
you
can
fork
all
of
these
third-party
projects,
which
is
a
lot
of
fun
or
you
can
just
cut
them
out
all
together
and
that's
really
what
we're
faced
with
and
it
was.
It
was
painful
and
it's
kind
of
still
painful.
So
anyway,
I'm
you
know
we're
kind
of
reaching
the
end
of
our
challenges.
This
cbe
thing
is
terrible,
and
so
I'm
I'm
just
kind
of
looking
around
and
seeing
like.
A
And-
and
you
know,
this
is
kind
of
the
problem
we've
had.
I
think
we've
said
it
before
I
was
talking
about
heroku
earlier
right
is
or
java
javascript
unix
wars
right,
glib
c
right.
We
want
stuff
that
can
be,
can
be
used
in
lots
of
different
places,
and
that's
that's
like
well.
This
is
kind
of
the
ideal
right
software
developers,
they
write,
they
understand
the
business
logic
and
then
they
don't
have
to
worry
about
how
it
gets
deployed
or
what
what
all
the
all
the
things
they
don't
have
to
care
about.
A
Yeah,
so
so
this
is
kind
of
like
so
I'll
get
there
I'm
going
to
demo
that,
but
so
what
this
is
kind
of
my
initial
impression
like
okay
web
assembly,
so
I
don't
have
to
have
the
I
don't
have
to
have
the
operating
system.
That's
in
docker
right,
I
can
have
it
be
really
fast.
It's
going
to
be
much
better
than
I
mean
I'm,
comparing
it
to
the
jvm,
I'm
comparing
it
to
spring
boot.
A
So
it's
it's
a
low
bar
right
in
terms
of
startup
time
say
or
memory
footprint
and
also
compliance
is
really
big.
We're
everything's!
You
know
we
had
a
lot
of
hipaa
fed
ramp
sock
tube
pci,
so
these
were
kind
of
like
okay.
This
is
going
to
be
great.
I'm
going
to
I'm
going
to
do
this,
and
maybe
we
can
just
run
it.
You
know
like.
Maybe
we
can
start
moving
people
over.
A
And
oh
yeah
and
of
course
right
is
the
spend
so
so
we
once
again,
you
know
somebody
adobe
might
find
out
about
this
conference
and
I'm
actually
kind
of
like
you
know
you
like
it's
kind
of
tongue-in-cheek,
because
we
we
do
get
a
lot.
I
do
get
that
question
fairly.
Often
what
is
cncf
you
know
so,
but
it's
a
lot
and
I
can't
say
how
much
it
is,
but
it's
a
lot
okay.
So
this
is
what
I
did.
A
I
we
have
this
really
simple,
javascript
app
that
you
give
it
an
image
and
it
removes
the
background
not
too
hard.
I'm
sure
you
guys
could
figure
out
how
it's
kind
of
done,
but
very
trivial
and
then-
and
I
just
wanted
to
see-
if
I
could,
if
I
could
run
it,
I
did.
I
did
fastly
cloudflare
browser
and
server
side
so
time
for
demo.
A
Because
it's
actually
going
to
run
it's
actually
going
to
run
inside
as
I
move
it
over.
Oh
here
we
go
there.
We
go
all
right,
didn't
want
and
okay
so
mac.
What
was
that
that
was
awful?
What
happened?
Click
click,
okay,
all
right!
So
so
here
we
go
so
this
is
actually
going
to
run
inside
inside
kubernetes,
which
is
pretty
cool,
so
this
runs
inside
our
actual,
like
adobe
kubernetes,
so
I've
I've
written
I've
written
out
this
business
logic
and
I'm
just
going
to
import
it
into
wasmcloud.
I
picked
wasmcloud.
A
A
A
A
A
And
yeah
it's
kind
of
slow.
Is
it
like
one
and
a
half?
Okay,
so
yeah,
so
really
not
hard
pretty
easy.
Once
you
get
the
once,
you
write
your
app,
you
can
run
it
on
wasm
cloud
in
kubernetes.
You
can
run
it
on
cloudflare
and
then
then,
actually
that's
the
end,
and
then
I
so
so
what
actually?
What
happened?
Was
this
got
put
into
the
product
and
so
like?
The
next
thing
is
showing
the
beta
version
of
the
product.
I
can't
show
so
so
I'll.
Just
I.
I
will.
A
A
A
A
A
A
Really
come
on,
drag
and
drop,
drag
and
drop.
Okay,
oh
okay!
Okay,
if
you
drag
and
drop,
you
get
the
same
response,
so
it
works
in
all
three
places
really
like.
I
guess
I
need
to
bring
a
mouse
next
time.
Thanks,
trackpad,
okay,
I
don't
know,
I
don't
know
what
to
tell
you.
If
you
could
drag
and
drop
in
a
ui,
then
I
could
show
you
that
I
can
drag
and
drop
this
file.
Oh
yeah,
thanks,
okay!
Well,
you
can't
you
can't
because
matt
can't
come.
I
can't
handle
this.
A
A
That's
a
demo
and
that
was
actually
pretty
cool
and
of
course
I
showed
this
to
people
and
they're
like
oh,
we
can
just
run
in
the
browser
great
and
that's
that's
that's
what
most
people
took
out
of
that,
but
and
it
actually
did,
it
actually
is
going
to
be
put
into
the
product
to
replace
something.
You'll
never
notice,
but
so
now
that
will
be
done
in
the
browser
next
demo.
A
Next
demo,
I
was
afraid
this
is
going
to
be
too
short.
So
that's
where
we
are
now
it's
excruciatingly
long,
all
right!
So
next
thing
was
cloudflare.
Has
this
thing
this
this
kind
of
it's
this
cloudflare?
I
was
really
impressed
with
this
was
a
it
was
hard
to
type
up
here,
all
right,
local,
okay,
yeah,
all
right.
A
Oh,
wait
has
cloudflare,
has
durable
objects,
and
this
was
a
big
thing
that
I
was
interested
in,
because
when
I
was
joining
my
team,
it
was
about
you
know,
collaborative
editing
and
stuff
like
that,
and
so
I
was
like
okay,
I'm
going
to
see
what
collaborative
editing
is
editing
is
like
and
and
so
what
you
could
do.
I
thought
this
was
really
cool.
Is
you?
Can
they
have
these
things
called
durable
objects?
A
A
So
right
so
yeah,
okay,
so
here
we
go
two
browsers
and
I
thought
this
was
cool.
So
if
I
open
up
this
and
and
what's
really
cool
right
from
a
application
perspective
is
that
this
is
actually
happening
in
valencia
right.
So
I
I
do
something
in
one:
it
affects
the
other,
so
it's
web
hooks.
I've
got
a
session
with
cloudflare.
I've
got
web
hooks
sending
down,
so
you
people
can
co-edit
right.
A
I
thought
this
was
really
powerful
and
this
is
really
tiny
and
this
is
rust
and
web
assembly,
so
that
was
that
was
also
really
cool
and
it
was
before
I
joined
the
team,
so
it
has
no
nothing
to
do
with
what
adobe
actually
does.
I
thought
that
was
really
cool
and
then
the
last
one
is
the
last
one
is
christoph
bruving.
A
He
was
here
yesterday
but
he's
from
bmw
and
he
came
up
with
a
wasm
cloud,
onyx
and
tensorflow
inference,
and
so
that
actually
is
something
when
I
was
going
around,
I'm
not
gonna.
I
was
talking
to
people
and
they're
like
well.
You
know
we
have
this
really
heavy
compute
thing
that
sounds
like
it
would
be
good
for
wasm
right
and
it's
like
well,
you
know
actually
multi-processing,
not
so
great
in
wasm,
so
no
and
the
other
one
was
well.
We've
got
these
these
all
these
machine
learning
models.
A
That's
probably
the
most
compelling
use
cases
right
here
because,
let's
say
actually,
if
you
have,
if
you
have
acrobat
on
your
phone
and
you
open
a
pdf,
it
will
actually
run
and
run
it
run
it
through
a
machine
learning
inference
and
it
will
reposition
the
text
and
images
and
it'll
all
show
up
nicely
on
your
phone.
But
the
problem
is
that
you
need
to
have
a
nice
phone
for
that
to
work
for
you
and
if
you
don't
have
a
nice
phone.
Hopefully
this
is
okay
to
mention
you
know.
A
Sometimes
that
has
to
be
done
somewhere
else,
so
that
has
to
be
done
on
server
side.
So
if
you
could
run
it
all
at
the
edge
in
all
the
major
cities
around
the
world,
that
would
be
a
big
big
win
right,
and
so
so
so
this
is
so
I
don't
know,
bmw
must
need
it
for
cars
or
something,
but
we
you
know
adobe,
and
probably
lots
of
people
like
adobe
could
really
take
advantage
of
this.
A
Hopefully
all
right
there.
It
goes
okay,
cool!
So
so
there
we
go.
So
that's
actually
running
machine
inference
on
my
local
host,
but
that's
that's!
The
kind
of
thing
we
need
is
to
be
able
to
run
onyx
models
or
tensorflow
models
at
the
edge.
Of
course,
it's
not
running
at
the
edge
it's
running
on
my
laptop
but
same
idea,
so
that
that
really
the
and
the
problem
we're
really
trying
to
solve
there
is
that
you
have
an
onyx
model
or
tensorflow
model.
A
A
Okay,
so
yeah,
and
so
that
last
one
I
I
didn't
have
much
to
do
with
that
was
that
was
christopher,
bruving
and
steve
schutler
from
steve
schulte
from
cosmonaut,
who
did
most
of
that,
but
that
was
a
actual
adobe
use
case,
so
yeah,
so
so
pretty
quickly,
and
this
is
something
you
know
if
you
have
customers
if
you're
writing
a
platform
and
you
have
customers
things
to
make
sure
they
understand
right.
So
if
they've
got
stuff
working
in
v8
it
doesn't
it's
not
a
it's,
not
gonna.
A
Necessarily,
it's
probably
not
gonna
work
in
wazi
and
then
there's
all
these
things.
Like.
Oh
here's,
an
image,
here's
some
machine
learning.
Could
you
run
that
here's
some
here's
just
a
simple
image,
manipulation,
tesseract
library,
nope
right?
No,
it
doesn't
work.
The
other
big
thing
is:
there's
no
doubt
right
that
wasn't
that
a
wasi
based
workload
is
going
to
run
much
faster
than
java,
but
you
know
what
else
runs
much
faster
than
java,
especially
in
starting
up
anything
else,
and
yet
people
use
it
right
and
right.
A
I
mean
people
still
use
java
in
docker
containers
at
a
massive
scale,
so
the
whole
like.
Well,
it's
going
to
be
faster
and
cheaper,
and
you
know
you're
going
to
save
money
doesn't,
for
you
know,
doesn't
work,
it's
not
a
valid
argument,
and
so
so
you
have
to
kind
of
like
next
level
right
like
well.
It's
going
to
let
you
do
things
you
couldn't
do
before,
because
you
know
the
thing
is:
if
you
have
hundreds
of
thousands
of
engineers
and
they
all
write
java,
that's
going
to
take
a
really
it's
going
to.
A
A
I
know
that
we
kind
of
got
it
working
in
the
browser
with
the
dynamic
threads,
but
sooner
the
better
on
on
how
to
kind
of
get
around
that
problem,
and
also
the
other
big
thing
is
that
it's
it
doesn't
it's
a
major
major
shift
in
thinking
so
and
of
course
it
has
to
work
in
kubernetes,
because
that's
what
people
run
right
until
you
have
something
where,
where
you
know
really
next
level,
where
it's
like.
Well,
it's
in
the
data
center
and
it's
everywhere
right.
A
It's
in
your
you
know
local
cell
tower
people
are
going
to
want
it
to
run
in
kubernetes,
and
so
this
is
from
taylor.
I
don't
know
if
taylor's
still
here
thanks
taylor,
thanks
for
this
diagram
taylor,
but
it's
hard.
It's
it's
a
lot,
and
but
actually,
what's
really
cool
here
in
washington
cloud.
If
you
notice
is
that
you
can
connect
to
aws
resources.
So
that's
that's
another
must-have
right,
aws
and
azure
microsoft.
People
make
sure
that
you
know
have
some
sort
of
identity
system.
A
A
I
aws
azure
has
to
have
some
sort
of
identity
tie-in,
so
we
actually
for
fedramp.
We
had
to
use
we.
We
went
with
spiffy
for
certain
identities.
That
kind
of
thing
like
people
have
spent
a
lot
of
time
and
money
working
on
solving
problems
with
this
stuff.
So
it
has
to
still
use
this
stuff
and,
of
course,
the
machine
learning
super
super
important,
because
companies
have
spent
a
lot
of
money
on
machine
learning.
A
I
don't
know
if
you
noticed
you
know,
there's
there's
a
lot
of
a
lot
of
work
being
done
on
machine
learning,
and
sometimes
you
know,
and
sometimes
it
pays
off,
so
they
want
to
keep
that
stuff
and
once
again
I
know
bailey
started
us
off
with,
like
people
have
this
misconception
about
rust,
but
he's
like
yeah.
If
you're
gonna
start
greenfield,
you
should
ride
in
rust.
A
We
obviously
adobe
uses
cd
plus
plus
for
all
of
its
web
assembly,
but
and
then
the
other
thing
is
that
for
reasons
that
I
don't
really
quite
understand,
but
I
have
pretty
good
ideas
about
the
large
you
know.
Infrastructure,
as
a
service
providers
are,
are
a
little
behind
the
eight
ball
on
this
stuff.
I
think
it's
because
you
have
these
different
silos
and
you
know
going
back
to
the
first
slide
right.
A
It's
a
lot
of
stuff
kind
of
converging
in
one
place,
and
so
at
these
big
you
know
what
I
mean
these
big
cloud.
Vendors
they've
got
lots
of
silos
and
it
it's
really
well.
Is
it
lambda
ed
edge
right?
Is
it
lambda?
Is
it
the
iot
people
right?
I
don't
know
if
they,
those
people
talk
to
each
other,
but
so
I
think,
there's
a
real
opportunity
for
a
lot
of
you
here
to
to
challenge.
A
You
know
to
really
carve
a
niche
here
and-
and
you
know,
take
care
of
that.
Take
advantage
of
the
portability
make
something
that's
really
everywhere
at
one
time.
So
what
time
am
I
about
done,
5,
15.,
so
so
yeah.
So,
anyway,
to
sum
it
up
edge
workers,
I'm
I
think
this
is
really
the
time
is
now
this
stuff's
really
ready
to
go.
I
think
you're
gonna
see
a
lot
of
people
using
this
enough
very
soon.
A
Then
there's
going
to
be
a
lot
of
adoption,
I
really
like
durable
objects.
I
know
it's
not
going
to
work
at
an
open
source
conference,
but
I
guess
the
way
it
would
work
is
durable.
Objects
are
good.
Let's
make
an
open
source
version
of
them.
How
about
that
server-side
webassembly,
I
think
I
mean
so
so
yeah,
so
it
works
for
the
really
trivial
cases
and
it's
kind
of
it's
gonna
work
really
soon
for
more
complex
cases,
but
it's
still
it's
still
kind
of
challenging.
A
A
And
you
know
I
mean
this
was
true
a
year
ago.
It's
it's
less
true
now,
but
but
I'm
really
looking
forward
to
the
future
of
of
kind
of
a
seamless
experience.
I
think
we,
the
last
talk
kind
of
talked
about
that
so
and
it's
definitely
going
to
be.
It's
definitely
going
to
be
a
thing.
Wasm
will
be
a
major
player
on
the
server
side.
For
what
you
know,
that's
my
two
cents,
all
right.
So
that
is
all
thank
you
very
much.