►
Description
In this episode, Aaron catches up with Loren Sands-Ramshaw of Temporal. In it they talk about durable execution, Loren's book on GraphQL, getting through system design interviews, and his upcoming talk at Cassandra Forward. Also, this is the first episode that we're trying out a video podcast format.
A
B
Consulting
full
stack,
mobile
and
web
dev
and
writing
a
book
on
graphql
and
then
after
I
finished
the
book
I
spent
a
few
months,
not
a
few
months.
Maybe
three
months
I,
don't
know
it
was
a
long
time
applying
to
to
big
check.
Full-Time
jobs
and
I
had
a
few
offers,
but
was
waiting
on
Google
because
their
process
was
the
longest
by
far
and
while
I
was
doing
that,
I
got
a
a
a
a
new
newsletter
from
swix
Sean
Wang
about
iPhone
for
system
design.
B
My
favorite
part
of
the
interview
process
for
big
Tech
was
the
system
design,
questions,
interview,
questions
sure
and,
and
this
blog
post
sort
of
explained
temporal
and
and
pitched
it
as
like.
This
is
the
thing
that
solves
a
lot
of
your
system,
design
problems
or
distributed
system
problems
in
general
and
and
I
was
like.
B
Oh,
my
God
I
can
use
this
as
the
answer
to
lots
of
my
interview,
questions
and
it's
it's
so
much
simpler
and
easier
to
to
use,
and
he
offered
me
a
Consulting,
gig
sort
of
learning
it
and
and
explaining
it
improving
like
examples
and
stuff,
and
that
was
like
a
dream
job
so
I
did
that
and
then
I
wound
up
joining
full
time.
I
worked
on
the
the
node
runtime
and
now
I'm
switched
to
devrel.
B
A
B
I
came
across
graphql
and
I
was
like.
Oh
my
gosh.
This
is
this
is
a
great
improvement
over
rest
and
whenever
I
guess
back
then
now
now
when
I
learn
something
new,
I
go
straight
to
Youtube,
but
back
then
I
used
to
always
buy
the
book
and
there
wasn't
a
book
that
I
liked
about
graphql
out
at
the
time
that
I
was
trying
to
learn
it
yeah
I
I
think
this
is
a
great
thing.
B
I
think
it's
gonna
like
improve
developer
experience
for
everyone
in
the
world
and
I
wanted
people
to
know
about
it
and
be
able
to
learn
it
efficiently.
So
I
was
like
I
could
write
a
book
and
and
I
I
did
it
took
a
bit
longer
than
I
thought
it
would.
It
was
like
a
five-year
project
and
wow
almost
900
Pages,
it's
a
it's,
a
very
big
book.
B
I,
don't
think
I
could
be
printed,
I
think
it's
too
long
for
a
print,
but
it's
a,
but
it's
an
ebook
and
a
website
version
and
and
yeah
I
guess
like
I,
it's
the
I
think
the
most
most
comprehensive,
graphql
single
resource
out
there
and
it
it
teaches.
Like
goes
through
the
spec
teaching
you
it
and
then
it
goes
through
a
different
different
front
ends
and
back
end
as
sort
of
a
long
tutorial
style
where
it
teaches
each
concept
with
examples.
Okay,
oh
excellent.
A
A
B
B
Sure
so
it's
a
it's
a
new
sort
of
model
of
programming
in
which
you
are
programming
at
a
higher
level
of
abstraction,
where
you
don't
have
to
be
concerned
with
a
number
of
different
distributed
system
concerns
and
you
can
and
and
we
can
and
I
guess,
once
you
write
a
durable
function,
it
is
guaranteed
to
complete
no
matter
what
happens.
Okay,
and
that
includes,
like
your
process,
crashing
your
process
being
killed
by
the
OS.
B
B
This
sort
of
takes
care
of
all
that
for
you
and
automatically
retries
with
that
special
back
off
and
does
so
reliably
and
at
high
scale.
So
yeah,
and
also
like
opens
up
some
new
possibilities
like
sleeping
for
30
days
and
not
reliably
working,
and
you
can
also
like
send
rpcs
to
your
your
durable
functions,
to
give
them
instructions
or
or
get
back
information.
You
can
also
have
them
run
an
indefinitely
long
period
of
time
and
you
can
treat
local
variables
as
as
durable
or
as
personable.
B
A
A
Yeah
yeah,
okay,
okay,
so
so
what
would
you
say
your
your
experience
was
with
Cassandra
was
it
you
know
hey.
This
is
hey.
This
is
great
or
maybe
hey.
This
needs
a
lot
of
work
or
you
know.
I
know.
I,
know
that
developer
friendliness
is
something
that
that
we've
been
working
on
to
improve
for
for
quite
a
while,
so
I'm
I'm
curious
to
know
you
know
from
a
from
a
newcomer.
You
know
what
was
your
you
know.
What
was
your
perspective
on
that.