The MS Azure team will probably have a better answer, but this is what has worked for us so far.
- We have several application applications, each of which is in its own project (and solution).
- Of these functional applications, some have only one function, others have several functions in their own class / file.
- If we have several functions, this is due to the fact that these functions are associated with a certain area of ββthe functions of our system. Therefore, they work together, and it makes sense for us to support and deploy them as a group.
- Other functional applications are independent, containing only one function that performs work that is not related to any other function. For instance. we have one timer-controlled function that compresses some numbers and sends a push notification as needed.
- Grouping functions this way (so far) made sense to us, because it gives us a balance between keeping our deployment relatively simple and the ability to scale βgroupsβ independently.
In any case, this turned out to be good enough for our project, but I would be interested to know if there are better ways.
source share