►
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.
https://wasmcloud.com
A
B
B
I've
just
been
interested
with
how
the
technology
works
and
how
portable
it
is
and
being
in
the
rust
space.
That
kind
of
exposes
you
to
that,
and
you
know,
with
vlasim
cloud
coming
up.
I
thought
the
technology
would
be
very,
very
interesting
for
the
type
of
stuff
that
I'm
interested
in
the
type
of
stuff
that
I'm
looking
to
do
in
the
future.
So
that
is
me.
A
A
A
So,
let's
see
last
week
or
or
two
weeks
ago,
we
talked
about
how
we
are
adding
tiny
ghost
support
for
wasmcloud
for
our
actors
and
one
of
the
things
that
I
just
wanted
to
show
today.
You
know
this
is
kind
of
a
multi-faceted
demo,
so
I'm
gonna
show
a
few
things,
but
we
adapted
one
of
our
examples,
not
just
the
hello
world
example,
but
to
show
you
a
full
a
full
example
of
getting
a
request
to
an
actor
and
then
making
a
request
of
a
capability
provider.
A
We
took
our
kind
of
classic
kv
counter
example:
that's
in
rust,
where
receives
an
http
request
and
then
increments
a
counter
and
a
key
value
store,
and
we
ported
that
to
tinygo.
So
we
basically
just
took
the
equivalent
functionality
and
wrote
that
in
tinygo,
so
it
it
still
is-
is
very
simple:
the
the
reduced
boilerplate,
the
the
low
boilerplate
experience
that
rust
gives
you
where
we
are
getting
an
http
request,
returning
an
http
response.
A
Now
what
I
did
is
I
set
this
up:
got
the
got
some
things
running
in
in
wasn't
cloud,
so
I've
got
the
the
wasp
dashboard
running
locally,
our
kb
counter
tiny,
go
http
server,
redis
key
value
all
that
stuff,
and
we
actually
have
this
endpoint
set
up
I'll
go
ahead
and
bring
it
in
the
chat.
If
anybody
wants
to
also
hit
that
endpoint
now,
you'll
notice
that
this
is
not
running
on
my
local
host,
it's
you
know
some
ip
address
out
in
out
somewhere
else
yeah
I
actually.
A
If
people
could
hit
it,
it's
pretty
fun
because
it's
just
gonna
go
up,
but
one
thing
I
wanted
to
show
is:
I'm
actually
not
running
anything
on
my
local
machine
other
than
a
wasn't
cloud
dashboard
to
like
look
at
this.
What
I
have
is
the
http
server
capability
provider,
that's
running
on
a
vm
in
gcp,
that's
where
this
ip
address
is
actually
coming
from.
A
You
see
everybody's
actually,
oh
god,
everybody's
actually
using
it
and
hitting
the
counter-
and
I
just
have
that
you
know
open
to
the
internet,
at
least
for
the
duration
of
this
call,
and
then
I
also
have
another
host.
That's
running
our
key
value,
counter
tiny,
go
tinygo
and
redis,
and
you
can
see
that
the
device
is
an
ipad
and
the
location
is
behind
you.
A
So
this
is
not
actually
really
running
a
wasn't
cloud
host.
It's
using
evan's
get
pod
template,
but
it
has
support
for
that
in
safari.
I
just
thought
that
that
was
cool.
So
the
you
know,
the
the
other
facet
of
this
demo
that
I
wanted
to
show
off
is
the
additional
support
for
the
tiny
go
language
in
the
get
pod
template.
So
evan
matiza
was
in
here.
He
has
really
contributed
an
awesome
project
by
setting
us
up
with
a
template
for
git
pod.
That
includes
all
kinds
of
things
it
includes.
A
We
go
to
the
tiny
go
actor
and
we
we
build
it.
Oh
darn,
and
we
don't
have
it
already
built
and
we
build
it.
It
has
a
little
tiny
go
tool
chain
in
here.
So
you
know,
evan
was
super
responsive
for
this.
We
reached
out
to
him
and
said:
hey
we
added
additional
language
support.
Can
you
add
that
into
the
get
pod?
A
A
D
D
We
we've
pulled
together.
What
we
hope
is
a
really
helpful
walkthrough
of
both
webassembly,
as
well
as
as
well
as
wasmcloud
with
some
new
training,
and
things
like
that
on
here,
so
you
can
simply
come
in,
and
jordan
has
spent
a
ton
of
time
helping
to
pull
these
together
and
cosmonic
has
elected
to
sponsor
these,
because
this
all
now
runs
in
a
live
containerized
environment
here
that
spins
up
dynamically.
D
In
the
background,
so
as
you
get
into
the
classes,
you'll
find
that
there
is
some
emerging
video,
some
emerging
content
and
as
we
continue
to
update
wasmcloud,
our
hope
is,
is
that
we
can
continue
to
keep
this
up
to
date
with
new
examples.
So,
hopefully,
we'll
pull
together.
Some
go
training
to
highlight
the
new
support
for
tinygo
in
wasmcloud
and
give
you
some
hands-on
experience.
I
would
love
if,
as
folks
get
into
this,
if
they
can
start
to
give
us
some
feedback
on
how
things
are
working
here.
D
Water,
well,
there
we
go
well.
I
think,
if
you
follow
the
instructions,
you'll
have
a
better
luck
than
I
will,
but
as
we
get
into
this
we'd
love
to
get
any
feedback
that
you
might
have
on
the
experience
and
how
well
it
on
board
you,
if
you
have
any
ideas,
we'd
love
to
hear
that
as
well,
so
that
so
that
we
can
continue
to
try
to
make
this
a
really
helpful
set
of
tutorials.
D
So
and
as
you
get
further
into
the
lessons,
you'll
sort
of
find
that
that,
as
you
get
into
the
lessons,
you
can
even
have
multiple
tabs
up
here.
That
include,
you
know
the
washboard
to
make
it
make
it
really
easy.
So,
just
like
the
gitpod
experience,
this
should
be
similar
very
similar
to
that,
but
for
training
and
onboarding.
C
D
B
D
A
We
do
love
to
drink
our
own
champagne
here.
That's
for
sure.
I
just
wanted
to
to
add.
I
guess
one
more
comment.
So
not
not
quite
a
question,
but
the
you
know
on
labs.cosmonic
the
you
know
there
is
a
wazzle
cloud
track.
The
webassembly
track
is
not
bosom
cloud
specific.
It's
not
rust
specific.
It
is
a
general
webassembly
track
all
things
about
wasm,
so
you
know
it's
a
great
resource
for
anyone.
A
It
lightly
follows
like
a
similar
course
to
the
webassembly
definitive
guide
by
brian
slatten.
You
know
it's
very
similar
to
that
talking
about
modules
and
tables
and
and
memory,
and
it's
a
little.
I
guess
a
little
more
low
level
wasn't
but
great
if
you've
only
ever
used
wasm
as
a
compilation
target
as
a
walkthrough.
A
A
A
So,
if
you're
on
here
keep
an
eye
out
for
our
blog
posts-
and
you
know
all
the
cool
things
that
everyone
else
is
doing
additionally,
one
thing
that
I
will
tease
but
not
show
all
of
it-
we
are
going
to
be
adding
a
new
blog
onto
our
website
this
week.
It
is
about
tiny,
go
and
written
by
our
own
kevin
hoffman
kevin.
Do
you
want
to
do
you
have
any
comments
or
want
to
say
anything
about
this?
One.
E
A
Awesome
awesome
yeah
we're
we're
trying
to
continue
to
publish
content
like
this,
especially
you
know.
Many
of
you
who
are
in
this
call
are
active
in
our
community
slack
and
are
you
know
attending
these
calls
on
a
semi,
semi-weekly,
semi-frequent,
sometimes
weekly
basis,
so
you
know
getting
some
content
out
there
for
the
broader
community
that
may
not
join
slack
is
really
important
to
us
alrighty.
That
is
what
I
had
for
general
web
assembly
community
announcements.
A
I
have
been
checking
pretty
much
every
day
for
when
taylor
and
I's
my
talk
will
go
up
on
youtube
on
the
cnc
at
youtube.
It
should
it
should
be
uploaded
here.
I
think
by
june
6th
was
the
date
that
they
said
it
would
be
uploaded
by.
So
we
should
have
that
that
public
youtube
link
ready
for
you
pretty
soon,
but
does
anyone
else
have
anything
from
the
the
broader
webassembly
community,
any
blossom
cloud
callouts
that
they'd
like
to
put
out
there
or
any
issues
in
particular
that
you
want
to
talk
about.
A
E
A
A
E
E
A
Very
nice,
it's
always
nice
to
you
know,
I'm
I'm
interested
to
see
how
many
people
you
know
at
kraftkonk
have
heard
of
webassembly.
You
know
who's
coming
to
the
talk
like
totally
new
or
like
has
seeing
it
start
to
make
like
a
bigger
splash
in
cloud
native
and
they're
like
okay.
This
is
seems
like
a
really
big
deal.
What's
going
on.
E
E
F
A
B
G
An
issue
on
kind
of
creating
that
config
file
they
were
talking
about
yesterday
brooks
yeah.
I
can
link
it
in
there
soon,
so
I
I
made
this
and
started
writing
it
up,
but
this
will
probably
touch
a
lot
of
people
with
with
possum
if
we
end
up
with
cloud
if
we
end
up
going
with
it.
So
please
take
a
look
at
this
and
weigh
in
on
like
what
you
want
out
of
a
config
file.
G
A
A
If
we
have
a
let's
see
I
I
won't
won't
put
any
words
in
your
mouth
matt,
but
this
will
be.
This
is
great
to
have
just
like
general
wason
cloud
configuration,
maybe
combining
some
of
those
wash
flags
on
the
command
line
to
and
like
the
host
config
definition
that
we
use
for
a
wasn't
cloud
host
like
connecting
to
nats
and
things
like
that.
So
that
would
be
great.
G
A
G
The
the
main
thing
is
pretty
much
getting
rid
of
make
is
kind
of
the
main
goal,
I
guess
initially
and
then
kind
of
looking
at
the
other
stuff.
So
right
now
we
have
the
project
make
file
which
is
more
or
less.
The
configuration
file
has
like
the
actor's
name
and
the
different
capability
providers
and
everything
so
turning
that
into
a
actual
configuration
file
and
then
turning
the
the
make
file
that
we
have
is
kind
of
like
a
compiler,
more
or
less
right
now
into
something
that's
actually
built
into
wash.
G
A
I
think
in
rust,
like
in
cargo.tamil,
you
can
do
like
arbitrary
tamil
entries
like
for
metadata
or
tags,
or
something
like
that
annotations
one
of
those
things
and
I'm
pretty
sure
you
can
do
the
same
thing
in
like
a
package.json
for
eventually
using
like
an
assembly
script
support.
But
can
you
do
that
with
a
go
mod
like?
Is
there
nope.
E
E
Yeah,
I
feel
like
there's,
probably
there's
probably
a
lot
we
can
leverage
by
maybe
having
a
single
tamil
file.
You
know
like
a
netlify,
tamil
or
or
whatever
and
then
going
from
there
one
other
thing
I
was
thinking
of
now
that
I
just
saw
this.
This
is
the
first
time
I've
seen
this
request.
Is
that,
with
this
tunnel
in
place,
you
might
even
be
able
to
do
to
assume
a
bunch
of
reasonable
defaults
when
you're
using
other
wash
commands
so
like.
A
F
F
E
B
E
A
Well,
this
is
awesome.
Thank
you
for
for
grabbing
me
matt
before
I
stop
the
recording.
There
are
some
other
really
interesting
proposals
here
in
wash
now
that
you
might
also
be
if
you're
interested
in
that
one.
You
may
also
be
interested
in
things
like
interactive,
wash
claims
sign
to
make
that
a
little
bit
easier.
E
F
F
I
would
I
would
also
point
out
here
so
this
is
brooks-
has
really
been
driving
this
forward,
but
we're
just
trying
to
pay
down
some
of
the
devex
tech
debt
that
we've
been
accumulating
over
the
past
few
months
with
some
of
these
features.
So
if
you're
a
wasom
cloud
user,
we
really
want
to
get
your
feedback
and
things
as
as
we
start
to
roll
these
out,
because
this
is
meant
to
make
everything
easier.
F
All
of
us
who
are
all
of
us
are
core:
maintainers
are
using
wasm
cloud
as
well
like
we're
not
just
writing
the
code,
we're
also
using
the
code
for
the
stuff
we're
doing
at
cosmonic,
and
so
we
want
these
things
just
as
much
as
everybody,
but
if
we
base
it
purely
on
what
we're
doing,
I
know
we're
going
to
miss
edge
cases
here.
So
please
comment
on
those
things.
A
A
You
know
taking
rust
or
tiny,
go
for
all
the
creating
and
actor
parts,
and
so
I
don't
know
why
that
happens,
keeping
it
simple
for
installing
wash
you
know
an
easy
way
to
get
gnats
and
then
you
know
a
three
line
command
for
installing
and
unpacking
wasmcloud
really.
You
know
this
reduces
the
friction
for
the
initial
install,
but
we
want
to
make
this
as
clean
and
crisp
as
possible.
D
A
A
A
Janitor
you
just
sent
the
invoke
web
request
thing,
and
it
this
always
just
like
and
powershell
is
really
powerful
right.
It's
a
really
powerful
scripting
language,
I'm
not
used
to
it,
and
that
is
why,
but
it
always
just
like
numbs,
my
brain
a
little
bit
when
I
come
and
try
to
figure
out
how
to
use
a
utility.
It's
just
a
it's
a
lot
of
stuff.
I
just
don't
know
powershell,
that's
probably
the
the
reason,
but.
G
C
C
Sorry,
I
just
have
to
my
internet's
dodgy
and
it
seems
to
be
everywhere,
or
at
least
like
these
ghost
meetings
I
had
this
morning
was
also
bad.
I
was
just
saying
the
control
spacebar
actually
seems
to
work
reasonably
well,
but
yeah,
the
errors
and
all
that
sort
of
stuff,
but
to
everybody's
point
I
am
on
wsl
for
most
of
the
time
on
linux,.
A
A
C
Actually,
I
have
a
question
kevin
something
so
looking
at
what
him
again,
I
think
something
that
I've
never
actually
really
got
through.
My
is
that
you're
actually
trying
to
propose
cqrs,
yes
and
I
started
playing
around
with
a
tool
called
commanded
which
does
the
event
streaming
and
cqrs
separation.
I
was
wondering
whether
that
was
exactly
what
you
were
thinking
of,
or
were
you
thinking
of
something
completely
different
and
I'm
completely
off
the
wrong
track.
E
You
know
things
like
reading
from
the
system
clock
and
you
know
other
things
that,
where
the
formality
of
pure
event
sourcing
would
sort
of
get
in
the
way,
so
I
would
I
would
describe
wadam
as
event
driven
rather
than
like
pure
event
sourcing,
so
probably
not
a
full
cqrs
es
type
implementation,
but
similarly
inspired
I'm
hoping
that
when
I
get
back
from
budapest
that
I'll
be
able
to
spend
a
little
bit
of
time
on
it
and
move
it
a
little
bit
further.
And
then
hopefully
you
know
get
some
of
this
stuff.