►
Description
wasmCloud is a platform for writing portable business logic that can run anywhere from the edge to the cloud, that boasts a secure-by-default, boilerplate-free developer experience with rapid feedback loop.
A
B
Hey
thanks
liam
so
quick
background.
Essentially
the
idea
was
to
port
the
the
web
assembly,
the
wasm
cloud
host
into
a
browser
environment
where
we
can
launch
actors
inside
a
browser,
link
them
to
a
provider
outside
of
running
outside
of
the
outside
the
browser
and
then
be
able
to
invoke
the
the
running
actor.
That's
inside
the
browser
and
pass
the
message
back
and
everything
is
connected
through
nets.
B
B
So
the
wasm
cloud,
js
module,
is
pretty
much
global
to
the
page,
because
I'm
running
the
compiled
output
so
essentially
there's
one
main
method
and
it's
called
and
it's
an
async
function.
So
you
have
to
do
the
await
and
it's
called
start
host,
which
will
start,
which
will
essentially
start
the
browser
host
and
the
parameters
are
the
host
name,
whether
or
not
you'll
be
using
tls
with
the
with
your
docker
registries.
B
Just
because,
if
you
are
using
tls
you'll
have
to
configure
the
course
options
and
then
the
third
parameter
is
a
series.
It's
either
an
array
of
of
nats
nats
host
names
or
you
can
pass
in
and
that's
connection
object
for,
like
authentication,
tls
and
whatever
other
options
that
that
supports,
and
then
there's
a
couple
optional
parameters.
B
The
first
one
is:
it's
essentially
an
object
where
you
can
pass
a
series
of
invocation
callbacks,
where
once
an
invocation
happens
on
an
actor
that
callback
can
be
triggered,
and
you
can
essentially
use
that
data
to
do
something
on
the
ui
I'll
leave
that
blank
for
now
and
then
the
final
parameter
is
essentially
when
we
start
a
host,
we
want
to
do
a
heartbeat
and
the
default
heartbeat
is
every
30
seconds.
But
if,
for
some
reason
you
have
some
other
requirement,
you
have
a
way
to
customize
that
as
the
final
parameter.
B
So
I'm
going
to
start
the
host-
and
this
usually
takes
takes
a
couple
seconds
when
you
run
when
you're
running
with
the
compile
output,
just
because
it
has
to
fetch
a
a
wasm
file
and
what
this
wasn't
file
is
doing.
Is
it
uses
parts
of
the
wasm
cloud
capabilities,
library,
the
rust
and
keys
library,
and
I
think
the
there's
essentially
parts
of
rust
that
was
ported
over
to
javascript
just
so
that
we
can
generate
the
the
host
key,
because
the
m-keys
js
library
doesn't
doesn't
know
what
the
concept
of
a
server
key
is.
B
B
So
I'm
gonna
go
into
washboard
and
start
a
http
server
provider
and
I'm
gonna
do
it
from
file.
Just
because
I
know
the
one
that
I
have
in
my
registry
is
kind
of
broken.
So
that's
starting
I'll
go
back
into
ending
my
into
my
browser
host
and
start
an
actor.
Wait,
that's
launch
actor
and
the
actor
I'm
launching
is
the
echo
actor
and
it's
version.
0.2.3.
B
So
once
I
do
host.actors,
it
shows
me
the
the
actor
name
and
the
details.
Select
the
actor
count,
the
actor,
the
key
the
claims
and
then
the
the
capabilities
as
well.
So
if
I
go
on
back
into
washboard
now
I
see
the
actors
running
and
it
shows
the
host
id
from
my
browser
host.
So
I'm
going
to
define
a
link
between
the
actor
and
the
provider.
B
A
B
B
Looks
like
there's
a
bug
there,
but
essentially
we've
got.
We
were
able
to
launch
an
actor
inside
the
browser,
link
it
to
a
provider
outside
the
browser
and
be
able
to
actually
invoke
invoke
the
module
that
was
loaded
or
the
actor
module.
That
was
loaded
and
then
the
final
thing
I
wanted
to
show
off
is
using
it
as
a
library.
B
This
eventually
will
work
so
like
the
the
ecmascript
module
6
version,
just
doing
it
just
important
to
start
host,
so
you
don't
need
to
use
the
object.
The
only
reason
it's
not
working
right
now
is
because
we're
using
the
the
wasn't
binding,
webassembly
there's
a
bit
of
a
bit
of
issues
with
the
bundling,
but
that's
being
worked
on
so
I'll
save
this
and
then
I've
got
the
webpack
configuration.
B
So
essentially
you
want
to
compile
your
main.js
into
an
output
file
and
at
the
same
time
you
want
to
copy-
and
this
is
this
again-
this
is
a
hack
just
for
this
version.
This
won't
be
needed
once
you
have
once
we
have
the
es6
version
fixed,
but
essentially
what
you're
doing
is
you're
copying
the
the
compiled
wasm
into
your
distribute
distribution
folder.
Just
so
that
you,
you
don't
have
to
go
fetch
it
from
somewhere
else.
I'm
gonna
stop
the
server
do
an
npm
in
it.
B
B
So
I've
got
the
index
file
the
main
the
package,
the
web
webpack
config
and
when
I
run
run
webpack.
What
should
happen?
Is
it's
going
to
drop
an
output
for
an
output.js
and
a
wasm
file?
So
there's
the
walls
of
wallzim
and
the
out.js
I'll
go
back
into
the
index,
get
rid
of
this
and
reference.
The
out.js.
B
And
start
the
python
server
again
and
then,
when
I
load
it
up,
it
shows
the
window
dot
host.
So
essentially,
you
can
now
use
the
use
this
as
a
library
inside
of
your
applications
without
having
to
download
just
the
final
distribution.
Like
the
the
final
output,
the
caveat
there
is
that
you
need
the
webpack
bundler
to
to
copy
the
files
into
your
distribution
folder,
but
that's
pretty
much.
The
entire
idea
of
the
the
browserist
is
a
way
to
launch
actors
inside
a
browser
and
connect
it
with
a
remote
lattice.
C
C
When
you
go
to
curl,
it's
actually
essentially
going
to
round
robin
between
the
two
browser
tabs
in
order
to
satisfy
your
request,
and
so
you
can
essentially
just
add
compute
to
your
army
of
subservient
browser
tabs
just
by
opening
more
more
wasmcloud
hosts
everywhere.
You
want
them
running
and
starting
your
actors
in
those
hosts.
B
A
B
Yeah
that
would
be
that'd
be
interesting.
I
mean
there's
obviously
some
capabilities
that
we
couldn't
do
like
the
http
server,
but
I
yeah
there's.
Definitely,
I
think,
possibilities
there,
because
I
mean
if
it's
just
wasm
files,
then
as
long
as
the
browser
can
interpret
it
through
I'm
using
the
wap
cjs
library.
As
long
as
it
can
use
that,
then
I
think
we
should
be
able
to
at
least
at
least
like
give
it
a
stab
and
see
what
happens.
A
I
I
think,
if,
if
kevin
doesn't
want
to
chime
in
what
would
be
super
exciting,
I
think
from
a
capability
perspective.
Would
you
know
even
starting
to
think
about
accessing
capabilities
that
are
available
through
a
through
a
mobile
browser,
so
think
about
things
like
access
to
a
camera
on
a
mobile
phone
or
the
possibilities
of
microphone
or
you
know
a
whole
other
litany
of
of
of
information
or
capabilities
that
would
be
in
a
mobile
device.
A
A
There's
a
little
difference
between
you
know,
x86
in
the
cloud
you
know
a
web
browser
and
you
know
arm
or
some
tiny
cpu
somewhere
where
we
can
have
payloads
that
just
seamlessly
shift
up
and
down
the
continuum
here
which
is
sort
of
the
vision
we've
been
driving
towards
and
we
have
more
vision
here.
This
was
originally
going
to
be.
A
The
quarter
of
march
of
the
run
times
was
how
we
started
this,
and
I'm
glad
that
we
did.
I
know
we
got
a
little
distracted
with
the
scale
and
the
effort
around
the
otp
work
that
we
are
kind
of
you
know
following
through
on
this.
You
know
looking
down
the
road
map,
I'd
love
to
hear
from
kevin
later
about
his
thoughts
on
prioritization
or
the
community,
perhaps
about
prioritization
for
swift
host,
potentially
next
or
or
doing
a
capability
provider
in
a
web
browser.
C
Yeah
I've
got
a
number
of
thoughts
there
around
the
the
swift
runtime.
That's
definitely
one
that
we've
wanted
to
build.
It's
just
been.
You
know
we
we
only
have
so
many
hands
to
to
put
to
keyboards,
and
so
we
just
essentially
ran
out
of
resources,
but
that's
another
one.
That
makes
an
awful
lot
of
sense
to
me
is
putting
a
wisdom
cloud
host
wrong
time.
There.
A
As
far
as
it's
it's
just
to
speak
to
that
kevin
briefly,
it's
it's
just
such
a
great
example
of
not
linux.
You
know
when
you
think
about
the
better
together
story
with
the
cloud
native
ecosystem
starts
with
hey
we're
compatible
with
kubernetes
and
containers
and
there's
a
growing.
You
know,
part
of
the
world
and
part
of
the
ecosystem,
where
you
know
the
assumptions
that
containers
bring
to
the
table
around
operating
on
linux
and
around
operating.
You
know,
compiling
for
a
specific
cpu
architecture.
A
C
Alongside
the
capability
provider.
That's
feeding
frames
of
video
to
it
and
that
actor
could
do
things
like
object.
Detection
in
you
know
using
machine
learning
models
and
all
sorts
of
stuff,
and
wouldn't
you
know
about
an
eyelash
being
able
to
do
that
and,
in
addition,
would
still
have
all
that
access
to
all
the
actors
and
providers
that
are
running.
C
You
know
those
types
of
things
are:
are
things
that
work
both
in
a
browser
and
on
iot
devices
like
you
know,
raspberry,
pi's
and
so
on?
And
so
now
you
can
imagine
that
you've
got
an
actor
that
performs
this
object.
Detection
on
video
frames,
where
you
you
know.
Finally,
you
have
that
dream
of
not
having
to
modify
your
code
at
all
and
you
can
dynamically
push
that
actor
to
a
raspberry
pi
into
a
browser
and
to
maybe
something
in
the
back
end.
A
It's
truly
mind-blowing
the
possibilities,
and
I
start
to
think
about
things
like
you
know.
Like
you
know,
if
nests
doorbell
code,
you
know
you
could
open
it
up
as
an
app
in
a
web
browser
or
run
it
on
a
you
know,
a
piece
of
embedded
hardware
as
well.
I
mean
I
think
they
were
really
starting
to
make
some
crazy
dynamic
topologies
possible.
A
A
D
Let's
see
you,
can
everybody
see
a
little
little
browser
screen
here
with
a
somewhat
familiar
washboard,
but
a
couple
changes,
yep
cool,
so
I've
been
I've
been
posting
in
the
slack
for
over
the
past
couple
of
days,
just
to
get
some
ui
feedback,
as
I
kind
of
tweak
the
dashboard
into
getting
ready
for
for
mvp
functionally.
It's
it's
pretty
much
there,
but
I
wanted
to
add
a
couple
of
things.
D
D
D
But
what
you
can
do
is
you
can
select
between
this
list
of
hosts
to
view
kind
of
more
specific
information,
so
you
can
see
only
the
actors
and
providers
that
are
scheduled
in
this
one
host.
You
can
kind
of
see
like
an
overall
view
of
how
many
actors
and
providers
and
the
labels
that
are
on
this
host,
so
you
can
see
what
type
of
you
know
these
these
host
core
or
built
in
are
default
labels.
D
The
only
other
change
to
note
here
is
that
you
are
still
able
to
start
actors
and
providers
from
file
when
it's
the
local
machine,
because
that
deals
with
like
starting
and
directly
from
your
disk,
but
for
a
remote
host.
It's
only.
The
only
option
is
from
an
oci
registry
now,
which
is
essentially
exactly
what
we
allowed
before,
but
by
default
you're,
going
to
see
the
actors
and
providers
across
the
entire
lattice,
and
then
I
guess
the
only
other
thing
to
show
here
is
that
I've
moved
the
metrics
over
to
a
different
tab.
D
D
D
C
A
I
think
it's
definitely
awesome
and
brooks.
I
think
it's
looking
a
lot
better.
I
love
the
I
love
how
you're
you
know
pulling
everything
together
and
you
know
the
ability
to
see
across
the
lattice
view
now
you
know
there
should
be.
I
just
think,
that's
pretty
exciting
when
we
start
to
think
about
visualizing
this
and
seeing
it
all
come
across
here
great
work
on
all
that
any
other
questions
for
brooks
as
he
continues
to
go
along
here.
A
A
For
example,
perhaps
there's
a
host
dashboard,
a
capability
dashboard
and
an
actor
dashboard
where,
if
I
just
wanted
to
view
that
particular
resource
type
in
an
environment
I
could
see,
maybe
just
tables
of
you
know
all
the
metadata
dumped,
and
you
know
something
along.
Those
lines
feels
like
that
might
be
a
pattern
that
you
know
that
that
would
be
useful
in
a
heads-up
display
like
this.
So
I'll
try
to
maybe
pull
some
of
that
together.
A
A
A
If
you
did
not
see
any
of
the
news
today,
there
is
a
the
three
or
four
great
articles
already
posted
in
a
few
on
the
way
that
are
talking
about
the
excitement
around
wasm
cloud
and
we
really
plan
to
beat
that
drum
all
the
way
through
kubecon
and
into
re
invent
this
year
august
31st
in
germany
there
is
a
new
event
called
better
code
eu.
This
is
a
wasom
thatbettercode.eu,
which
is
a
webassembly
focused
event.
A
A
Get
my
screen
shut
out.
Congratulations,
david
and
stuart
for
being
accepted
as
speakers
at
wasm
wasmday.
I,
for
one,
am
incredibly
looking
forward
to
some
stunt.
Hacking
live
cosmonic,
we'll
have
a
sponsored
keynote
here
later
bailey
is
in
our
community.
She's
got
a
phenomenal
talk
around
running
web
assembly
in
a
database
which
I
love
connor,
it
will
be
doing
a
platform
talk
from
subordinal.
A
A
Here
is
the
talk
from
stuart
and
team,
and
then
we've
got
the
cube
warden
folks,
who
are
in
our
community
as
well,
we'll
be
talking
about
writing
admission
policies
using
kubeborden.io,
which
is
moving
quite
quickly.
If
you're
not
following
it,
then
we've
got
a
shopify
talk
around
sort
of
an
update
on
what
they're
doing
with
their
platform
and
a
this
is
a
an
akari
talk
which
we
did
do
an
akari,
lightning
talk.
A
At
the
last
wasm
day,
we
were
trying
to
make
sure
we
covered
different
content
this
time,
but
this
is
really
dialing
it
into
running
they're,
running
akari.
Now,
in
webassembly
and
a
few
other
things,
we've
got
a
talk
from
jason
song
over
at
ant
group,
which
I
loved
is
an
end
user
talk.
They
are
actually
putting
forward
a
model,
that's
somewhat
similar
to
wasmcloud.
A
They
call
it
a
layer.
Eight
layout
is
what
they
call
it,
but
they're
running
things
at
incredible
scale.
They
talked
about
running
on
over
200
000
nodes,
so
it
should
be
a
very
interesting
talk.
Bindle's
bundle
talk
from
taylor
and
matt
and
then
michael
wand
from
second
state
talking
about
integrating.
You
know
the
better
together
story
with
docker,
kubernetes
and
wasmedge.
A
E
Neither
as
as
mind-blowing
or
inspirational
as
taoshik's
host
in
the
browser,
nor
is
it
as
colorful
and
interactive
as
brooks's
dashboard
demo,
but
I
have
something
almost
boring
and
black
and
white.
I
could
show
so
I
connected
together.
Three
capability
providers,
the
wasn't
the
http
server,
the
http
client
and
the
random
number
generator
and.
B
B
A
E
E
Yep,
so
here's
the
here's
the
code
to
get
a
random
number
within
any
inclusive
range.
So
that's
one
of
the
built-in
capability
providers,
there's
a
built-in
logging
and
a
built-in
number
capability
provider
that
gives
you
random
numbers
and
generates
fluids
and
things.
Here's
the
the
http
client
it
fetches,
the
url
gets
the
result
and
then
then
we
generate
the
web
page
and
send
it
as
a
response.
A
E
A
All
right,
that's
incredible.
I
know
you
and
kevin
brooks
and
others
have
just
been
slaving
away
at
this
for
a
while.
Thank
you
for
the
you
know.
The
extra
organization
and
all
the
you
know
also
putting
on
your
scrum
master
hat,
to
help
us
keep
all
that
in
track
and
measured
any
feedback
on
the
on
the
weekly
reports.
That
steve
is
putting
out.
You
know
I
kind
of
feel,
like
that's
a
a
wall
of
text.
A
You
know
we've
been
trying
to
drop
that
in
weekly
now
for
a
month,
and
I
don't
know
that
we
really
get
get
a
lot
of
comments
or
feedback
on
it
that
people
just
skip
over
it
when
it
drops
into
general.
On
the
like.
You
know
what
happened
last
week,
what
what
we're
going
to
try
to
accomplish
next
week?
Maybe
should
we
try
formatting
it
up
a
little
bit
making
it
look
nicer
or
anybody
have
any
feedback
on
that.
H
A
H
A
That
has
been
my
error,
I've
I
had
hired
someone
that
was
going
to
do
it
for
us
and
it
didn't
work
out.
So
I
have
been
just
overwhelmed
on
getting
those
up.
I
can
try
to
get
the
last
couple
up
if
there's
ones
you
have
in
mind
more
quickly,
but
I
am
looking
for
a
resource
to
hire
that
can
just
reliably.
You
know,
show
up,
dump
the
meeting
and
and
upload
it.
We've
just
been
completely
swamped
lately
with
a
million
things
in
that
on
the
back
end.
Here.
A
A
You
know
a
paid
position
if
you
wanna,
if
you
want
a
totally
open
to
that,
you
know
yeah,
I
accept
hugs
as
currency
and
that's
about
it.
Well,
if
you're
lucky,
I
actually
just
found
a,
I
don't
remember
derbycon,
I
can't
see
your
blur.
Thingy
is
blurring
it.
Oh
it
says
it's
a
man-hug
ticket.
It
was
from
relic.
You
know
dave
dave.
It
was
always
phenomenal
for
epic
hugs
and
so.
G
A
Cleaning
out
some
old,
you
know
hacking
project
and
I
found
one
of
these
folded
between
the
pages
of
a
of
a
you
know:
notebook
around
hacking,
wi-fi
or
something
like
that.
So
I
think
it's
fun
all
right.
I
will
get
them
uploaded
jordan,
and
I
really
appreciate
that
it
would
be
a
huge
uplift
for
us
all
right
now,
because
I
know
that
was
super
helpful
and
we
did
have
a
pretty
reliable
stream
of
people
watching
stuff.
So
we'll
start
today
and
we'll
try
to
pick
that
back
up
again
david.
A
C
So
the
rfc
isn't
actually
for
the
kubernetes
controller,
it's
for
a
controller
to
be
used
by
other
controllers,
one
of
which
could
be
a
kubernetes
controller.
I
know
it's
kind
of
splitting
hairs,
but
yeah
I
mean
generally,
you
know
the
more
feedback
I
get
on
that
the
better
I'd
like
to
start
actually
working
on
that
and
you
know,
setting
up
some
scaffolding
around
it
so
that
other
people
can
start
contributing.