►
From YouTube: .NET Foundation Project Spotlight - Orleans
Description
.NET Foundation Marketing Committee member Isaac Levin spoke to Reuben Bond, one of the maintainers of Orleans. For more detail, be sure to check out the Project Spotlight page
https://dotnetfoundation.org/projects/spotlight?project=Orleans
A
Hi
everybody
another
episode
of
project
spotlight
here:
I'm
isaac
levin
from
the
marketing
community
for
the
donna
foundation.
I'm
super
excited
to
have
reuben
from
the
orleans
project.
Join
us,
hello,
reuben,
hi
isaac
awesome,
so
reuben,
let's
just
get
started.
So
let's
talk
about
you
know
what
is
orleans
I
mean
I
bet.
A
lot
of
people
are
curious.
You
want
to
give
me
a
little
high-level
intro
to
it.
B
Yeah
sure
so
orleans
is
a
framework
for
helping
you
to
build
distributed
systems,
and
usually
that
sounds
kind
of
scary
like
what
is
distributed,
but
you
can
just
think
of
it
as
any
time
that
you
have
a
bunch
of
instances
of
your
application
and
you
want
to
make
them
work
together
in
a
cloud-native
way.
Orleans
is
good
for
those
kinds
of
scenarios,
so,
if
you're
running
on
kubernetes
or
azure
app
service
or
any
other
kind
of
place,
where
you've
got
you
know,
multiple
instances
of
your
app
orleans
is
good
help.
There.
A
Awesome
so
obviously
it
makes
like
it
sounds
a
lot
like
microservice
architecture
right.
A
lot
of
people
talk
about
microservice
architecture,
all
the
time,
so
what
it
makes
orleans
interesting
for
net
developers
versus
you
know
more,
like
you
said,
kubernetes
or
using
any
of
the
other
different
paradigms
out
there.
B
Yeah,
so
one
of
the
things
that
orlando
allows
you
to
do
is
to
build
applications
that
are
very
they're,
very
net
native
right,
so
they'll
feel
like
regular.net
apps,
so
you're
writing
applications
you're
using
these
cloud
native
objects
that
are
called
grains
and
that
just
don't
make
classes
right
and
they
they
talk
to
each
other
by
making
method
calls
on
each
other.
You
handle
errors
using
exceptions
like
try,
catch,
etc.
A
A
That's
great,
I
imagine,
a
lot
of
the
developers
would
see
orleans
and
they'd
say.
Oh,
this
is
completely
different
than
how
you
know
typical
microservice
architectures
are
written
right,
they're
using
go
or
something
else
right.
I'm
curious
to
know
moving
how
you
got
started
with
orleans
right.
So
obviously
you
know
you
work
at
microsoft.
Now,
I'm
curious
as
to
when
you
got
started
with
orleans
and
what's
your
first
impressions
were
of
it.
B
Yeah,
so
I
think
it
was
a
long
time
ago,
maybe
around
2015
or
maybe
even
earlier.
I
was
just
working
on
my
own
thing
in
open
source
and
and
orleans
came
out.
I
liked
it
a
lot
right.
I
guess
I
fell
in
love
with
it
and
I
started
contributing
it
contributing
to
it.
I
think
very
early
on
maybe
even
maybe
even
submitted
the
first
pr
to.
A
B
Don't
know
if
I
needed
it
that
quickly,
but
I
was
ready
for
it.
I
actually
I
knew
exactly
what
I
wanted
to
contribute
and
I
heard
that
I
was
gonna
become
open
source
and
so
as
soon
as
it
did,
I
said
I'm
going
to
fix
this
one
little
configuration
thing
and
from
there
I
started
taking
on
bigger
and
bigger
tasks
and
and
one
of
the
big
ones
in
the
beginning.
A
More
formally,
that's
great,
so
it
sounds
to
me
like
you
initially
were
a
fan
of
it,
and
then
you
got
into
contributing
how
a
lot
of
people
do
they.
They
want
to
either
open
up
issues
or
contribute
to
via
submitting
code
themselves.
So
you
know
for
folks
that
are
in
the
same
vein,
maybe
as
you
were
in
the
past
and
they're,
they
see
orleans
they're
heavy
users
of
it
and
they
want
to
contribute
what's
the
best
way
for
them
to
do
that.
B
B
So
even
if
it's
you
know
get
kind
of
knowledge
or
or
if
it's
you
know
etiquette
around
opening
prs
and
things
like
that
or
coding
conventions
and
and
whatnot,
we
can
help
you
through
that
and
then
get
your
coding
right.
If
you've
got
an
idea,
maybe
we
can
help
you
implement
it
right
and,
and
some
ideas
in
the
past
have
ranged
from
very
small
things
or
maybe
medium-sized
things
like
you
know,
contributing
plug-ins
for
the
different
database,
back-ends
for
streaming
or
storage,
or
something
like
that,
or
even
things
which
change
fundamentals.
B
A
That
sounds
great,
so
I'm
curious,
you
you
make
it
sound
like
there's
a
ton
of
great
community
work,
that's
going
on
with
orleans,
so
you
know
roughly,
you
know
what
what
would
you
think
the
current
contributors
numbers
are
like
active
contributors
like
how
many
people
are
currently
working
on
orleans,
either
for
a
full-time
job
or
for
a
part-time
job
for
fun?
You
know
maybe
they're
outside
of
microsoft,.
B
So
we
have
our
team
here
at
microsoft,
but
then
outside
there
are
several
people
who
work
on.
You
know
contributing
back
when
when
they
say
they
do
consulting
work,
that
involves
all
these
rights.
So
perhaps
they
work
for
a
game
company
or
they
do
contracting
or
things
like
that
or
they
use
all
liens
in
in
their
own
business.
B
It's
like,
I
need
this
thing,
and
so
I
go
and
implement
that
or
I
need
that
thing,
but
we
tend
to
have
you
know
several
more
prominent
mainstays
as
well
as
a
lot
of
I
like
to
call
them
drive-by
commits
you
know,
someone
might
just
see
something
like
I'll.
Take
that
and
then
they'll
go
and
fix
that
thing
and
you
might
even
never
see
him
commit
again
right.
I
do
a
lot
of
those
same
kinds
of
commits
as
well,
but
but
it's
hard
to
put
a
number
on
it.
A
A
Is
I
take
a
look
at
the
documentation
and
as
a
user
I
always
can
you
know
be
a
quick
judge
of
whether
or
not
a
a
project
is,
is
really
kind
of
they
they're
thinking
like
that
for
their
users
by
how
well
their
documentation
is
written.
So
you
know
what
folks
want
to
learn
more
about
orleans
instead
of
just
going
out
to
the
github
repo.
Is
there
some
formal
documentation
somewhere.
B
Yeah
definitely
so
we
actually
keep
our
documentation
in
a
separate
repo
just
because
it's
a
little
easier
to
organize
it.
That
way.
So
it
does
the
orleans
github
repo,
but
there's
also
the
orleans-dox
rebirth
and
that
has
all
the
source
for
the
documentation.
But
you
can
go
and
look
at
the
precompiled
version
of
that
online.
A
A
B
Well,
that's
a
good
one!
Okay!
So
recently,
we've
had
one
interesting.
One
is
deeper
integration
with
kubernetes,
so
we
have
a
plug-in
essentially
which
allows
you
to
tell
orleans
more
about
the
kubernetes
environment.
So
we
can
sense.
You
know,
based
on
the
kubernetes
environment,
who
were
the
other
clusters,
sorry
who
are
the
other
silos
around
and
they
can
ask
kubernetes
for
more
information
there.
So
that's
one
nice
one,
it's
more
of
a
nicety
than
saying
that's
required,
but
it's
a
nice
thing
to
have
another
one
is
some
improved
stability
for
clustering
itself.
B
So
if
there's
a
network
problem,
that's
just
isolated
to
you
or
if
you've
got
you
know
very
slow
processing
because
of
let's
say
thread
pull
blocking.
Then
you
might
start
saying:
hey
you're,
down
you're
down
you're
down
it's
a
very
rare
kind
of
case,
but
it
can't
happen,
and
so
we
have
extra
extra
resiliency
against
that
now
and
that's
a
recent
change.
I
think
in
the
last
few
months,
but
another
kind
of
a
bigger
one,
that's
kind
of
lower
level
as
well.
A
Yeah
I
it's
just
as
completely
unrelated
to
the
technology
of
orleans.
I
just
love
the
nomenclature
of
the
different
things,
their
name
right,
silos
and
grains.
It
definitely
makes
it
feel
like
it
has
nothing
to
do
with
technology
at
all
right
yeah.
Do
you
know
a
little
bit
about
the
backstory
of
that?
I'm
curious.
B
I
I
don't
know
exactly
where
it
originated,
but
I
think
that
the
team
at
the
time
were
looking
for
a
good
analogy
for
it.
So
when
orleans
was
first
released,
these
things
weren't
referred
to
as
actors,
the
term
virtual
actor,
which
is
like
the
taxonomical
way
of
referring
to
a
grain
in
the
literature
that
wasn't
even
that
wasn't
even
there
yet,
and
so
they
instead
they
said.
Okay,
we
want
something
which
refers
to.
B
You
know
this
little
encapsulation
of
behavior
and
state
in
this
little
unit,
and
then
we
want
to
talk
about
something
which
holds
that
right,
and
so
we
had
grains,
which
is
like
these
little
tiny
things,
and
then
they
live
in
silos.
It's
like
a
grain
silo
one
farm
right,
and
so
the
server
in
orleans
is
referred
to
as
a
silo
right
and
the
little
things
inside
of
it
are
called
grants.
A
Yeah
I
mean
it's
brilliant.
I
think
it
harkens
back
to
you
know
when
you,
you
know
a
long
time
ago,
people
used
to
give
their
servers.
Maybe
they
even
still
do
like
their
servers.
Silly
names,
like
I
remember
at
the
university
I
went
to
all
the
servers
in
the
in
the
department
were
named
after
different.
You
know,
ships
in
in
various
science
fiction.
Television
shows
right,
like
that's
always
a
go-to
for
folks,
but
I
think
using
the
analogy
of
farming
with
grains
and
silos.
B
A
I
think
one
of
the
things
that's
also
really
exciting
about
orleans.
You
know
you
mentioned.
You
know
the
fact.
That's
written
in
c
sharp
and
it's
for
microservices,
which,
as
a
lot
of
folks
know,
is
really
important,
are
not
important
as
much
as
interesting
right
now.
You
know
so
for
folks
that
maybe
aren't
quite
familiar
with
microservices
right.
Do
you
see
orleans
as
a
is
an
interesting?
I
guess
bridge
between
microservice
architecture,
for
folks
that
are
net
developers
by
trade.
B
Yeah,
so
you
can
refer
to
actually
the
first
time
I
ever
heard
micro
services.
It
must
have
been
years
and
years
and
years
ago,
and
actually
the
speaker
was
talking
about
actors.
They
were
talking
about
akka
actors
on
on
scala
right,
and
so
they
said
that
hey
these
actors,
they're
like
little
micro
services
right,
but
then
comparing
actors
which
is
very
similar
in
size
to
a
grain
comparing
that
to
a
micro
service.
B
Today
it
really
it's
more
like
a
nano
service
right
like
it
should,
if
you
think,
of
a
grain
or
actor
as
like
a
a
nano
service
and
you've
got
this
infrastructure
which,
where
you've
got
a
nano
service
architecture
right
these
tiny
little
things
are
communicating
with
each
other.
Now
you
could
say
that
orleans
is
kind
of
like
a
platform
for
building
those
kinds
of
systems,
or
you
could
just
use
orleans
as
a
part
of
a
regular
traditional.
B
I
guess
it's
not
really
traditional,
given
how
new
microservices
is,
but
as
a
part
of
a
regular
kind
of
microservice
architecture.
So
you
know,
maybe
one
service
inside
of
my
microservice
architecture
runs
or
leans,
but
the
others
don't
and
they
can
just
communicate
to
it
using
http
or
grpc
or
signalr
or
whatever.
They
would
like.
A
That's
awesome
I
mean
it
sounds
to
me
like
orleans.
Is
you
know
it
does
a
lot
of
interesting
things,
especially
for
dot
net.
Folks,
because
is
somebody
who's
been
a
dot
developer,
their
entire
career?
You
know
that
just
the
thought
of
having
to
you
know
work
with
different
languages,
not
just
in
different
languages
but
different
architectures
of
services.
A
You
know
whether
it
be
microservice
based
or
event
based
right,
there's
other
programming
languages
that
people
de
facto
go
to
to
write
in
those
particular
tools
right,
but
you
know
having
a
dotnet
implementation
that
does
something
just
as
valuable
and
just
as
I
would
say
just
as
interesting.
It's
super
exciting,
especially
as
somebody
who
is
always
trying
to
learn
new
different
intricacies
of
ways
to
do
things
with
dot
net.
I
see
orleans
is
one
great
example
to
do
so.
B
Yeah
yeah,
I
think
it's
very
interesting
for
someone
who's
not
really
used
to
that
kind
of
way
of
thinking
with
with
say,
grains
or
spreading
objects
around
the
cluster
and,
maybe
is,
let's
say,
they're
more
used
to
message
passing
right
or
cue
processing
instead,
so
I
think
it's
good
to
get
a
different
feel
for
different
different
architectures
and
different
styles,
especially
in
distributed
systems.
I
think
it's
an
interesting
way
to
just
improve,
improve
learning
right.
A
B
So
the
github
reaper
has
a
readme
that
takes
you
through
an
introduction
of
it.
There's
also
a
website
which
is
at
the
the
docs
page.
Essentially,
it's
uh.net.github.io
forward
slash
or
leads,
and
so
that'll
walk
you
through
all
the
conceptual
docs
as
well
as
tutorials
and
some
reference
docs
as
well,
and
then.
A
B
Have
any
questions
there's
github
discussions,
there's
also
github
issues
but,
as
I
mentioned
before,
there's
the
gita
room,
and
so,
if
you
don't
feel
like
my
question,
maybe
is
you
know
maybe
it's
too
basic,
you
think
or
or
whatever
the
case
you
know.
Nothing
is
nothing.
Is
too
simple
or
you
shouldn't
be
embarrassed
about
asking
any
kind
of
question
there,
because.
A
Awesome
so
reuben.
I
want
to
thank
you
so
much
for
hopping
on
project
spotlight
and
talking
to
us
about
orleans
again
so
orleans,
it's
the
github
repo
under
the
net
organization.
So
it's
a
part
of
a.net
foundation.
So,
as
we
close
I'd
like
to
kind
of
get
your
thoughts
as
a
contributor
or
maintainer
how
the
net
foundation
is
has
helped
orleans
and
if
you're,
you
know
whether
it
be
working
with
signing
or
working
with
different
ways
of
documentation
or
just
you
know,
having
something
behind
it
like.
B
Yeah,
I
think
that
the
foundation's
role
in
in
making
a
better
bigger,
more
inclusive.net,
that
also
is
focused
forward
on
adding
on
new
developers.
Right
is
very
important
and,
of
course,
that's
aside
from
things
like
you
mentioned,
signing
and
and
other
facilities
like
that.
That
are
very
useful,
but
I
think
the
net
foundation's
role
in
just
nurturing
the
ecosystem
is
really
saying
they
can't
be
understated.
A
Awesome
again
reuben.
Thank
you
so
much
for
hopping
on
project
spotlight.
You
know
for
everybody
else.
You
know
please
take
up
orleans.
I
I'm
super
excited
to
get
a
little
bit
more
accustomed
with
it.
I
I
played
with
it.
It
feels
like
years
ago
now,
community
two
or
three
years
ago.
I
imagine
things
have
substantially
changed
since
then,
so
I'm
gonna
be
busy
for
a
little
bit
again
reuben.
Thank
you.
So
much.