►
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
been
trying
to
get
myself
kind
of
current
with
what's
kind
of
happening
in
the
wild
space.
One
of
my
counterparts
has
been
very
active
as
well.
We
actually
spoke
at
the
wasm
day,
primarily
just
to
try
to
provide
strategic
direction
for
a
lot
of
our.
You
know,
engineers
across
adobe,
as
we
kind
of
evaluate
all
the
building
blocks
that
make
up
cloud
native.
I've
also
been
very
active
in
the
kubernetes
community.
I
just
most
recently
came
off
being
the
emuratus
advisor
for
the
124
release.
B
I
also
work
along
with
sig
release
and
just
a
lot
of
the
maintainer
tools,
a
lot
of
things,
how
we
just
kind
of
get
kubernetes
cut
and
release,
and
also
around
six
contrabex.
So
I
love
being
part
of
communities
and
trying
to
just
share
the
things
that
I've
learned
along
the
way
and
as
this
group
is
developing
and
if
there's
opportunities
for
me
to
participate
and
help
shepherd
along,
I
love
to
be
able
to
be
in
a
position
to
help
make
this
grow.
A
C
Yes,
welcome
and
welcome
joseph
all
right.
There's
the
beautiful
blank
canvas
that
we'll
use
to
start
so
we've
been
a
lot
of
folks
have
been
asking
for
what
other
languages
can
we
use
to
build
our
actors
besides
rust
and
today
we're
introducing
tiny
go
so
one
way
to
to
get
started
is
with
the
wash
new
actor
command.
Now
that
I'm
using
a
wash
that's
pre-released,
but
this
is
will
come
soon.
I'll
show
you
where
the
sdk
is.
C
The
syntax
of
tiny
go
is
pretty
much
the
same
as
go.
There
are
a
couple
limitations
and
I'm
gonna
show
you
I've.
Actually
this
is
generated
from
a
template
and
the
template
hasn't
been
up
to
date.
I'm
going
to
actually
simplify
this
a
little
bit
because
we
just
made
a
change
where
you
don't
have
to
implement
that
health
request
on
your
own.
C
So
this
is
this.
Is
all
you
have
to
do?
Here's
one
method
that
responds
to
an
http
request,
so
the
make
file
which
is
generated
automatically
links
it
to
there.
It
is
http
server,
so
I'm
gonna,
I'm
just
gonna,
say
make
to
make
to
build
it
and
then
I'm
going
to
say
make
push
to
push
it
to
my
local
registry
and
start
to
start
it
and
link
to
link
it
to
the
capability
provider.
C
C
B
C
C
So
this
is
the
host
dashboard.
You've
all
seen
it's
always
running
with
a
wasm
cloud
host
on
default
is
port
4000..
The
tiny
go
sdk
is
right
here.
The
wasm
cloud
repo
and
all
you
have
to
do
to
use
it
is
you
just
do
go,
get
go,
get
the
tiny,
tiny
go
sdk.
In
this
case,
we
also
had
to
get
the
http
server
interface
to
get
the
definitions
for
the
http
http
request.
C
So
we've
gone
through
the
interfaces
repo
in
github,
where
we
store
the
interface
definitions
so
for
http
server.
This
is
where
we
keep
the
smithy
definitions
and
there's
a
rest
subdirectory
with
the
rust
library
and
now
there's
a
tiny
go
subdirectory
for
all
of
them.
That
has
the
code
automatically
code
generated
for
your
your
tiny
go
library.
D
I
have
one
quick
question:
steve
yeah,
the
templates
when
we
do
this
correct
me
if
I'm
wrong,
when
we
do
wash
new-
and
this
probably
isn't
new
this-
I
just
probably
figured
this
out
the
hard
way
it
actually
reaches
out
to
github
and
pulls
templates.
So
if
we're
on
a
non-internet
connected
machine,
are
we
not
able
to
generate
a
new
like
actor
via
the
templating.
C
C
C
C
Great
question
brooks
it's:
it's
when
you
see
the
announcement
for
the
wash
0.11
release,
it'll,
be
there,
we've
got
it
in
it's
in
the
github.
Now,
if
you
wanted
to
build
it
from
source,
but
I
think
it
should
should
I
you
can
tell
me
it's
a
it's.
A
team
call
on
when
we
release
it,
but
it
might
be
within
the
next
couple
days.
A
Yeah,
I
think
I
think
we
definitely
want
to
get
this
released
in
the
next
couple
of
days.
We'll
likely
do
some
kind
of
some
kind
of
blog
post
and
talking
about
announcing
tiny
go
as
an
additional
language.
So
all
of
that
will
probably
happen
at
the
same
time.
So
if
you
wanted
to
give
this
a
try
now
you
can
install
from
from
main,
but
we'll
have
this
released
in
the
next
couple
of
days,
so
that
it'll
just
be
standard.
C
C
A
That's
a
good
point,
and
probably
one
more
thing
just
to
point
out-
is
that
we'll
also
be
updating
our
documentation.
A
lot
of
our
documentation
goes
through
the
initial
flow,
with
a
rust
based
actor,
and
now
you
know
we
have
a
different
possible
path
of
running
through
that
hello
example.
You
know
we're
still
using
rust
capability
providers,
but
the
first
example
could
be
done
with
with
tiny
go
now,
so
we'll
definitely
be
updating
our
documentation
to
support
that
that
code
path
too.
C
A
I
have
a
couple
of
different
things
that
I
just
wanted
to
mention
from
like
general
community
and
and
wasn't
land.
We
just
came
back.
You
know,
taylor
liam
and
I
all
went
to
kubecon
eu
this
year,
so
we
had
a
great
time
in
spain.
Over
the
last
last
week,
we
had
a
lot
of
representation
for
for
wasm
on
the
server
side
and
was
cloud
specifically
christopher
engraved
gave
a
great
talk
at
cloud
native
rejects.
That
stream
is
now
live
on
youtube,
so
you
can
go
watch
his
talk.
It's
time
stamped.
A
I
assume
that
they're
going
to
slice
it
up
into
individual
videos,
and
things
like
that.
We
had
you
know
our
very
own.
Liam
randall
give
a
talk
at
cloud
native
security
day.
We
had
two
talks
at
cloud
native
wasmday,
that
mentioned
wasn't
cloud
or
that
were
specifically
about
wasmcloud
and
taylor,
and
I
gave
a
talk
at
the
main
conference.
You
know
from
cosmonic,
but
on
all
the
things
that
wasn't
cloud
enables
in
the
cloud-native
landscape
today.
A
You
can
now
find
our
slack,
which
you
know
many
of
you
are
already
in
there,
but
if
you're
not
you
can
join
there
and
we
also
have
a
calendar
which
you
know
we
through
our.
Through
our
talk
on
this
calendar.
We
have
the
watson
cloud
weekly
community
call,
but
you
know,
as
things
as
things
begin
to
show
up
in
the
wasm
community,
like
the
wasm
cloud
or
the
wason
time,
bi-weekly
meeting
or
our
machine
learning
sub
group,
we
plan
to
throw
it
on
here.
A
A
You
know
the
the
cosmonic.com
site,
but
we
also
want
to
be
publishing
blogs
that
are
specifically
focused
on
wasn't
cloud,
so
we
have
two
out
there
now,
one
which
I
wrote,
which
is
a
little
guide
on
how
to
publish
a
wasn't
cloud
actor
to
github
packages,
and
that
is
actually
already
included
in
our
project
templates
repo.
So
you
can
go
ahead
and
give
this
a
try
now
and
one
from
kevin
about
algebraic
effects
and
kevin.
A
E
Yeah
I
mean
the
the
general
idea
behind
that
blog
post
is
that
when
we
talk
about
what
our
capability
providers
are,
we
tend
to
refer
to
them,
as
you
know,
non-functional
requirements,
and
that
makes
sense
to
a
certain
audience
of
people.
But
so
I
wanted
to
write
this
blog
post
to
compare
our
capability
providers
to
what
functional
programming
refers
to
as
algebraic
effects.
A
Yeah
awesome,
so
please
we'll
we'll
do
a
little
more
publicity
about
this
one,
but
go
go
check
it
out
and
then
the
last
thing
that
I
had
for
general
wasm
community
from
us
at
cosmonic
and
thank
you
so
much
to
to
jordan
rash
who's
on
this
call.
Who
did
a
ton
of
work
on
this
and
brian
sletten,
who
put
together
the
training
for
this?
The
webassembly
course.
A
We
now
have
this
website
labs.cosmonic.com,
which
is
supposed
to
be
it's
a
new
home
for
the
training
for
for
wasn't
cloud
or
just
for
web
assembly
in
general.
So
we
wanted
to
provide
a
good
space
for
people
to
go.
You
know
if
they
haven't
heard
of
webassembly
before
you
can
go
check
out
the
the
webassembly
basics
training
lab.
This
has
everything
from
the
types
that
web
assembly
supports
to
you
know,
tables
or
memory.
You
know
it
gets
very.
Oh,
I
won't
spoil
anything
but
good
sure
brian.
A
It
gets
very
into
the
the
details
of
the
webassembly
format.
So
it's
really
great
if
you
haven't
actually
gotten
to
play
with
with
wasm,
at
least
if
you've,
maybe
just
heard
of
it
or
if
you've
always
used
it
at
a
higher
level,
and
we
also
have
our
own
wasmcloud
training,
module
and
training
sounds
so
official.
But
really
we
wanted
to
just
be
like
an
introductory,
spend
a
couple
minutes
walk
through
a
guided
tour
of
what
wasn't
cloud.
Is
we
previously
used
catacota
for
something
like
this,
but
they?
A
D
A
B
So
brooks,
if,
like
the
resources
like
this
and
stuff,
where
is
this?
Are
this
all
contained
on
your
your
repo?
Your
meeting
notes
captured
what
I'm
trying
to
do
is
just
as
I'm
going
along.
I
want
to
be
able
to
like
easily
share.
You
know
all
these
things.
That's
like
from
this
meeting.
Obviously
there's
recording.
A
Yeah
great
question:
so,
if
you're
looking
for
the
you
know
things
like
the
training
labs,
we
actually
have
that
on.
Here
we
go.
We
actually
have
that
on
the
cosmonic
website
under
open
source
we
have
labs
and
actually
on
the
labs
page,
that's
a
great
place
to
go.
It's
kind
of
a
general
hub.
These
meetings
are
are
recorded
and
where
we
actually
put
those
is
on
our
youtube
channel,
you
can
follow
the
link
at
the
bottom.
A
It's
just
youtube.comwasmcloud
cloud,
that's
kind
of
generally,
where
our
meetings
get
get
posted
and
everything
thank
you
justin
for
putting
that
there
another
great
place
to
just
kind
of
stay
up
to
date,
and
you
know
give
quick
feedback
or
ask
questions,
is
in
our
slack.
That's
where
all
of
us
are
generally
pretty
active
and
can
give
quick,
quick
feedback.
A
D
Not
yet
it
does
exist,
they're
they're,
with
the
platform
we
use,
there's
some
like
there's
some
things.
I
have
to
do
to
make
it
a
little
safer
because,
right
now
you
can
just
squash
on
top
of
the
training,
because
there's
no
real,
like
safety
checks
in
place.
So
as
soon
as
we
get
some
safety
checks
in
place,
that
will
be
open
sourced.
A
B
A
All
righty
well
the
last
thing
that
I
have
on
the
agenda.
I
do
have
a
couple
community
call
outs
which
you
know.
I
know
that
not
everybody
here
has
been
here
before
the
community
call
out
section
is
where
try
to
select
a
couple
of
good
first
issues
on
some
of
our
repositories
and
and
point
them
out
as
great
places
to
start,
give
a
little
detail
and
encourage
people
to
come
and
contribute
because
we
we
try
and
welcome
contributors
on
this
first
one
dan
filed
this
one.
A
We
have
a
feature
called
wash
context
that
you
can
configure
different
contexts
for
working
with
different
wasm
cloud
clusters
or
wasn't
cloud
lattices.
So
you
can
easily
work
on
your
local
machine
or
you
could
be
working
with
some
kind
of
cloud
deployment
of
wasmcloud
and
you
can
easily
switch
back
and
forth
kind
of
like
a
cubecontrol
context
and
the
way
that
it
works
today.
Is
you
specify
a
path
to
like
a
json
file
or
to
yeah
to
a
context?
A
Now?
I
actually
really
agree
with
the
way
that
dan
phrased
this.
We
should
instead
be
able
to
specify,
like
the
name
of
a
context
similar
to
how
cube
control
does
it.
So
this
is
a
great
place
to
get
started.
Really
it's
just
it's
in
the
wasm
cloud
shell.
So
this
is
a
this
is
a
rust
project
and
you'll,
be
specifying
a
name
to
a
defined
context,
is
a
great
great
way
to
make
an
impact.
A
The
second
one.
I
noticed
this
the
other
day
when,
when
I
was
testing
wash
claims
inspect,
I
was
inspecting
a
local
file
on
disk.
I
was
actually
playing
with
the
tiny
go
examples
and
if
you
specify
a
file
that
doesn't
exist,
we
actually
attempt
to
fall
back
and
pull
that
as
an
oci
artifact,
and
this
is
this-
is
intended.
This
is
nice
because
you
know
just
like.
I
was
talking
a
little
bit
later
here.
A
If
you
have,
you
know,
build.com
my
artifact
slash,
wasm
or
something
that's
a
that's
a
valid
path
and
a
valid
oci
reference
depending
on
you
know
where
it
is,
but
in
general,
like
the
experience
of
trying
to
inspect
a
local
file
and
then
getting
an
error
about
pulling
images
is
a
little
bit
of
a
confusing
experience.
So
I
think
a
good
way
to
improve
this
would
just
be
to
you
know
mention
that
we
couldn't
find
a
file
instead
of
instead
of
that
fallback
error.
A
So
this
is
another
great
place
to
to
help
aid,
the
developer
experience
and
any
initial
confusion,
and
the
last
one
I
wrote
this
morning
while
frustrated,
because
this
happened
to
me
a
ton
of
times
where
I'll
write,
something
like
wash
key
gen
cluster.
But
the
command
is
wash
keys,
gin
cluster
to
generate
an
n
key.
It
is
such
a
such
a
small
knit
but
clap.
A
A
So
all
of
the
community
calls
this
week
are
on
wash
or
the
wasm
cloud
shell.
So
it's
a
rust
project
if
you're
new
to
a
new
to
rust.
All
of
these
things
are
pretty
quick
fixes
that
make
an
impact.
That's
what
we
try
to
do
for
our
good
first
issues
here.
So
if
anybody
has
any
questions,
feel
free
to
ask
them
now
or
if
not
just
or
if
you're.
A
All
righty,
I
think
that
that's
all
that
I
had
for
the
you
know
the
structured
part
of
the
community
meeting.
Anybody,
let's
see
jordan
earlier,
you
were
talking
about
an
issue
with
like
the
wash
container
breaking
on
the
latest
build.
Do
you
want
to
talk
about?
You
know
what
happened
there,
what
the
what
the
fix
was.
D
D
So
locally
I've
gone,
I've
tagged
the
wash
container
to
alpine
three
one
five
and
then
alpine
to
three
one
five,
but
I
have
not
pushed
that
because
I
don't
know,
I
don't
know
what
that
means
long
term
right,
I
don't
know
if
wash
will
need
316
to
build
eventually
or
not
so
I
had
to
do
it
really
quick,
because
the
training
scenario
that
brooks
just
demoed
was
crashing
it's
back
up
now,
but
yeah,
that's
probably
an
issue.
I
need
to
write
up.