Summary
In this chapter, we discussed how the durable orchestration system comprising activities and orchestrators helps to solve a wide variety of use cases. We then walked through adding Durable Functions to our existing Functions code from the previous chapter. Via debugging, we demonstrated how the orchestrator rebuilds its internal state, and how to get information into a running orchestration instance. We then discussed some helpful tips to clear the local durable store during development and touched on some additional features and pitfalls.
In the next chapter, we‘ll take a look at related concepts including Table storage, Aspire, and some additional advanced API topics.
