►
From YouTube: Closing Remarks - Bernard Kolobara, Lunatic
Description
Closing Remarks - Bernard Kolobara, Lunatic
WebAssembly is finding its way into different companies and technology stacks. In this closing session, I will share our personal story and why we chose WebAssembly as the central component of our architecture.
A
Hi
everyone
welcome
to
the
last
session
of
today.
I
promise
I'm
going
to
make
it
quick,
so
we
can
all
head
to
the
party
afterwards,
so
I'm
bernard
colobara,
I'm
the
co-founder
and
ceo
of
lunatic
at
lunatic
we're
building
a
web
assembly
platform
inspired
by
erlang
principles.
This
means
massive
concurrency,
soft,
real
time
and
fault
tolerance
to
wrap
up.
Today.
I
would
like
to
share
with
you
a
bit
of
our
story
why
we
chose
web
assembly
for
our
stack
and
especially
how
it
helps
us
around
the
fault.
Tolerance,
part
of
our
platform.
A
I
started
my
career
in
it.
Support
and
a
big
part
of
my
day-to-day
job
was
just
to
go
around
and
turn
things
off
and
on
again
it
became
somewhat
of
a
joke
in
the
I.t
world,
but
believe
me,
it's
like
a
really
effective
method
in
fixing
issues,
it
comes
from
the
fact
that
long-running
applications
tend
to
get
stuck
in
an
unpredicted
state.
A
So
the
best
way
to
recover
from
this
error
is
just
to
revert
to
a
well-known,
fresh
state
and
also
it's
the
state
that
got
the
most
testing
out
because
developers
when
they
write
some
application.
They
write
some
code,
then
test
it
and
then
write
more
code
test.
It
again.
So
like
this
fresh
start
after
the
application
just
starts,
it's
usually
really
well
tested
and
erlang.
The
programming
language
takes
this
principles
and
applies
it
to
software
development,
and
this
approach
has
proven
to
create
some
of
the
most
resilient
applications
out
there.
A
It
works
in
erlang,
because
the
whole
programming
language
was
designed
around
this
concept
of
small
processes
that
don't
share
any
state
with
each
other.
This
means,
if
one
of
them
fails,
we
can
safely
restart
it
while
the
rest
of
the
system
keeps
running.
This
is
also
known
as
the
let
it
crash
philosophy
in
the
erlang
world
and
with
lunatic.
We
are
trying
to
bring
this
approach
to
all
programming
languages
using
webassembly,
to
show
you
how
we
do
it.
Let's,
for
example,
take
rust
rust
application
usually
share
a
whole
memory
space.
A
So
there's
only
one
memory
space
in
the
rust
applications
and
in
this
example,
all
threads
access.
One
shared
state.
This
means,
if
one
of
them
misbehaves
corrupts
the
state
it's
kind
of
corrupted
for
everybody
else.
So
if
we
just
shut
off
one
thread
restart
it,
this
would
actually
not
really
help
us
because
the
thread
would
be
respawned
inside
of
the
same
memory
space.
This
means
that
we
need
to
take
a
different
approach.
A
This
is
also
true
for
asking
tasks
in
essence,
rust
all
the
tasks
run
in
one
memory
space
and
can
reference
the
same
memory
locations.
So
we
never
really
have
the
guarantee
if
we
restart
it
that
it
will
start
from
a
fresh,
completely
new
state.
So
what
we
do
with
lunatic
is
we
introduce
a
new
concurrency
model
to
rust
turn
each
task
into
a
web
assembly
instance.
So
each
of
the
tasks
gets
a
linear
memory
on
its
own.
A
This
means
that
it's
safe
to
restart
each
individual
task
and
we
can
guarantee
that
the
memory
is
going
to
be
completely
fresh
and
the
state
is
going
to
be
new
and
to
be
able
to
do
this.
It
feels
a
bit
like
a
superpower
right
because
the
rust
language
was
not
even
designed
to
be
able
to
support
this
just
by
applying
web
assembly
to
it.
A
A
This
run
photoshop
figma
google
earth
all
at
a
high
frame
rate
inside
of
the
browser,
and
it's
also
bringing
compute
closer
to
our
data
in
the
database
and
also
compute
closer
to
the
users
on
the
edge,
and
it's
powering
a
lot
of
new
innovation
in
the
cloud
native
space
and
bailey
showed
also
today
in
the
keynote
many
more
use
cases
for
web
assembly.
Every
time
I
talk
to
somebody
new
that
uses
webassembly.
A
They
kind
of
show
like
a
slightly
different
variation,
how
they
are
using
webassembly
to
solve
their
problems
and
that's
why
I'm
really
grateful
that
we
have
events
such
as
today,
where
we
can
all
meet,
share
our
experiences,
how
we
use
web
assembly
and
learn
from
each
other,
and
I
would
like
to
finish
today
by
thanking
everybody
who
made
this
event
possible.
I
would
like
first
of
all
to
thank
all
the
organizers
and
program
committee,
matt
butcher,
taylor,
dolezal,
divia
mohan,
liam
randall
ralph
squillacci
lindsay
jean-draw
and
sheriff
wembley.