https://github.com/stuartleeks/durable-funkiness
Playground for Azure Durable Functions
https://github.com/stuartleeks/durable-funkiness
Last synced: about 1 year ago
JSON representation
Playground for Azure Durable Functions
- Host: GitHub
- URL: https://github.com/stuartleeks/durable-funkiness
- Owner: stuartleeks
- Created: 2017-11-29T17:52:20.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2018-03-11T17:04:52.000Z (about 8 years ago)
- Last Synced: 2025-02-17T10:49:10.474Z (over 1 year ago)
- Language: C#
- Size: 30.3 KB
- Stars: 1
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# README
This repo is my playground for Azure Durable Functions.
Notes here are to help me remember what the heck I was trying to do if I ever come back to it :-)
## simple
This was an exercise in recreating a simple Durable Functions call to activity functions from scratch
## mock-storage-batch(-2)
These two projects are an exploration of a scenario involving batches of files being uploaded to Blob Storage.
The base scenario used as a starting point is:
* Each batch comes from a single customer and contains a known set of files
* The files that make up a batch vary by customer
* Processing should be initiated once all the files in a batch are present
* Batches should only be processed once
For simplicity, the function to retrieve the list of files required in a batch for a customer is just a hard-coded implementation but could easily be replaced with a call to a data store.
In both cases, HTTP triggers have been used for dev purposes as a simulation for blob triggers to enable easier exploration of event orders. Also, the blob access has been substituted with simple local file access as another simplification for rapid exploration.
mock-storage-batch caters for not receiving an event for every file - it just requires that there is at least one event triggered after the last file is written. I.e. it would handle a case where notifications are batched.
mock-storage-batch-2 requires a trigger for each file but is more efficient in terms of the number of External Events that it raises (which reduces the number of invocations of the orchestrator function instance).
In both projects there is a scripts folder with powershell scripts to exercise different scenarios.
## starting-orchestrations
This project is used to explore multiple triggers firing in quick succession for scenarios where you want all certain groups of trigger events passed to a **single** instance of an orchestration.
For this, the orchestration is kept really simple, and there is a script in the `scripts` folder that fires triggers in rapid succession.
The trigger function attempts to route all events for a given instanceid (a query string parameter passed in) to the same instance of an orchestration, creating it if it isn't running.
By tweaking the `count` and `delayInMilliseconds` parameters in the script you can exercise the function in different ways.