Recommended
More Related Content
What's hot
What's hot (20)
Similar to Advanced Durable Functions - Serverless Meetup Tokyo - Feb 2018
Similar to Advanced Durable Functions - Serverless Meetup Tokyo - Feb 2018 (20)
Recently uploaded
Recently uploaded (20)
Advanced Durable Functions - Serverless Meetup Tokyo - Feb 2018
- 3. Events イベント React to timers, HTTP, or events from your favorite Azure services, with more on the way
- 4. Events イベント React to timers, HTTP, or events from your favorite Azure services, with more on the way Author functions in C#, F#, Node.JS, Java, and more Code コード
- 5. Events イベント React to timers, HTTP, or events from your favorite Azure services, with more on the way Outputs 出力 Send results to an ever- growing collection of services Author functions in C#, F#, Node.JS, Java, and more Code コード
- 8. •
- 9. • •
- 10. • • •
- 11. • • • •
- 12. • • • •
- 13. • • • •
- 15. •
- 16. • •
- 17. • • •
- 18. • • • •
- 25. Function chaining Fan-out / fan-in
- 26. Function chaining Fan-out / fan-in
- 27. Function chaining Fan-out / fan-in
- 28. Function chaining Fan-out / fan-in Event aggregation
- 29. Function chaining Fan-out / fan-in Event aggregation
- 30. Function chaining Fan-out / fan-in Event aggregation
- 31. Function chaining Fan-out / fan-in Event aggregation
- 32. Function chaining Fan-out / fan-in Event aggregation
- 33. Function chaining Fan-out / fan-in Event aggregation Extended Status Monitoring
- 34. Function chaining Fan-out / fan-in Event aggregation Extended Status Monitoring
- 35. Function chaining Fan-out / fan-in Event aggregation Extended Status Monitoring
- 36. Function chaining Fan-out / fan-in Event aggregation Extended Status Monitoring Async HTTP APIs
- 37. Function chaining Fan-out / fan-in Event aggregation Extended Status Monitoring http Async HTTP APIs
- 38. Function chaining Fan-out / fan-in Event aggregation Extended Status Monitoring http Async HTTP APIs
- 39. Function chaining Fan-out / fan-in Event aggregation Extended Status Monitoring http Async HTTP APIs Human interaction / timeout
- 40. Function chaining Fan-out / fan-in Event aggregation Extended Status Monitoring http Async HTTP APIs Human interaction / timeout
- 41. Function chaining Fan-out / fan-in Event aggregation Extended Status Monitoring http Async HTTP APIs Human interaction / timeout
- 42. F1 F2 x 1000 F3
- 47. Activity Function Orchestrator Function Orchestrator Function Execution History Orchestrator Started Execution Started Task Scheduled, SayHello, “東京”
- 48. Activity Function Orchestrator Function Execution History Orchestrator Started Execution Started Task Scheduled, SayHello, “東京” Orchestrator Completed
- 49. Activity Function Orchestrator Function Activity Function Execution History “Hello 東京!” Orchestrator Started Execution Started Task Scheduled, SayHello, “東京” Orchestrator Completed Task Completed, “Hello 東京!”
- 50. Activity Function Orchestrator Function Execution History Orchestrator Started Execution Started Task Scheduled, SayHello, “東京” Orchestrator Completed Task Completed, “Hello 東京!”
- 51. Activity Function Orchestrator Function Orchestrator Function Execution History Orchestrator Started Execution Started Task Scheduled, SayHello, “東京” Orchestrator Completed Task Completed, “Hello 東京!” Orchestrator Started
- 52. Activity Function Orchestrator Function Orchestrator Function “Hello 東京!” Execution History ? Orchestrator Started Execution Started Task Scheduled, SayHello, “東京” Orchestrator Completed Task Completed, “Hello 東京!” Orchestrator Started
- 53. Activity Function Orchestrator Function Orchestrator Function Execution History Orchestrator Started Execution Started Task Scheduled, SayHello, “東京” Orchestrator Completed Task Completed, “Hello 東京!” Orchestrator Started
- 54. Activity Function Orchestrator Function Orchestrator Function [“Hello 東京!”] Execution History Orchestrator Started Execution Started Task Scheduled, SayHello, “東京” Orchestrator Completed Task Completed, “Hello 東京!” Orchestrator Started Execution Completed, ["Hello 東京!"]
- 55. Activity Function Orchestrator Function [“Hello 東京!”] Execution History Orchestrator Started Execution Started Task Scheduled, SayHello, “東京” Orchestrator Completed Task Completed, “Hello 東京!” Orchestrator Started Execution Completed, ["Hello 東京!"] Orchestrator Completed
- 56. ダメ！
- 57. 1. ダメ！
- 58. 1. 2. ダメ！
- 59. 1. 2. 3. ダメ！
- 60. Worker Stateful/Partitioned Stateless Control Queue(s) Triggers orchestrator function execution Work Item Queue Triggers activity function execution History Table
- 61. Worker Worker Worker Stateful/Partitioned Stateless Control Queue(s) Triggers orchestrator function execution Work Item Queue Triggers activity function execution History Table
- 62. Worker Worker Worker Worker Worker Stateful/Partitioned Stateless Control Queue(s) Triggers orchestrator function execution Work Item Queue Triggers activity function execution History Table
- 72. • • HTTPS://DOCS.MICROSOFT.COM/EN-US/AZURE/AZURE-FUNCTIONS/DURABLE-FUNCTIONS-OVERVIEW • HTTPS://DOCS.MICROSOFT.COM/JA-JP/AZURE/AZURE-FUNCTIONS/DURABLE-FUNCTIONS-OVERVIEW • • HTTPS://GITHUB.COM/AZURE/AZURE-FUNCTIONS-DURABLE-EXTENSION • HTTPS://GITHUB.COM/AZURE/DURABLETASK/TREE/AZURE-FUNCTIONS • • •
Editor's Notes
- Purpose: Review the basics of Azure Function Takeaways: Azure Functions is an event-driven compute platform You only pay for the code executions
- Purpose: Review the basics of Azure Function Takeaways: Azure Functions is an event-driven compute platform You only pay for the code executions
- Purpose: Review the basics of Azure Function Takeaways: Azure Functions is an event-driven compute platform You only pay for the code executions
- Purpose: Review the basics of Azure Function Takeaways: Azure Functions is an event-driven compute platform You only pay for the code executions
- Purpose: Show the various services that bindings can connect to. Takeaway: There are a lot of services that can be connected to and we are committed to adding more.
- Purpose: Show the task-based programming model. Things to emphasize: Orchestrator functions coordinate the calling of activity functions. Activity functions can be called either synchronously or asynchronously. Whenever an await instruction is encountered, the orchestrator function will automatically checkpoint its progress. This way, if the process or VM your function is running on recycles or reboots, local state isn’t lost.
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state
- Purpose: Walk through a simple hello world scenario to illustrate how the runtime executes orchestrator functions. Emphasize: the use of event sourcing pattern to rebuild local state