►
Description
This session is run by the Philippine .NET Users Group (https://meetup.com/phinug) that hosts meetups in Manila, Philippines.
Meetup link: https://www.meetup.com/phinug/events/277831123/
For our next session we'll talk about:
Serverless .NET Development with Azure Durable Functions
Learn how to get started with .NET development the serverless way using Microsoft Azure Durable Functions. In this tech session, Jonah will present the fundamentals of serverless computing, comparison between monolith, microservices and FaaS, an overview of Azure Durable Functions, the known patterns it solves and durable functions best practices to consider. A short demo will also be presented.
============
About our speaker:
Jonah Andersson
Jonah Andersson is a Filipina-Swedish Software Developer at Forefront Consulting, Sweden.
She studied Computer Science in the Philippines and System Development in .NET and Java in Sweden, which makes her passionate about tech. Jonah likes solving challenging complex problems, programming back-end and has great interest in developing applications in .NET with new cloud technologies like Microsoft Azure. She likes continuous learning, connect with other developers, share her technical knowledge at her workplace and by public speaking. Jonah wants to make difference by advocating gender equality, diversity and inclusion in tech.
More of her content can be found at:
• Website: https://jonahandersson.tech/
• Azure User Group Sundsvall – Sweden: https://www.meetup.com/azureusergroupsundsvallsverige/
Follow her in the following social channels:
• LinkedIn: https://www.linkedin.com/in/jonahandersson/
• Twitter: https://twitter.com/cjkodare
• Facebook: https://www.facebook.com/jonahanderssontech
• Instagram: https://www.instagram.com/jonahandersson_ladyprogrammer/
A
My
name
is
john,
I'm
a
principal
developer
at
a
company
called
page
up
and
I'm
also
the
lead
for
the
philippine.net
users
group
and
in
tonight's,
in
tonight's
session
we
are
going
to
have
a
filipina
developer
with
us
working
working
overseas
and
she's,
going
to
talk
about
to
us
about
about
azer
and
and
a
really
interesting
topic
about
about
windows
azer.
But
but
before
we
proceed
to
that
talk,
I
would
just
like
to
share
a
bit
of
a
word
from
our
sponsor.
A
So
so
I
would
like
to
thank
the.net
foundation
for
for
hosting
this
live
stream
and
and
and
and
and
having
us,
you
know,
you
know
letting
us
use
their
use,
their
streaming
capabilities
and
and
and
and
everything
and
and
and
hosting
our
show.
Now,
there's
a
lot
more
user
groups
that
you
can
see
and
and
their
events
in
the
in
in
the
dot
net
foundation.
A
You
know
virtual
user
group,
so
please
join
them
and
meet
up
and
you
would
you
would
see
not
just
the
philippine.net
user
groups,
events
but
all
the
events
around
around
the
world.
You
know
so
so,
aside
from
the
philippines,
so
in
gym
and
time,
if
it's
a
us,
there's
a
lot
of
a
lot
of
investor
us
and
you
can
join
those
as
well.
If,
if,
if
the
topics
are
interesting
to
you
and
if
it's
convenient
to
your
time,
you
know
and
yeah,
so
that's
that's
basically
it
so.
So.
B
C
C
A
B
B
B
I
really
like
coding
and
working
with
azure,
I'm
a
full
stock
developer
for
coding,
mainly
c
sharp
and
that
net
and
I'm
also
recently
certified
as
an
azure
developer,
and
I
also
have
a
user
group
called
microsoft,
azure
user
group
sunswell
that
I
wanted
to
to
develop
and
improve
for
community
sharing,
and
that's
enough
about
me
so
we
will
be.
I
will
be
starting
my
talk
by
sharing
about
this
picture,
so
there
was
a
few
years
ago.
I
went
back
home
to
the
philippines
and
I
was
in
stockholm's
airport.
B
Orlando
is
the
name
of
it
and
then,
when
I
was
at
the
airport
about
about
the
check-in,
I
saw
this
a
line
of
queue,
lots
of
people
and
there
was
well
waiting
on
the
night.
I
wish
that
I
could
could
buy
or
grab
a
cup
of
coffee,
but
I
couldn't,
but
I
had
that
dilemma,
and
I
wish
that
I
could
do
multiple
things
at
the
same
time.
Unfortunately,
that
time
there
weren't
any
self-service
clothes.
B
So
it
was
something
that
I
had
to
stay
there
and
I
wish
there
was
a
solution
for
such
problem
without
waiting.
So
why
the
the
purpose
of
introducing
that
that
airport
cue
photo
is
that
azure,
durable
functions
is
meant
to
solve
complex
works
flow
problems
in
serverless
architecture,
which
means
that
you
can
run
parallel,
workflows
in
serverless
environment,
and
I
will
be
sharing
more
details
about
that.
So
as
an
overview,
I
will
be
just
giving
a
bit
of
introduction
of
what
cloud
and
serverless
computing
is
a
bit
about.
B
Azure
functions,
the
extension
of
our
azure
functions,
which
is
the
durable
functions,
the
common
patterns
as
well
as
a
live
demo.
I
will
be
showing
an
example
or
a
project
mini
project
that
I
created
this
week.
It
is
a
a
project
where
a
blob
triggered
azure
functions,
project
that
sends
notification
using
twilio
api
and
some
suggested
learning
resources
and,
to
start
with
we,
I
would
like
to
go
through
about
cloud
computing.
B
So
serverless
is
a
a
trend
in
a
technology.
That's
really
a
trend.
These
days.
A
lot
of
us
want
to
learn
more
about
it,
and
mainly
developers
want
to
find
out
what
it
is,
and
sometimes
we
question:
is
it
really
the
right
technology
or
solution
that
solves
their
problems?
So
serverless
is
it's
an
execution
model
where
cloud
providers
like
microsoft,
azure
and
there's
also
other
aws
and
google.
B
You
can
create
it
instantly
and
it's
event
driven
and
to
prop.
Actually
it's
not
really
serverless,
because
there
are,
there
are
actually
infrastructures
or
service
services
or
servers
behind
it.
Only
that
cloud
provider,
for
example,
microsoft,
azure,
take
cares
of
that
for
us
to
make
our
work
easier.
B
So
I
would
like
to
compare
a
sweet
comparison
about
the
different
technologies
that
we
have
serverless
against
others.
For
example,
the
monolith
monolith
is
like
a
pizza
is
a
big
piece
of
cake
with
we
have
the
different
layers
of
our
system,
architectures
and
in
our
logic
and
our
presentation
layer.
B
So
why
do
we
need
to
build
serverless
if
we
could
just
build
a
normal
web
apps
or
normal
apps?
So
it's
because,
as
mentioned,
it
increases
our
developer
productivity.
We
developers
want
to
really
like
solving
problems,
and
business
also
requires
us
to
deliver
and
be
productive,
so
you
would
serve
unless
we
can
comply
to
this.
B
For
example,
you
can
connect
your
serverless
application
with
iot
or
even
with
cognitive
services-
that's
already
in
the
cloud
today,
so
you
can
integrate
them
with
that,
and
there's
also
ability
to
solve
complex
problems.
Just
like
my
example
at
the
beginning,
the
the
key
problem-
and
that
happens
also
in
our
programming
world-
that
sometimes
we
we
want
to
do.
B
So
this
is
a
good
example
that
serverless
solves
for
us
and
also
seamless
connectivity,
which
means
that
you
have
the
ability
to
modernize
your
app
by
connecting
to
other
azure
services
that
are
also
great
and
also
external
azure
service
external
services
in
on
the
internet.
So
to
to
understand
what
durable
functions
is.
Are
you
need
to?
We
need
to
first
know
what
azure
what
azure
functions
are
for.
Azure
functions
is
the
main
domain.
B
So
it's
azure
functions
support
several
languages.
The
main
ones
are
the
as
of
date,
it
says
c-sharp,
f-sharp,
javascript
and
also
java,
and
this
is
how
usher
functions
are
composed
of
so
it's
code
driven
and
it's
events
and
data.
So
you
this
is
very
it's
a
lot
of
work
in
the
back
end.
So
and
then
you
connect
your
assert
functions
with
your
events
from
your
front
end
and
the
data
that
you
want
to
send
and
to
show
in
your
applications.
B
So
this
is
an
example
of
an
http
trigger
in
an
azure
functions
where
you
have
http
requests,
http
trigger
it
can
be
get
or
post
and
you
send
a
request
and
add
a
name,
and
then
it
returns
back
as
a
json
object
and
pricing
models.
So
we're
talking
about
consumption.
We
talked
about
consumption
model
and
it's
because
it's
important
to
know
price
the
main
pricing
models,
because
there
are
actually
the
pay-per-use
model.
B
That's
the
consumption
plan,
which
means
that
we
only
pay
for
the
time
that
the
code
runs
when
your
serverless
code
runs
and
there's
also
the
app
service
plan.
This
is
an
this
is
special,
it's
like
having
the
web
app,
but
you
can
also
use
app
service
plan
in
usher
functions
to
only
to
to
pay
a
monthly
pe.
For
example,
if
you
you
are
in
a
business
or
your
company
wants
to
track
and
wants
this
monthly
budget
that
we
want
to
spend
a
certain
amount
for
serverless
serverless
development.
B
B
So
why
why
why
what's
wrong
with
azure
functions?
And
why
do
we
need
to
have
durable
functions?
Usher
functions,
they're
good,
but
they
are
actually
stateless,
which
means
that
when
the
vm,
when
the
vm,
where
azure
functions
are
saved
from
are,
are
restarted,
then
your
azure
functions
will
lose
its
state
its
state.
So
if
you
want
to
run
long-running
workflows,
then
it
is
ideal
to
use
azure
durable
functions
because
it
solves
stateful,
long-running
workflows
and
azure.
Durable
functions
is
not
a
competition
or
it's
not
a
separate
service
from
azure
functions.
B
It
is
the
extension
which
is
which
means
that
it's
like
the
advance
it
has
the
advanced
features
that
a
normal
azure
functions
kind
of
do.
So,
if
you
want
to
solve
complex
stateful
function,
problems
or
solutions,
then
you
can
check
out
durable
functions
because
it's
a
powerful
technology
and
durable
functions
supports
a
few
languages
already.
It's
c
sharp,
javascript
python,
f,
sharp,
f,
sharp
and
powershell.
B
So
when
do
we
need
to
use
durable
functions,
so
you
can
use
azure
functions,
it's
also
powerful,
but
when
do
we
need
to
consider
using
durable
functions?
So
if
you
want
to
create
long
running
workflows
that
are
stateful
that
doesn't
lose
its
state
and
that's
when
you
also
want
to
work
with
recurrence
interval,
you
want
to
manage
the
life
cycle
of
your
tasks,
which
means
you
want
to
control,
how
you
want
your
workflow
be
like
or
how
you
your
tasks
will
be
performed
or
will
be
executed.
B
So
the
technology
behind
durable
functions
is
the
durable
task
framework.
It's
an
open
source
lightweight
framework,
that's
actually
open
in
public
on
github,
so
you
can
check
on
the
link
there.
That's
where
you
can
check
and
even
contribute
to
this
framework,
and
currently
it's
it's
improving
and
developing,
and
it's
getting
popular.
Many
are
interested
in
learning
more
about
this
technology,
and
this
is
the
this
is
a
big
picture
of
the
different
azure
function
types.
We
have
the
client
function
that
serves
as
a
starter
functions.
B
This
is
like
a
normal
azure
functions,
but
what's
special
about
the
client
function
is
that
it
can
only
be
triggered
by.
It
can
be
only
triggered
to
start
the
orchestrator
or
the
orchestration
and
it
kick-starts
the
orchestration
and
when
the
orchestrator
kick
is
kick-started,
then
all
the
activities
are
run
and
the
orchestrator
function
describes
how
the
actions
or
the
workflow
will
be
executed.
It's
like
the
blueprint
or
the
plan,
the
the
project
plan,
how
it
how
functions
should
be
executed
and
the
activity
functions.
B
That's
where
you
perform
your
test,
just
like
a
normal
functions
test
that
you
do,
but
the
main
heart
of
durable
functions
is
the
orchestrator,
so
there's
also
a
different
type
of
fourth
type,
which
is
called
entity,
functions
and
entity.
Functions
works
with
durable
entities
and
they're
specially
used
for
that
to
to
define
operations
for
such
entities,
and
if
you
want
to
work
with
entity
functions,
it's
only
available
in
version
2.0
and
above
and
you
would
need
to
use
entity
trigger
and
as
of
this
date,
it
only
support
net
and
javascript.
B
B
Why
do
why
do
we
need
to
create
or
code
the
orchestrator
function
in
a
deterministic
way?
It
is
because
the
whole
function
orchestrator
function,
it's
a
workflow,
it
will
be
replayed,
so
you
need
to
be
consistent
and
determined
on
the
task
that
you
want
to
to.
You
want
to
happen
in
your
workflow
and
there
are
more
information
about
a
deterministic
api
like
the
orchestrator
in
durable
function
through
this
link.
So
you
can
check
it
out
and
read
more
about
that,
and
here
is
also
another
example
of
deterministic
versus
non-deterministic.
B
So
this
is
like
the
the
orchestrator
like
durable
functions,
and
this
is
like
a
different
separated,
normal
azure
function,
so
they
don't
have
a
flow.
They
can
run
anytime,
they
can
lose
its
state,
but
this
is
the
advantage
on
the
left
side,
the
advantage
of
deterministic.
You
have
the
workflow
that
controls
every
task.
B
So
what
we
should
do
instead
is.
If
we
need
to
have
random
numbers,
then
we
can
retrieve
the
data
or
work
on
the
data
in
our
activity
functions
and
then
the
next
one
do
not
access
data
source.
It
stores
like
databases
or
configuration
in
your
orchestrator,
then
what
you
can
do
instead
is
you
can
pass
configurations
into
activity
functions
and
the
next
one
is
that
do
not
use
thread
functions
like
a
thread
like
sleep
run
or
delay
within
your
orchestration.
B
What
you
can
do
is
you
can
make
use
of
the
context,
the
durable
orchestration
context,
which
has
everything
in
it.
If
you
want
to
use
such
concurrency
methods
and
also
do
not
create
infinite
loops,
so
since
the
orchestrator
will
be
replayed,
so
if
you're
gonna
create
an
infinite
for
loop
or
for
each
loop
within
the
orchestrator,
then
it
will
be,
it
will
be
a
problem.
It
will
cause
some
some
technical
errors.
Maybe-
and
of
course,
if
you
have
a
consumption
plan,
it
might
create
infinite
bills
in
your
azure
subscription
as
well.
B
So
we
need
to
be
careful
not
to
create
infinite
loops
in
our
in
our
orchestrator.
So
what
we
can
you
do
instead?
So
if
we
really
need
to
repeat
a
process
within
within
the
orchestration,
we
can
use
the
method
called
create
as
new.
So
this
is.
This
is
a
method
that
you
can
access
via
the
durable
orchestration
context,
and
also
one
example.
Is
we
don't
we
don't
it's
not
recommended
to
use
current
date
time
because
date
time
they
change
every
milliseconds
and
it's
not
determined,
so
we
can
use
a
special
function.
B
B
So
so
I
will
be
going
through
an
overview
about
the
durable
function
patterns
because
they
are
examples
and
how
or
what
kind
of
workflow
problems
that
durable
functions
can
solve.
So
there
are
known
sec,
the
six
functions
pattern,
it's
the
function,
chaining
defining
out
and
fanning
in
the
async
http
http
apis,
and
we
also
have
the
monitoring
human
interaction
and
external
events
correlation
or
the
aggregation
pattern,
and
to
dig
deeper
into
the
first
example
of
the
first
pattern.
We
have
the
function
chaining
so
in
this
function.
B
Chaining
is
that
you
execute
the
function
in
specific
order
and
then
the
first
function.
The
the
second
function
takes
the
input
from
the
first
function,
for
example
in
this
code
code
snippet
here.
So
we
have
like
a
function
one
it
doesn't
receive
any
parameter
or
data,
but
in
function
two
f2
it
receives
the
the
it
has
variable
x
as
an
input
so
on
and
so
forth.
B
So
it's
executed
in
a
sequence,
sequential
sequential
order,
and
I
will
be
showing
an
example
of
function
chaining
in
my
demo
today,
and
this
is
how
it
works.
Actually,
so
we
have
the
orchestration
behind
the
scene.
This
is
how
it
works
in
the
background.
So
when
the
orchestrator
is
started,
the
activity
one
is
scheduled
and
then,
when
the
activity
one
is
scheduled,
the
orchestration
sleeps.
So
when
the
orchestration
sleep,
that
means
that
you're
not
charged
for
the
other
functions
or
activity
functions
that
are
not
running.
B
So
that's
the
good
thing
about
orchestrate
or
or
deterministic
orchestration,
because
you
don't
have
to
worry
of
being
charged
of
activity,
functions
that
are
that
don't
need
to
be
run
and
when
it
sleeps.
What
it
does
is
that
it
waits
for
the
next
that
first
activity
to
be
done,
and
then
it
wakes
up
again
and
when
it
wakes
up
it
schedules.
The
second
activity
gets
its
input,
it
sleeps
again
and
then
it's
done
and
then
the
orchestration
is
completed.
So
this
is
like
it's
very
organized
and
synchronized
in
sequence.
B
The
function
chaining
example.
So
there
are
different
patterns
and
examples
with
this.
But
this
is
a
good
one
and
there's
a
second
pattern
and
it's
called
fannin
and
fan
out,
which
means
that
you,
you
execute
multiple
functions
at
the
same
time
and
then
you
do
it
in
parallel.
And
then
you
aggregate
you
wait
and
aggregate
the
result
as
one
output
and
then
process
it
further.
B
B
B
If
my
website
is
running
or
not,
if
it's,
if
it's
running
and
it's
not
getting
the
the
500
or
the
error
codes
for
http,
then
I
will
be
logging
or
printing
out
the
content
of
my
website
and
then
I
can
process
it
further
and
it's
running
asynchronously
and
then
next
is
the
monitor
pattern
in
monitor
pattern.
It
is
actually
the
opposite
of
http
api.
B
The
monitor
patterns
refers
to
a
recurring
process
in
a
workflow.
It's
like
running
monetary
job.
For
this
example,
it's
doing
its
job
and
then
when
it
uses
a
timer.
So
when
a
certain
time
or
when
that
timer
happens,
then
it
does
other
tests
to
perform
and
the
next
is
human
interaction.
This
is
a
human
interaction.
Pattern
requires
either
a
human
to
approve
the
action
before
it
goes
to
the
next
test,
or
it
can
be
a
robot
or
comp
programmed
program.
Timer
that
responds
to
to
some
actions.
B
For
example,
in
this
case
there
is,
there
is
adversary,
approval
requests
and
that
person
needs
to
approve.
If
that
person
doesn't
approve,
there
will
be
a
timer,
a
timeout,
a
durable
timeout,
and
it
sends
the
approval
to
another
functions
like
the
escalate
function.
To
do
something
else,
maybe
forward
the
event
to
another
person,
maybe
a
supervisor
if
the
manager
is
on
vacation,
for
example.
B
And
then,
when
we
work
with
http
or
with
durable
functions,
there
are
several
http
statuses
that
we
can
expect.
For
example,
the
200,
which
means
it
is
okay.
It's
completed,
there's
also
accepted
that
the
instance
is
in
progress,
400,
very
common,
bad
requests
for
for
the
fact
it
didn't
find
the
file,
for
example,
and
500
the
common
one
is
that
server
error,
and
this
is
an
example
of
the
data
that
you
use.
B
For
example,
if
you
gonna,
you
have
an
http
trigger
in
your
orchestrator,
you
can
use
postman
to
get
the
data
of
your
orchestration.
So
here
you
can
see
the
id
the
orchestration
id
the
orchestration
instance
and
the
event
url,
and
you
also
have
the
terminate
post
url.
You
can
use
this
if
you
want
to
terminate
or
the
program
to
program,
to
terminate
your
orchestration
or
you
can
also
restart
and
also
purge
the
history
of
your
orchestration.
B
B
There's
a
tool
called
cada
that
you
can
use
to
work
with
serverless
with
azure
durable
functions,
so
you
can
check
out
the
code
the
link
here,
if
you
want
to
learn
more
about
how
to
develop
serverless
azure
functions
in
kubernetes
and
dotnet
five.
Unfortunately,
all
right
as
of
today
durable
functions
is
not
supported
in
dot
net
five,
but
it
is
actually
planned
and
coming
in
few
years.
So
probably
when
there
is
the.net
6
is
in
preview,
we
will
be
able
to
use
durable
functions
in
that
net
five
framework.
B
It's
called
there's
a
there's.
An
article
called
durable
functions,
blue
green
deployment
strategy
that
are
also
worth
checking
out.
So
you,
when
you
have
time
you
can
review
the
video
and
maybe
take
picture
of
the
link.
So
you
can
visit
it
or
we
can
send
it
to
you
later
as
well,
and
error
handling
is
important
for
development
so
to
handle
errors
for
durable
functions.
Usually,
if
you
get
an
error,
you
get
the
function
field
exception
in
your
code,
but
to
handle
that
you
can.
B
What
you
can
do
is
you
can
call
another
function
activity
or
you
can
use
the
automatic,
retry
and
failure
method.
That's
ready
in
your
context,
in
your
durable
orchestration
context
and,
of
course,
the
traditional
try
catch
black
blocks
in
our
code
also
helps
in
touching
those
errors
and
handling
it,
and
here
is
an
example
of
that
here,
so
it
has
like
transfer
fonts
and
a
try
sketch
example.
So
if
there's
an
error,
it's
gonna,
retry
and
call
another
activity
function
to
credit,
the
account
that
something
went
wrong,
for
example.
B
So
when
you
want
to
develop
durable
functions,
there
are
several
tools
that
you
can
use.
You
can
develop
durable
functions
in
azure
portal
easily.
You
can
also
use
azure,
cli
and
azure
core
function
tools
and
you
you
can
also
code
locally,
using
visual
studio,
bs
code,
as
well
as
for
http
requests
and
debugging
with
web
app
apis.
B
B
Microsoft,
learn,
has
a
good
path
for
durable
functions
to
get
started
and
the
documentation
has
everything
that
you
need
to
know
in
all
concepts
and
examples
there
and
there's
also
a
youtube
channel
that
I
really
like
following.
It's
called
the
azure
functions
university
in
europe
in
youtube
by
ammar,
tucker
and
gwen
pena
sigera
sequenza,
where
they
go
through
the
the
fundamentals
of
azure
functions,
as
well
as
real
life
advanced
examples
of
of
it
so
definitely
check
it
out.
B
It's
a
it
is
a
good
free
resolution,
free
resources
and
I
also
wrote
the
blog
about
azure
dev,
durable
functions
and
dev
community.
So
you
can
also
check
it
out
and
some
developer
tools
you
can
use
csharp.net
and
this
tools
in
here
they
already
mentioned
as
well
and
nexus
will
be
the
demo.
Before
I
start
switching
my
screen,
I
wanted
to
show
you
what
my
demo
is
about,
so
my
demo
is
about
a
serverless
azure
cloud
storage
notifier,
in
which
I
will
be
using
the
function
chaining
pattern.
B
If
it's
sent
or
not,
I
will
be
sending
an
sms
and
a
call
to
me,
the
admin
admin
user
that
I
said
set
using
the
twilio
api
and
then
the
last
one.
It's
it's
still
in
progress.
I
was,
I
will
be
working
on
creating
another
function
to
fetch
those
messages
from
azure
service
bus
queue
so
mary's
before
I
present
it,
I
will
be
showing
what
I
expect
the
result
will
be.
For
example,
when
I
run
my
durable
functions
a
project,
I
should
be
getting
a
text,
an
sms.
B
I
hope
my
time
is
okay,
I
think
so
so
here
I
have
an
ongoing
project.
That's
not
final,
yet,
but
good
good
good
to
demo
anyway,
a
short
one.
So
I
have
an
a
project
called
serverless,
azure,
storage,
notifier
and
in
here
I
have
several
functions.
I'm
still
about
to
refactor
this,
but
let
me
see
so
I
have
a
starter
function,
which
is
a
blob
trigger,
and
here
I
have
my
connection
string
for
my
storage,
and
here
I
check.
B
B
What
data
I
want
to
store-
and
my
first
chain
is
that
when
I,
when
a
blob
is
uploaded
in
my
azure
storage
using
the
context
and
it's
triggered
the
orchestration,
I
will
be
calling
another
serverless
azure
function
to
save
the
the
message
composed
message
about
the
club
blob
like
the
link
to
the
blob
into
my
service
queue.
And
then,
when
it's
done
and
it's
done,
I
will
be
sending
an
sms
and
the
my
application
will
be
calling
me
and
then
I
will
be
logging
that
information.
B
B
C
B
B
I
added
I
wasn't
sure
exactly
how
how
many
it
was,
but
I
added
one
more
message
in
in
in
in
my
service
box,
so
my
next
function,
the
next
change
I'm
going
to
do
is
I'm
going
to
create
the
function
that
gets
all
the
images
from
the
service
bus
queue
and
show
it
in
an
application,
but
actually,
even
if
I
have
coded
any
front-
and
yet
I
can
actually
go
in
my
asher
portal
and
go
on
pic
peak
means.
I'm
gonna
like
pick
like
check.
B
So
so
that
is
my
short
demo
about
gerbil
functions
and
just
few
more
slides.
I
want
to
summarize
that
you,
you
learned
a
bit
about
durable
functions,
some
fundamentals
of
it
some
useful
and
examples,
helpful
resources
and
if
you
need
a
copy
of
the
code
or
the
presentation,
feel
free
to
contact
me
on
the
information
here
and
thank
you
so
much
for
listening,
and
I
hope
that
you
learned
something.
A
A
F
B
Yeah,
I
I
good
question.
Thank
you
mullen.
I
think
it
was
mentioned
on
my
presentation
that
it's
good
to
use
durable
functions.
Actually
you
can
both
of
them
are
serverless
azure,
function
and
durable
functions.
They
are
the
same.
They
are
like.
There
are
like
family.
The
only
difference
is
that
durable
functions
is
like
the
extension
of
durable
functions.
It's
like
the
enhanced
version
like
it
has
more
powers
because
it
can
pre
perf
it
can
let
you
develop
a
stateful
serverless
logic
without
losing
its
state.
B
So
if
you
have
something
that
you
need
to
to
perform
long
running,
then
you
should
use
azure
durable
functions,
but,
as
you
can
see
in
my
example,
I
kind
of
like
combine
actually
usher
functions
and
durable
functions.
What
makes
it
different
is
that
I
had
an
orchestration
that
kind
of
like
arrange
and
organize
things
how
I
want
it.
So
I
hope
that
answers
moline's
questions,
but
if
not
feel.
A
Yeah,
I
have
my
own
clarification
about
that,
because
what
it
was,
what
I
was
was
getting
here,
is
that
the
the
difference
between
the
two,
so
your
azure
function
right,
it's
it's.
Basically,
it's
atomic.
It
stands
alone.
You
feed
in
the
function
it
feeds
out
the
result.
It
doesn't
remember
anything
about
about
about
the
data
that
you
fed
in.
I
wanted
to
clarify
then
that
if
it's
a
durable
function,
does
that
mean
that
it
keeps
some
of
the
state
or
it
remembers?
Yes,.
B
Yeah,
okay,
it's
called
durable
because
it's
it
keeps
its
state
because
it's
like
in
one
place
and
like
I
have
an
example,
I
think
in
one
of
my
presentation
somewhere
here.
Let's
see,
I
had
an
example
about
I'm
sorry,
I'm
toddling.
There
is
an
example
here,
it's
good
to
show
this
one
here,
you
see
if
you
see
this
one.
This
is
like
on
the
right
side.
B
They
are
like
normal
azure
functions
and
they're
like
they
can
run
based
on
how
you
code
it,
but
this
one
this
azure
function
can
be
in
a
different
like
can
be
stored
in
a
different
virtual
machines
in
the
cloud
which
is
controlled
by
azure,
so
it's
kind
of
like
randomly.
But
when
you
use
the
durable
functions,
api
or
the
framework,
then
you
have
the
option
to
like
you:
don't
lose
the
state,
even
if
even
if
the
vm
is
restarted.
So
it's
like
that.
A
G
B
C
B
B
B
A
A
A
B
B
Yeah,
it's
it's
it's
kind
of
like
interesting
question,
because
if
you,
for
example,
you
have
you
have
a
mobile,
app
or
web
app,
it's
like
pass
and
serverless
is
like
serverless.
It's
like
two
different
deployment
models,
but
you
can
combine
it.
You
can
combine
it
by
having
an
event
in
your
web
app
or
mobile
app
and
use
triggers,
for
example.
What
I
did
I
had
like
a
blob
trigger
and
it
calls
the
api,
so
it's
possible
actually
to
to
build
an
api
or
services.
B
It's
like
it's
gonna,
be
like
micro
services
like
you,
create
each
function.
Activity
functions
is
a
mini
service.
Just
like
what
I
did.
I
had
a
function
activity
functions
that
sends
the
message
from
about
the
blob
to
the
queue
and
then
I
can
create
more
functions,
lots
of
functions
and
one
so
it
is.
There
is
an
advantage
in
using
that,
but
at
the
same
time
before
we
create
it
with
mobile
device,
we
need
to
check
how
it
works
for
different
environments,
so
I
hope
it
yeah.
It's
really
in
me.
B
B
G
F
F
A
A
A
The
thing
with
a
the
thing
with
a
freestanding
api
or
an
app
service,
an
asp.net
web
api
deployed
on
app
service
versus
this-
is
that,
okay,
for
for
going
back
to
one
of
your
slides,
you
said
about
you
said
it
was
about
con
control
on
one
one
side,
so
yeah
monolithic,
monolithic
approach,
you
have
control,
but
the
thing
is:
whenever
you
deploy
it,
every
single
part
of
that
api
goes
down.
So
all
the
end
points
go
down
all
the
all
of
that
need
to
need
to
be
yeah.
D
A
A
B
Like
my
separately,
just
like
my
sweet
example
like
the
monolithic,
it's
like
a
big
cake
with
different
layers,
microservices
is
like
cupcakes
and
then
the
serverless
or
the
functions
as
a
code.
It's
like
candice
like
the
lights
and
you
can
do.
You
can
choose
what
you
want.
If
something
goes
wrong
or
if
you
ate
up
the
candy,
then
you
still
have
those
other
functions
working
still.
It's
still
there
available.
A
B
Yeah
yeah,
they
are
actually
this.
This
the
same
for
service.
You
go
to
the
usher
portal,
you
create
a
service
and
you
actually
create
like
the
container
for
azure
functions
or
durable
functions,
called
function
up
and
in
your
function
app
you
can
have
durable
functions,
there's
different
kinds
of
a
template
and
trigger
that
you
can
create.
You
can
create
the
default
gerbil
functions
which
has
the
starter
template
in
it
or
you
can
create
a
normal
azure
functions
with
blob,
trigger
or
service
bus
triggers
and
different
triggers.
A
B
A
B
B
Yeah,
I
actually-
and
this
is
interesting
because
in
this
the
live
demo-
that
I
did
it's
like
it's
a
blob
trigger,
triggered
when
when
a
blob
is
uploaded
and
that
blob
trigger,
you
can
also
use
that
as
a
normal
functions
and
do
other
tests.
But
what
I
did
is
that
I
used
the
blob
trigger
as
the
starter
function.
To
kick
start
the
orchestration
this
one.
So
it
is,
it
is
possible
to
to
to
convert
it,
but
you
would
need
to
make
changes
in
your
in
your
code.
B
B
You
would
need
to
add
the
durable
orchestration
client
as
a
parameter,
because
you
need
the
this
client
or
the
starter
to
kick
start
here,
your
orchestrator,
so
you
can
just
create
minor
changes,
so
you
can
convert
it
and
when
you
change
your
normal
function
to
to
a
durable
orchestration,
you
will
also
need
to
build
your
orchestrator,
which,
which
requires
you
to
carefully
plan
your
workflow
like
what
I
did
here.
So
that's
why
it's
good
to
use,
try
catch
or
there's.
Also
another
method
here
called
call.
B
If
you
I
remove
this,
there's
also
something
called
all
retry
this
one,
so
you
can
also
call
it
retry
and
in
your
orchestrator
there's
also
another
feature
that
you
can
create
a
sub
orchestration.
So
there
are
a
lot
of
cool
things
to
do
or
you
can
do
with
durable
functions.
But
of
course,
there's
no
perfect.
B
A
A
B
Yeah,
actually
this
one.
This
is
the
the
demo
that
I
have.
This
is
just
a
simple
demo,
but
I
what
I
plan
to
do
so.
The
messages
that
I
have
is
in
that
was
sent
by
the
blog
trigger,
for
example,
in
the
in
my
blog.
When
I
received
the
blog,
I
created
a
post,
a
message,
and
I
come.
I
saved
that
message
into
the
usher,
service,
bus
queue
and
my
plan
as
a
practical
example.
B
For
example,
for
me,
that's
using
asher
when
I
upload
something
I
want
to
be
notified,
so
I
can
use
practical
examples
like
I
showed
like,
I
got
an
sms
using
the
twilio
api
and
I
even
got
a
call
or
I
can
later
on,
send
an
email.
So
I
do
that
by
retrieving
using
the
azure
service
queue.
So
there
are
different
scenarios.
For
example,
you
can
use
durable
functions
with
event
triggers
event
hub
for
your
iot
applications.
B
For
example,
you
have
an
iot
kit
that
wants
to
check
or
track
the
temperature,
and
you
want
to
get
sms
or
emails
notification
about
it,
so
you
can
use
or
combine
a
different
integration.
So
it's
kind
of
free,
the
practical
use
cases
it
depends
on
how
you
want
it
like.
Where
developers
we
can
build
anything
just
kidding.
A
You
could
probably
achieve
some
of
the
same
things
using
just
plain
functions,
and
then,
and
and
especially
with
the
event
hub,
you
could
you
could
I
mean
you
could
pass
off
the
state,
the
whole
the
whole
state
management
to
the
event
hub
itself
and
and
and
use
you
know,
use
that
as
your
event
store.
Basically.
A
B
B
D
B
A
A
Functions
were
supposed
to
be
stateless
in
the
first
place
and
and
if
you're
a
person
from
say
a
functional
programming
background,
you
would
cringe
an
idea
of
hey.
Why
are
you
putting
state
there,
but
but
but
microsoft,
I'm
being
microsoft
being
microsoft,
they
usually
want
to
address
a
lot
of
a
lot
of
scenarios.
D
A
C
A
B
Yeah,
and
also
not
just
different
ways
of
programming
give
us
it
kind
of
like
gives
us
the
flexibility
to
to
code
and
to
develop
something
based
on
the
business
requirements,
and
it
kind
of
like
make
it
like
a
hybrid
or
dynamic,
almost
like,
for
example,
in
databases,
were
used
back
in
long
time
ago.
We're
used
to
sql
and
structured
data.
Now
in
the
cloud
we
have
cosmos
db
that
can
handle
different
kinds
of
data
and
to
enormous
sizes
as
well.
B
So
it's
kind
of
like
we
developers
it's
kind
of
give
us
the
challenge.
We
developers
as
well
to
kind
of
like
be
intact
with
this
technologies
as
well,
and
choosing
the
right
service,
azure's,
functions
us
or
durable
functions
or
event
hubs,
or
triggers.
It's
really
important
to
know
that.
So
it's
good
that
we
have
this
tech
communities
like
finog,
that
does
these.
D
A
B
Yeah
I
had
I
had
it
here.
Let
me
just
go
to
the
end.
I
lost
it.
Yeah,
let
me
just
go
and
I
I
need
to
learn
how
to
go
to
the
last
part
of
my
slide,
this
one
yeah.
So
I
I
just
want
to
say
thank
you
salama
to
all
the
the
viewers
to
john
fina
philippine.net
user
group
and
and
the
dotnet
foundation
for
having
me
here.
B
A
B
B
Yes,
I
am,
I
recently
created
user
group
locally
here
in
sweden
it's
called
azure
user
group
sunsvale.
Currently
it's
new.
I
only
have
25
members,
but
I
have
some
sessions
coming
where
I'm
really
I'm
gonna
share
about
azure,
because
I'm
passionate
about
it
but
feel
free
to
join,
maybe
that
the
joint
to
the
link
and,
if
you're,
one
of
if
you're,
watching
and
you're
interested
to
share
knowledge
about
azure,
feel
free
to
contact
me.
So
I
can
organize
an
event
that
you
can
share
knowledge
in
sweden
and
internationally
so
feel
free.
D
A
B
A
B
G
D
A
G
E
F
A
Yeah
awesome
all
right.
Thank
you
very
much
jonah,
and
it's
really,
you
know
it's
really
great
dude
to
have
it's
really
great,
to
have
filipino
de
vero
filipina
developer
with
us,
and
and
also
someone
who
has
me,
you
know
who's
making
their
mark
outside
of
the
philippines.
So
so
thank
you
very
much
for
for
being
here
yeah.
So
I'm.