►
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
Welcome
to
awesome
cloud
wednesday
for
february
the
23rd
2022
as
usual,
we
want
to
start
with
a
demo.
We've
got
three
quick
demos
today,
let
me
start
with
one
that
was
submitted
to
us
via
our
slack
channel,
and
this
is
neat.
I'm
gonna
try
to
get
alan
to
come
out
and
give
a
longer
presentation
on
this.
A
But
what
alan
has
created
here
is
a
multiplayer
browser
game
built
with
bevy
and
wasn't
cloud
as
the
back
end
and
he's
open
sourced
all
of
this-
and
I
kind
of
put
it
out
here-
and
it
looks
like
some
pretty
interesting
stuff
that
he's
got
between
his
game
logic
and
and
all
the
actors
that
he
was
able
to
build
and
put
in
here.
A
So
I'm
pretty
excited
to
tear
into
this,
but
we'll
put
a
link
to
this
in
our
slack
channel
for
folks
that
want
to
play
and
and
then
I
want
to
hand
off
the
mic
for
our
next
demo
to
matt
matt.
You
want
to
take
a
second
and
maybe
introduce
yourself,
and
then
you
can
introduce
the
topic
you'd
like
to
bring
up
today.
B
Sure
so
ty
my
name's
matt
gilbride.
I
will
I've
been
lurking
for
a
while
making
pedestrian
contributions
with
brooks
to
wash
in
between
child
rearing
and
and
my
day,
job,
and
I
started
about
a
year
ago
wanting
to
poke
around
with
rust,
and
I
created
a
little
game
if
anyone's
heard
of
code
names,
it's
a
board
game
popular
here
in
the
us,
with
with
rust
as
the
rest
service
backing
the
game.
B
So
I
kind
of
pulled
out
all
the
component
parts,
and
now
the
backing
data
store
is
dynamodb,
which
kind
of
inspired
me
to
want
a
dynamodb
provider
of
sorts,
so
I've
begun
work
on
a
provider
called
kv
dynamodb
yesterday
and
I've
just
gotten
to
the
point
where
I
have
some
methods
to
set
and
get
keys
in
dynamodb
and
it's
it's
brought
up
some
interesting
interesting
conversations
about
what
dynamodb
is,
I
think
in
some
cases
it
could
be
a
key
value
provider.
B
Some
could
argue
that
there
are
use
cases
where
it's
a
blob
store
and
like
lots
of
things
in
between,
but
I'll
post
I
can
share
liam
or
I
can
just
post.
The
links
in
the
channel
here
is
the
the
game
that
is
currently
not
running
on
wasm
cloud
under
the
hood,
but
hopefully
will
be
soon
and
here's
the
repo.
A
B
Here
we
go
so
code.
Names
is
a
pretty
rudimentary
kind
of
word
game
for
those
of
you
that
are
familiar
where
you
essentially
have
a
team.
Two
teams,
a
red
team
and
a
blue
team,
are
attempting
to
guess
which
of
these
cards
are
red
or
blue,
based
on
a
clue,
which
is
any
other
word
that
someone
called
the
spymaster
will
give
them.
So
if
I
join
a
team,
for
instance,
as
a
spy
master.
B
I
now
can
see
the
answers
right
and
I
would,
for
instance,
try
to
get
my
teammates
to
connect,
putting
myself
on
the
bot
spot
here
say
pants
and
police,
which
are
both
blue
words
by
throwing
out
some
other
word
and
hoping
that
they
associate
those
two
words
together
and
don't
guess
any
of
the
red
words
and
for
sure,
don't
guess
what
is
called
the
death
card,
which
immediately
ends
the
game.
So
you
can
imagine
there's
like
some
kind
of
basic
rest
api.
B
So
let's
say
I
want
to
give
a
clue
of.
You
know
closed
interactions
going
on
here,
I'll
go
back
and
log
in
as
another
user.
So
if
I'm
now
not
spymaster
the
blue
team
member.
B
May
want
to
guess
say
I
want
to
guess
the
word
shot
and
then
see
that,
like
okay,
all
right,
that
was
a
blue
word.
So
that's
the
game
and
behind
the
scenes
here
I
actually
implemented
the
service
layer.
You
know
in
attempts
to
learn
rust
in
kind
of
three
different
pieces,
so
one
piece
is
called
domain.
That
is
just
intended
to
be
pure
rust,
business
logic.
B
Another
piece
is
called
actics,
which
is
just
a
rust,
actix
web
implementation
of
the
game,
which
is
what's
running
now
and
then
a
now
defunct
piece
called
wasm,
which
was
intended
to
be
the
equivalent
wasn't
cloud.
Wasm
cloud
wasn't
cloud!
Sorry
if
I
mispronounced
implementation
of
the
the
game
logic,
so
it
took
a
bit
of
effort.
There's
been
a
few
iterations
where
I'm
kind
of
pulling
out
component
parts,
so
there
are
less
functional
dependencies
between
architecture
between
pieces
of
architecture
like
front
end
back
end.
B
So
the
last
thing
here
quickly
is
here's,
my
just
some
some
whip
in
progress
fork
of
the
capability
providers
project
where
I've
begun
to
implement
a
you
know:
dynamodb
key
value,
client
that
is
just
interacting
with
a
dynamodb
table
as
if
it's
a
key
value
store.
So
it's
just
using
a
single,
simple
partition,
key
string,
column
or
attribute,
and
then
a
string
value
attribute
is
the
expectation-
and
this
is
caught
off.
B
The
presses
as
of
yesterday
and
I've
just
started
to
ask
some
questions
in
the
channel
about
how
to
test
this
now,
there's
some
rudimentary
functionality
in
existence.
I'm
hoping
that
I
can
push
the
envelope
here
for
a
few
more
weeks
and
get
it
out
there.
C
B
Currently
yeah
so
there's
an
iam
role
assigned
to
the
ec2
instance
that
I
that
I
have
running
out
there
in
authentication
dynamodb,
actually
there's
some
good
work
that
steve
s
did
in
the
blob
store,
s3
provider,
where
you
know
I
just
I
just
wrote,
copied
his
configuration
struct
that
basically
reads:
access
keys
and
secret
keys
from
the
environment
or
from
kind
of
the
provider
chain
of
aws.
B
C
C
B
I
was
gonna
say
there
probably
is
a
like
longer
term
conversation
about
providing
kind
of
generic
interfaces
for
connections
to
the
various
cloud
providers,
right,
what
be
it
azure,
dynamodb
or
azure,
aws,
gcp
and
whomever
else.
A
Yeah,
what
I
was
going
to
add
here
was
there
is
a
couple
layers
of
the
conversation
there
and
as
matt
picked
up.
Steve
is
actually
in
the
process
right
now
of
committing
an
s3,
a
capability
provider
with
integrated
support
for
aws.
A
I
am,
and
in
that
case
it's
compatible
with
the
sort
of
one
of
the
two
standard
kubernetes
ways
of
doing
sts,
which
is
the
temporary
credentials
that
are
granted
via
cube2im
to
a
something
running
in
a
container,
and
that
is
something
that's
being
done
for
one
of
the
cosmonic
enterprise
customers
and
I
think
yes,
there
needs
to
be
some
broader
education
on
that
story
there
and
we're
actually
talking
now
about
putting
an
example
into
the
community
that
may
leverage
that
or
something
along
those
lines,
and
I
think
that
I
would
love
to
know
kevin's
thoughts,
maybe
around
a
two
kind
of
issues
there
in
regards
to
that
on.
A
Is
there
a
broader
pattern
or
framework
that
we
put
out
as
a
separate
capability
provider
or
something
or
separate
library,
kevin
and
and
what
are
your
other
thoughts
and
then
I'll?
Just
dovetail
on
the
second
piece,
nikki
on
retrieving
secrets
for
use.
We
are
also
separately
working
on
a
vault
type
plug-in
for
the
ecosystem.
A
I
don't
know
that
we
discussed
it
internally,
yet
I
I'm
under
the
impression,
though,
that
we're
open
sourcing
that
and
putting
that
into
awesome
cloud
as
just
another
capability
provider.
You
know
we
get.
I
think
we've
got
a
deep
understanding
of
the
enterprise,
pain
and
suffering
and
all
the
requirements
that
come
in
from
all
the
places
and
those
are
exactly
what
we're
letting
people
guide
us
to
from
a
prioritization
order
kevin.
Do
you
want
to
maybe
chime
in
on
that.
D
D
You
know,
client
sdk,
abstractions
across
you
know,
multiple
clouds,
but
so
yeah.
I
guess
it's
really
just
a
matter
of
trying
to
figure
out
where
the
abstraction
ends
and
you
know,
trying
to
reuse
as
much
code
as
possible,
but
I
mean
for
for
rust
anyway,
there's
a
fairly
decent
aws
client
sdk
that
works
pretty
well.
If
you
were
going
to
write
your
capability
provider
in
go,
I
think
that
that
one
may
even
be
in
better
shape
than
the
rust
one.
So
it
really
just
depends
on
which
cloud
you're
trying
to
interact
with.
C
So
so
I
I
agree
with
everything
you
said
kevin
and
I
agree
it's
a
fool's
errand
to
try
and
solve
it,
because
it's
just
not
gonna
work,
but
I
think
what
what
would
be
helpful
I
mean
for
someone
like
me
right
would
be
like
here's
an
established
pattern,
and
this
established
pattern
uses
this
role
and
if
you
do
these
three
four
five
things
whatever
they
are,
your
provider
can
now
access
that
role,
whether
it's
through
an
sts
token
or
inherited
inherit
the
role
from
an
ec2
instance
or
whatever
right,
but
the
relationship
again,
I'm
speaking
mainly
on
from
aws,
because
that's
my
familiarity,
but
I'm
guessing
this
transposes
to
other
clouds
too
right.
C
D
I
wonder
what,
like
you
said,
you're
spot
on
in
that
this
isn't
a
problem.
The
you
know,
connectivity
to
these
clouds,
isn't
our
problem
to
solve
that.
That's
the
the
realm
of
the
client
sdks,
but
one
thing
that
we
might
be
able
to
do
is
extract
to
this
pattern
of
making
something
I
am
compatible
into
like
one
of
the
templates.
So
right
now
you
know
when
you
do
wash
new
provider.
D
I
think
we
prompt
you
for
which
kind
of
provider
you
want
to
see
as
an
example,
one
of
the
things
maybe
we
could
look
into
doing
is
as
an
example.
When
you
do
wash
new,
we
could
prompt
you,
for
you
know
one
of
the
options
might
be
like
an.
I
am
compliant
provider,
and
it
includes
you
know
the
the
boilerplate
necessary
to
get
that
job
done.
C
Right
and
and
the
tying
them
from
the
provider
down
to
the
role
right
like
that
to
me,
is
a
critical
step
that
it's
then
it's
up
to
the
person
to
figure
out.
Oh
well,
you
know
this
example
to
use
this
role,
so
this
is
how
I
change
it,
and
you
know
I
think,
just
drawing
out
the
stepping
stones,
I
think
would
be
tremendously
helpful
and
then
people
can
decide
if
they
want
to
skip
a
stone
or
give
everything
admin
ads
to
us.
I
mean
you
know
whatever
they
want
to
do
right.
A
Well,
certainly,
nicki,
in
addition
to
examples
we'll
get
some
documentation
out.
Steve
just
got
the
first
pass
of
that
that
checked
in
just
recently
matt.
I'm
glad
that
you
noticed
that
and
we're
able
to
leverage
that
work
already,
but
we'll
make
sure
that
we
include
documentation
and
some
guidance
in
watsoncloud.dev
as
we
get
it
up
and
just
this
morning
in
our
earlier
meeting,
we
were
discussing
what
would
the
demo
look
like
that
we
would
put
together
to
put
into
the
community.
So
we
had.
A
You
know
some
more
enterprise
examples
of
hey
here's,
a
common
deployment
scenario,
for
example.
How
would
you
integrate
with
that
and
matt?
It
sounds
like
if
you've,
if
you've
built,
if
you're
building
another
one
here,
there's
multiple
examples
to
get
that
out.
Matt.
I
really
appreciate
your
demo.
Are
there
any
other
questions
across
the
community
for
matt
and
the
dynamodb
stuff
that
he's
working
on
now.
B
I
had
one
kind
of
other
comment:
kind
of
related
to
nikki's,
not
related
to
authentication,
so
to
speak,
but
testing
only
because
it's
front
of
mind.
You
know
the
immediate
thing
that
I
want
to
do
now
that
I
have
kind
of
a
hello
world
capability
provider
that
interacts
with
aws
is
tested
in
some
way
shape
or
form,
and
it's
not
abundantly
clear
to
me
from
like
a
high
level
approach,
how
I
might
want
to
do
that,
whether
it
be
you
know
in
the
case
of
dynamodb,
you
can
actually
run
a
local
dynamodb
instance.
B
It's
like
a
first
party
thing
provided
by
aws,
but
other
cloud
services
may
or
may
not
have
something
that
you
can
run
locally.
So
it's
just
kind
of
a
thought
to
throw
out
there.
You
know
spaghetti
against
the
wall,
how
we
kind
of
provide
some
best
practices
in
terms
of
testing
capability
providers
that
interact
with
cloud
service
providers.
D
There
yeah,
I
think
there
there's
a
lot
of
opportunity
for
us
to
smooth
out
how
the
the
provider
test
harness
works,
and
normally
this
is
where
I
would
just
hand
it
over
to
steve
and
have
him
comment
on
the
provider
tests
and
see
he's
the
one
who
wrote
it
but
yeah.
D
I
think
if
there
are
specific
things
that
you
that
you've
had
trouble
with
around
that
we'd
definitely
like
to
hear
hear
those,
but
I
wouldn't
be
surprised
if
we
went
about
refactoring
the
way
we
do
provider
tests
in
in
the
near
future,
because,
ideally,
I
want
to
make
sure
that
you
know
that
stuff
is
as
easy
as
possible
to
test.
A
So
it
sounds
like
maybe
we
can
ask
steve
to
do
an
update
on
that
next
week,
when
he's
on
I'll
note
that
for
next
week's
meeting,
if
there
are
no
other
questions,
I
think
nikki
you
had
something
you
wanted
to
share
in.
Today's
call
is
that
right.
C
C
It
looks
like
it
okay,
so
let
me
just
kind
of
sort
of
lay
like
a
very
short
context
here.
This
is
kind
of
a
reflection
of
me
primarily
is
like
again.
The
way
I
think
is,
I
need
to
see
the
big
pieces,
and
when
I
see
the
big
pieces
then
I
can
like.
I
can
then
make
the
connections,
but
if
I
don't.
C
I'm
just
like
a
child,
I'm
just
lost
right,
so
I
mean
you
know
working
with
you
guys
over
the
last
month
or
two
I
kind
of
lose
track
of
time,
and
you
know
I
I
hear
about
these
pieces
of
technologies
and
I
always
ask
myself
well
how
do
they?
How
do
they
relate?
Because
until
I
can
draw
those
relationship
again,
I'm
lost
so
what
I
did
was.
I
talked
a
little
bit
about
this
with
liam
and
I
know
I
flooded
the
channel.
D
C
C
I
talk
about
like
well,
you
know
everything's
improved,
except
for
application
management,
which
is
still
kind
of
a
bear,
the
place
that
I
would
like
feedback.
The
most
is
on
these
two
slides
and
I'm
looking
for
like
technical
accuracy.
So
here
I
start
talking
about
you
know,
obviously
the
sandbox,
it's
locked
down.
You
have
the
notion
of
pride.
You
have
the
notion
of
an
actor
if
I
go
a
little
bit
further,
the
notion
of
the
lattice
and
there's
a
notion
of
a
contract.
C
Again,
I
believe
this
is.
I
I'm
pretty
comfortable
in
saying
it's
thematically
correct,
but
I
may
have
gone
to
detail
wrong
that
maybe
kevin
or
brooks,
or
someone
else
would
pick
up
that
you
know
is
completely
lost
on
me,
in
which
case
I'm
happy
to
make
a
correction,
and
then
the
next
discussion
is.
Is
this
one
that
I
know
that
I've
I
showed
briefly
I'll?
Let
me
screw
it
over
to
that
side
right.
So
something
like
this,
where
I
start
babbling
about.
C
Okay,
you've
got
multiple
clouds,
multiple
providers,
this
guy
initially
connect
to
this
guy,
but
this
guy
had
a
heart
attack,
so
this
guy
reconnected
to
this
provider
over
here
right.
So
where
I
would
like
the
most
feedback.
Is
these
two?
Obviously
any
feedback
is
good
feedback,
so,
but
I'm
looking
the
part
that
I'm
personally
most
concerned
about
is
make
sure
this
is
technically
correct.
C
Again,
I
believe
it
is
in
terms
of
stylistically,
I
I
know
I
purposefully
speak
very
slowly
and
there's
a
reason
for
that,
because
you
know
I'm
trying
to
try
to
make
this
as
public
as
I
can,
including
non-native
english
speakers.
So
speaking,
a
little
bit
slower
might
help
a
little
bit
there.
C
A
Nikki
I
know
I
looked
at
an
earlier
version
of
with
you,
but
I
I
haven't
looked
at
this
version
yet
and
I'm
excited
to
see
where,
where
it's
at
and
give
you
some
feedback,
and
I
think
if
a
couple
people
in
the
community
can
help
contribute
to
that
discussion.
We
can
put
this
on
all
the
twitters
and
tweet
it
all
out
and
linkedin
and
all
the
places-
and
you
know
try
to
get
some
views
on
it.
C
Yeah
and
so
what
I've
done
so
far,
is
I
just
put
it
on
youtube?
I
didn't
I
just
told
like
a
handful
of
people
that
it
was
there.
I
didn't
tell
a
lot
of
people.
Obviously
I'm
only
now
telling
this
channel
but
yeah.
You
know
I'd
like
to
I'd
like
to
post
on
my
linkedin,
but
again,
you
know
any
feedback
that
I
have
prior
to.
That
is
good
and
again,
the
the
notion
here
is
this
is
just
setting
a
foundation.
C
A
Nikki,
can
you
put
that
into
a
slack
just
so
folks
that
are
following
along
in
general
or
wherever
have
a
chance
just
to
give
you
and
maybe
do
a
call
out
and
just
ask
for
feedback
on
it
and
then
I
think
once
you're
again,
you
know
my
perspective.
Was
I
really
wanted
this
in
your
voice,
because
I
think
the
more
voices,
the
more
diverse,
the
descriptions,
the
better
we
can
connect
with
different
personas
and
people
with
different
backgrounds,
and
things
like
that.
A
A
Okay,
a
couple
quick
community
call
outs.
I
want
to
do
a
quick
call
out
to
the
we
love
tech
series
that
red
badger
is
hosting
there's
still
plenty
of
time
to
get
signed
up
for
that
and
stuart
you're
on
the
call.
Is
there
anything
you
want
to
mention
about
the
current
plans
or
how
things
are
going.
E
Yeah,
thank
you
yeah.
It's
a
week
today
and
taylor
and
brooks
are
talking.
We
did
a
bit
of
a
run
through
with
the
av
stuff
this
afternoon,
which
is
much
appreciated
their
time.
Yeah.
It's
really
it's.
I
think
it's
going
to
be
exciting.
We've
got
a
talk
from
single
store
as
well
as
cosmonaut,
and
I
think
it's
going
to
be
we're
going
to
look
at
different
ways
in
which
was
webassembly
is
being
used
outside
of
the
browser.
A
Okay,
that's
awesome
and
then
another
we'll
put
a
link
to
this
in
both
slack
and
we'll
tweet,
this
out
as
well
stewart
to
try
to
help
get
folks
registered
for
that
and
then
an
additional
call
out,
there's
still
time
to
submit
for
the
2022
kubecon
eu
webassembly
day
I'll
put
the
link
into
slack
as
well,
but
submissions
are
open
until
the
28th,
so
you
still
have
five
days
to
pull
together
submission.
A
Anything
that
is
tangently
involved
in
cloud
native
and
web
assembly
is
welcome
for
the
event
that
we're
trying
to
curate
we
have
been.
I
think
we
were
the
highest
rated
focused
day.
Last
year
we
got
a
4.5
out
of
five.
We
received
a
gold
dni
award
and
we
had
around
300
attendees
at
kubecon
us
accounting
all
of
the
online
there's
a
slight
change
in
the
attendance
this
year.
A
So
I
think
we'll
have
an
even
bigger
turnout
this
year,
if
you
buy
an
online
ticket
for
kubecon
your,
it
includes
full
access
to
all
of
the
day
content.
So
I
think
we've
now
opened
it
up
to
the
you
know,
20
to
70
000
registries
registries,
depending
on
how
quickly
we're
returning
to
normal
numbers
this
year.
If
you
want
to
go
and
attend
on
site
in
valencia,
spain,
this
may
you
still
do
need
a
ticket
for
that,
because
there's
meals
and
catering
and
facilities
and
support.
A
So
I
still
really
welcome
and
encourage
anyone.
If
anyone
has
questions
or
like
some
assistance
or
guidance
in
submitting
a
talk,
please
don't
hesitate
to
reach
out
to
me,
I'm
happy
to
help
give
you
some
advice
or
feedback
on
a
submission
and
how
you
can
dial
it
in
to
get
the
best
look
possible
with
that
I'd
open
it
up
any
other
community
call
outs
or
events
that
people
are
aware
of.
A
Now
we
have
some
fun
demos
coming
up
in
the
next
few
weeks,
with
some
big
performance
improvements
that
we're
unlocking
and
and
other
things.
But
if
there's
no
other
topics,
we
can
go
ahead
and
call
today's
meeting
and
I
look
forward
to
seeing
everybody
next
week
actually
next
week,
I
will
not
be
here,
I'm
going
to
be
on
vacation
next
week
so
brooks.
Maybe
you
can
be
our
our
benevolent
coordinator
since
you
do
most
of
the
talking
anyway,
in
the
meetings.
F
Yeah
here
we
go,
you
check
my
name
really
quick
in
the
oh
yeah.
That's
right!
That's
right
hold
on
not
that
not
that
there
we
go.
A
F
A
A
Right
all
right,
we
can.
I
look
forward
to
seeing
how
all
liam
goes.
I'm
gonna
try
to
listen
in
at
least,
but
I
think
I'm
gonna
be
in
an
airport
or
possibly
even
on
a
plane
when,
when
the
meeting
happens
based
on
my
current
schedule
so
to
be
continued
with
next
week
with
alt
brooks,
I
mean
alt
liam.