►
From YouTube: .NET Microservices with Steeltoe
Description
Steeltoe is an open source framework for .NET that provides libraries to build cloud-native and microservice applications.
In this episode, Cecil chats with David and Hananiel from the Steeltoe project to learn about the various scenarios that it enables for .NET developers.
[01:55] - What is Steeltoe about?
[03:31] - How Steeltoe augments existing .NET features?
[07:43] - Getting started demo
[11:25] - Supporting health checks
[16:33] - Distributed tracing and Dynamic logging
[21:58] - What other features does Steeltoe support?
[27:10] - Azure Spring Cloud for .NET support
[28:22] - Learn more about Steeltoe
Get stared
https://steeltoe.io/get-started
Steeltoe on GitHub:
https://github.com/steeltoeoss
.NET Microservices: Architecture for Containerized .NET Applications
https://docs.microsoft.com/dotnet/architecture/microservices/?WT.mc_id=ondotnet-c9-cephilli
Containerized Docker Application Lifecycle with Microsoft Platform and Tools
https://docs.microsoft.com/dotnet/architecture/containerized-lifecycle/?WT.mc_id=ondotnet-c9-cephilli
#aspnet #microservices #dotnet
A
A
A
Now
I'm
really
interested
to
talk
about
this
framework,
because
you
know
it's
right
now:
it's
running
on.net
core
30,
it's
running
as
a
part
of
the.net
foundation
set
of
projects,
and
we
actually
have
some
folks
here
from
the
team
that
are
going
to
talk
to
us
a
little
bit
about
how
the
project
works,
and
you
know
what
are
some
of
the
benefits
of
us
even
looking
at
and
using
instituto
in
some
of
the
work
that
we
do.
So
why?
C
Awesome,
I'm
helenio
sarola
and
I've
been
with
the
steeltoy
team
for
a
couple
of
years
now,
but
I've
been
a
dotnet
developer
for
almost
20
years,
just
about
as
soon
as
dot
net
came
out
and
then
later
I
switched
to
beings
doing
some
java
development
and
that
made
me
a
good
fit
for
our
team,
and
so
here
we
are
very
excited
to
be
here
as
well.
Thank
you
for
having
us
on
sizzle.
A
Sure
I
find
like
it's
hard
to
just
be
around
the
technology
space
and
not
hear
someone
say
the
word
microservices.
It's
like
microservice,
this
and
microservice
that
and
platforms
and
frameworks
and
libraries
and
all
kinds
of
stuff,
and
I
think
it'll
be
really
interesting
to
see
what
exactly
steeltoe
does
for
the.net
developer
to
make
microservices
like
a
really
comfortable
thing
to
do.
I
think
when
we
talk
about
things
like
tooling
familiarity,
you
know
just
overall
developer
experience
and
ease
of
use,
like
those
things
are
really
important
for
adoption.
A
B
First
of
all,
why
are
we
here
talking
about
steel
toe?
Why
does
it
exist?
It
was
created
quite
a
few
years
ago
in
2015
by
a
theme
actually
within
pivotal,
and
it
was
donated
to
the.net
foundation
couple
years
later
in
2017,
it's
a
fully
open
source
project
and
the
idea
is
to
enable.net
developers
to
build
best
practice
microservices
right.
This
is
we're
specifically
talking
about
microservices
within.net.
B
Why
do
you
care
about
steel
toe
because
it
makes
programming.net
quicker
easier,
safer,
better,
you
know
all
the
keywords
there
right.
The
key
is,
though,
as
you're
gonna
see
in
some
of
the
demos,
steel
toe
is
going
to
abstract
away
all
the
boilerplate
stuff
right
we're
going
to
the
cloud.
We
know
how
this
should
run.
We
know
what
it
should
look
like.
Why
should
I
spend
time
doing
that
stuff?
Get
me
into
my
business
logic
and
into
the
real
stuff
as
quickly
as
possible.
B
This
is
a
common
question
that
we
see.
We
we
all
generalize
and
say.net
right,
but
we
have
to
be
specific
here
and
in
fact,
when
we
talk
about
microservices,
we're
talking
about
asp.net
right
and
in
that
framework.
So
it's
a
common
question
that
we
see,
can
I
just
use
net
everywhere,
sorry
seal
toe
everywhere,
and
if
you're
gonna
bring
a
console
app
into
a
container
and
do
some
some
things
there,
then
you
know
we're
talking,
but
for
the
most
part
this
is
a
web
api
project.
B
That's
going
to
benefit
from
all
the
steel
toe
goodness
so
just
kind
of
driving
that
idea
home.
Because
again
we
hear
this
a
lot.
We
are
not
trying
to
replace
net
at
all
one
bit
dot
net
core
and
net
framework
have
so
much
goodness
in
them.
Steel
toe
was
originally
made
for
net
framework
apps
and
we
continued
that
on,
but
it
also
adapted
when
dot
net
core
came
out,
because
obviously
that
made
microservices
really
really
easy
and
so
eye
configuration.
B
C
You
know,
if
I
can
add
to
that.
You
know
one
of
the
things
that
sealta,
as
a
team
tries
to
provide,
is
good
abstractions
to
abstract
ourselves
from
other
non-business
logic
concerns,
whether
it's
the
cloud
you're
running
on
or
whether
it
is
an
interface
you're
programming
to
now
that
microsoft
provides
a
lot
of
these.
C
A
good
example
of
this
would
be
like
an
eye
logger
right,
so
that
is
the
standard
for
logging,
but
yet
there
are
teams
like
ceralog
that
provide
a
lot
of
value
on
top
of
it,
and
you
can
also
think
of
microsoft,
health
checks
and
you
can
think
of
zebral's
open
source
contribution
to
health
checks
there
and
how
they
play
together.
Now
stilta
comes
along
and
makes
it
even
more
easy
to
use
those
with
other
spring
cloud
type
infrastructure,
for
example,
spring
boot
admin
or
cloud
foundry.
C
Later
microsoft
came
back
and
made
event
search
available
across
all
all
over
the
both
framework
and
core
and
in
linux
and
everywhere,
and
as
soon
as
they
did
that
we
quickly
adopted
and
used
that
and
now
all
those
events
are
available
for
you
in
your
metrics
endpoint,
that
that's
an
example
how
we
work
together
with
microsoft,
definitely
not
replacing
it
but
making
it
better
for
an
open
source
direction
that
microsoft
is
going
with
all
right.
I
guess
that
brings
me
to
my
demo
and
before
we
get
started
off
with
the
demo.
C
C
This
doesn't
work
for
work
for
us,
because
there
is
drawbacks
from
adding
micro
moving
to
a
microservices
platform
and
some
of
those
drawbacks
are
it's
hard
to
find
what
the
problem
is
with
your
microservices,
when
you
have
so
many
instances
of
your
business
logic,
spread
all
over
the
place.
Now,
when
there
is
a
problem,
how
do
you
find
where
the
problem
is?
Another
example
is
okay,
there's
a
problem
with
one
part
of
my
application
or
one
microservice,
and
all
the
upstream
microservices
or
downstream
microservices
are
going
down
because
of
that.
C
How
do
you
isolate
from
that?
That
speaks
to
resilience
right,
so
we're
going
to
take
a
quick
look
at
a
demo
to
show
you
how
easy
it
is
to
add
steel,
toe
and
add,
get
these
benefits
for
free
without
a
lot
of
fuss
and
and
not
just
waste
a
lot
of
time
and
not
get
it
all
mingled
up
with
your
business
logic,
your
business
logic
stays
in
its
lane
and
the
microservice
concerns
are
addressed
separately
and
cleanly
and
we'll
take
a
quick
look
at
that
all
right,
so
we're
in
visual
studio
2019
is
community
edition.
C
I'm
going
to
create
a
new
project,
I'm
going
to
create
asp.net
core.
We
want
a
web
api
application
like
the
basics,
template
that
comes
with
microsoft
and
we're
going
to
start
from
there,
and
so
I
picked
asp.net
core
web
application
next
and
local
web
application
3.
That
sounds
good
to
me
and
here
we'll
get
a
choice
of
what
type
of
asp.net
core
and
we
here
we
want
to
say
you
can
pick
empty,
we're
going
to
say
an
api
application
and
it
will
create
it
and
it's
basically
a
simple
weather
app.
C
It
has
a
controller
that
spits
out
a
sample
weather
data
right,
so
there
you
are,
and
so
nothing
exciting.
Here
you
got
your
regular
program,
dot
cs
with
your
I
host
builder.
You
have
your
startup,
where
you're
setting
up
your
dependency
injection
container,
adding
services
to
it
and
then
you're,
adding
any
middleware
that
you
might
want.
You
have
the
new
endpoint
routing
available,
nothing
fancy
here
and
we
can
take
a
quick
look
at
the
weather,
forecast,
sorry,
the
controller
and
again,
a
really
simple
controller.
And
if
you
run
this.
C
And
so
let's
pretend
for
a
second
that
this
weather
app
is
your
business
logic
and
it's
doing
its
thing,
but
you're
in
a
microservice
environment.
And
now
you
want
to
know
there's
20
instances
of
this.
Let's
say
you
want
to
know
how
it's
doing
and
that's
a
problem
that
a
little
steel
toe
component
called
endpoints
that
we
provided
it
kind
of
mirrors.
The
spring
boot
actuators
is
how
they
work
and
they
work
with
other
things
that
that
use
them,
such
as
cloud
foundry
or
spring
boot,
at
an
open
source
project,
for
example.
C
B
C
C
C
A
C
Yeah
absolutely
so.
Today's
avro
provides
a
whole
bunch
of
asp.net
health
checks
for
all
your
databases
and
many
things,
there's
dozens
of
health
chips
that
they
provide
and
they
all
build
on
the
microsoft
eye.
Health
check
abstraction
right.
So
we
have
our
own
eye
health
contributor,
abstraction
that
we
also
there
are
teams
that
are
already
using
our
abstraction.
C
So
we
combine
these
two
because
now
there's
so
much
that's
the
beauty
of
open
source
that
anybody
can
come
in
and
provide
value
in
this
ecosystem
before
we'd
have
to
wait
for
microsoft,
to
do
something
like
that
and
then
being
one
company
they're,
focusing
on
the
most
important
thing
to
do
for
everybody,
whereas
open
source
projects
can
come
in
and
provide
all
kinds
of
value
for
developers,
and
it's
just
free
for
the
taking
right.
So
it's
I
think,
a
great
time
to
be
alive
as
a
developer
and
take
advantage
of
all
these
things.
For.
A
C
It
obviously
doesn't
know
about
this
right
so
because
those
health
contributors
weren't
built
for
that,
so
the
other
thing
about
is
the
health
endpoint
has
its
own
way
of
representing
and
serializing
the
health
data.
There
are
two
links,
that's
already,
for
example,
cloud
foundries
like
a
quick
example,
I
can
think
of
or
spring
boot.
Admin
is
a
quick
example.
C
They
work
with
the
spring
format
right,
so
this
makes
it
available
in
that
same
format,
and
not
only
does
it
make
it
available,
it
makes
all
of
the
asp.net
cores
available
or
anybody
else,
building
an
eye
health
check,
microsoft,
eye
health
check,
abstraction,
makes
it
available
in
in
this
format,
so
it
all
depends
on.
What
you
need
is
what
your
tooling
is
and
what
you're
doing
with
it,
and
it's
completely
flexible
and
xero.
C
Even
has
a
nice
ui
that
you
can
plug
into
this,
that
you
can
get
a
different
kind
of
dashboard
yeah,
so
it's
they're
all
about
choices
for
developers
and
whatever
floats
your
boat.
You
know
more
options
are
better,
and
yet
we
provide
a
simplified
and
opinionated
way
to
do
things
that
we
hope
that
you'll
find
useful
and
helpful
and
make
you
more
productive.
C
So
another
thing:
that's
got
quite
a
bit
of
a
problem
in
microservices
is
you
know,
tracing,
and
you
know
correlating
your
logs
to
your
traces,
so
there's
all
kinds
of
tooling
that's
available
to
trace
your
application
with
zipkin,
for
example,
and
then
you
have
your
traces.
How
do
you
correlate
them?
So
we
can
we're
going
to
take
a
look
at
how
we
can
make
that
happen
and
again
there
are
two
simple
components:
we're
going
to
add.
C
One
is
called
dynamic
logging
and
you
know
the
some
of
these
things,
I'm
just
showing
like
a
really
the
tip
of
the
iceberg
of
functionality
here
right.
So,
if
we're
looking
for
dynamic
logging,
it
can
do
a
lot
more
things
where
you
can
at
run
time,
scale
up
and
scale
down
your
log
levels
right,
that's
a
useful
thing
to
have.
When
you're
in
the
cloud
you
don't
have
to
redeploy
stuff.
You
just
update
the
config
via
an
api
call
and
it
will
automatically
sca
increase
the
verbosity.
C
If
there's
a
certain
component,
that's
making
giving
you
a
problem,
or
even
you
could
say,
even
a
certain
namespace
inside
your
application.
That's
giving
you
a
problem!
What
you
can
say
is,
let's
say
my
company
dot
component,
one
dot
feature
two
turn
up
the
logging
for
that,
and
you
can
do
that
at
one
time.
So
that's
a
great
feature,
I'm
not
showing
that
right
now,
but
what
I
do
want
to
show
is
the
distributing
trace.
Sorry
distributed
tracing
like
I
mentioned.
C
And
that's
that's
about
it!
Well,
that's
about
all.
You
have
to
do
to
add
the
dynamic
console
and
all
it'll
do
right
now
is
just
give
you
an
error
message:
let's
go
ahead
and
go
to
the
controller
and
say
use
your
regular
logging
abstraction.
We
didn't
change
any
of
the
abstractions
right.
We're
using
what's
been
built
into
the
framework
and
say
from
the.
C
C
And
none
yeah,
and
so
what
we're
showing
right
now
is
basically
log
correlation
right.
Now,
we're
not
gonna,
there's
a
lot
more
functionality
to
these
components
that
we're
not
getting
to
for
a
sake
of
time
right
now.
But
all
we
do
is
add
this
to
our
service
container
and
there
you
go
intellisense
to
the
rescue,
tells
you
what
to
do
right
and
and
that's
pretty
much
it
yeah,
and
so
let's
go
ahead
and
run
this
application
again
and
this
time
we're
gonna
look
for
some
log
messages
in
the
output
right.
B
C
Yeah
so
yeah,
so
this
correlating
logs
and
your
context.
You
know
you
see
that
you're
tracing
your
application
and
this
particular
component
is
taking
a
long
time
and
you
want
to
know
what
the
context
in
which
it
executed
was,
and
you
want
to
see
the
actual
headers
to
be
able
to
see
where
the
problem
actually
happened.
C
And
so
now
you
see
this
hi
from
constructor,
and
so
you
see
these
tracing
headers
that
will
allow
you
to
search
if
you're
dumping,
your
logs
into
a
different
system
and
your
traces
in
different
system,
and
you
see
slowness
or
whatever
you
can
go
and
look
at
your
logs
and
examine
them
together
or
if
you
get
an
error.
This
is
super
useful
again.
What
we
want
to
show
here
is
how
easy
it
is
to
add
a
little
bit
of
steel
to
a
goodness
without
messing
with
any
of
your.
A
I
that
was
a
really
great
demo
and
again,
like
I
love
how
easy
it
is
for
us
to
just
add
methods
and
add
nuget
packages
without
interrupting
our
code
so
much,
but
until
it
adds
so
much
rich
functionality
on
top
of
what
we're
already
doing
in
terms
of
our
business
logic
and
our
micro
services
that
we're
trying
to
create.
So
why
don't
we
talk
a
little
bit
about
what
else
can
we
do
with
steel
toe
and
like
what
are
some
of
the
other
benefits
that
we
get
from
adopting
this
framework.
C
Absolutely
so
here's
a
few
more
examples
and
places
where
steeltalk
can
really
help
you
now
the
first.
Obviously
we
are
moving
to
a
microservice
framework
in
in
today
they
are
the
new
normal
right.
So
if
you're
an
enterprise
application-
and
you
have
a
lot
of
teams,
it
is
really
important
not
to
block
one
another.
With
a
monolith
and
20
teams
inside
one
code
code
base
trying
to
figure
out
who
goes
first
and
go
to
production
quickly,
so
you
need
to
be
able
to
iterate
independently,
and
so
this
is
a
given.
C
C
So
it
helps
you
deliver
value
pretty
much
and
then
another
advantage
of
using
stealto
is
you
need
resilience
patterns
and
resilience
patterns
are
hard
to
create,
but
on
your
own,
and
so
there
are
many
that
are
available
and
there
are
many
practices,
so
stilto
encodes
some
of
those
practices
and
makes
it
very
easy
to
get
set
up
with
minimum
fast.
So
you
have
things
like
load,
balancing
circuit,
breaking
we've
seen
a
little
bit
of
distributed,
tracing
and
monitoring
and
and
so
much
more.
The
second
thing
is:
where
are
you
deploying
to?
C
You
may
be
deploying
to
a
specific
cloud
to
multi
multiple
clouds,
no
matter
where
you're
going
or
you
could
even
be
on
premise
in
an
air
gap
environment
because
of
security
or
whatever
concern
and
stealth
can
help
you
there
with
the
components
and
the
open
source,
stealing
tooling,
that
that
comes
from
our
teams
around
you
know,
service
discovery
or
any
of
the
microservice
concerns
that
you
face
normally
in
the
cloud
right,
so
it
still
does
not
tie
you
to
any
specific
cloud.
Even
though
vmware
is
our
sponsor,
we
don't
just
go
to
vmware.
C
We
can
go
to
azure
with
it.
You
can
go
to
gcp
with
it.
Wherever.Net
can
run,
sealta
can
help
you
there
all
right
and
finally,
if
you're
building
web
apps
right,
that's
a
big
use
case
for
enterprises
to
create
web
applications
and
there's
still
a
lot
of
concerns
that
steeltoe
can
help
you
with
one
is
everybody
needs
application
configuration?
How
do
you
manage
configuration
silta
makes
it
really
easy
to
consume
configuration?
C
You
know
whether
or
not
you're
in
the
cloud,
especially
if
you're
in
the
cloud
that
becomes
a
big
problem
that
still
doesn't
solve
a
second
thing
is
data
access.
You
know
everybody
needs
to
talk
to
a
database
and
whether
you're
using
a
relational
non-relational
database
or
cloud-based
data
service.
It
is
probably
a
steel
toe
connector
that
can
help
you
bridge
that
gap
and
make
it
very
easy
to
develop.
C
And,
finally,
you
know
talking
about
microservices.
Only
recently
people
have
started
talking
about
driven
architectures
for
microservices
oftentimes.
You
have
this
chain
of
dependencies
of
microservices
and
they're,
not
the
most
optimal
way
to
represent
your
business
logic,
because
in
reality,
business
represents
an
even
it's
better,
represented
by
an
event,
architecture,
event,
driven
architecture,
there's
new
stuff
coming
just
new,
with
3.3.0
release
coming
up
with
still
to
stream,
and
now
some
of
you
may
be
familiar
with
the
spring
cloud
stream
project
and
it
builds
on
the
abstractions
of
spring
messaging
and
spring
integration.
C
C
Abstractions,
it
becomes
so
much
easier
for
your
teams
to
all
come
in
together,
whether
you're,
using.net
or
java.
So
will
be
a
great
addition
for
the
stilto
library
and
there
are
more
new
editions
coming
up
and
one
definitely
that
we're
looking
forward
to
is
azurespringcloudfor.net
and
what
it
is
is
a
managed
service
that
provides
you
spring
cloud
discovery
spring
cloud,
config
server
and
application
monitoring
built-in
it's
built
for
spring
applications,
and
now
it's
also
available
for
it's
been
there
for
spring
java
applications
for
a
while.
B
The
java
version
of
azure
spring
cloud
is
going
to
be
coming
out
of
public
preview
to
bga
later
this
year,
2020
and
then
we're
going
to
do
a
fast
follow
it's
already
in
development.
It's
basically
already
a
thing
privately.
The
net
version
of
azure
spring
cloud
is
gonna.
Follow
that
later
this
year,
2020,
maybe
early
21,
2021
somewhere.
C
Around
cool,
thank
you
for
that.
I
I
for
some
reason
assumed
you've
solved
yeah
but
cool.
Thank
you
yeah,
and
so
that's
pretty
much
our
presentation
on
what
stilto
can
do
for
you.
Definitely
if
you're
a.net,
developer
and
you're
building
microservices,
it's
definitely
worth
taking
a
look
at
you
know:
there's
lots
of
open
source
libraries
and
projects
going
on
and
steeltouch
helps.
You
use
many
of
them,
so
you
should
definitely
take
a
look
at
it.
You
can
learn
more
about
it
at
stilto.io.
C
You
know,
there's
a
getting
started,
guides,
documentation
and
internal
if
just
a
new
developer
and
you're
trying
to
get
started
with
net.
I
think
this
is
a
great
place.
In
addition
to
all
the
other
places
you
go
to
learn,
stuff,
come
and
learn
how
developers
do
things,
because
we're
definitely
informed
by
a
polygon
world
view
right
so
coming
from
a
little
bit
from
the
java
side,
a
little
bit
from
the
dartmouth
side,
I
think
we
make
the
world
a
better
place,
looking
at
it.
That
way
and
there's
obviously
training
that's
available.
C
If
your
team
is
interested
that
we
can
pursue
and
if
you
have
support
questions,
so
we
have
an
open
slack,
anybody
can
join
slack.steel.io,
slack
or
stack.
Overflow
is
another
place.
You
can
ask
questions,
I
submit
a
pr
if
you
have
a
great
idea
or
open
an
issue.
If
you
have
an
idea
that
you
think
we
should
do
so
yeah.
So
that's
pretty
much.
My
conclusion
here.
Thank
you
so
much
for
having
and
do
you
have
any
questions
for
me.
A
A
So
we
just
saw
a
lot
of
really
good
demos
about
steel
toe
and
how
we
could
build
micro
services
with
net
applications.
I
definitely
recommend
all
of
you
go
and
check
it
out
like
we
mentioned
before.
Thank
you
both
gentlemen
from
the
team
coming
on
and
talking
to
us
about
it.
I
definitely
want
to
do
some
more.
I
definitely
want
to
keep
this
conversation
going
because
I
feel
like
there's
so
much
functionality.
That's
available
that
we
haven't
even
really
touched
the
surface
of
what's
possible,
so.
A
Right
so
we're
going
gonna
make
sure
that
we
have.
You
know
some
of
you
folks
back
on
or
some
of
your
other
teammates
come
on
and
definitely
let's
keep
the
conversation
going
and
learn
like
how
rich
this
framework
is
and
how
much
we
could
actually
do
with
dotnet
and
building
micro
service
type
applications.