Skip to content

Latest commit

 

History

History
242 lines (193 loc) · 21.5 KB

functions.md

File metadata and controls

242 lines (193 loc) · 21.5 KB

GENERAL

AWS LAMBDA COMPARISONS

CANCELLATION TOKENS

CONTACT

ARM TEMPLATES

COSMOSDB AND AZURE FUNCTIONS

DEVOPS

DURABLE FUNCTIONS

ISOLATED

LEARN

MESSAGING

POWERSHELL

MONITORING

PERFORMANCE

PREMIUM FUNCTIONS

Pre-warmed instances are shared by all apps in your plan. So, with 3 apps with low load and a minimal memory footprint you would be running on just your pre-warmed instances. You can only deploy Function Apps to this plan, no other resource, like Logic Apps can share that capacity.

You are always billed for 24/7 usage of your minimum plan size with Premium Funcitons. So, multiply your min plan size by the number of seconds in your month and the CPU/memory size you’ve chosen to get that minimum cost. Once you scale beyond that you are charged at the same CPU/memory rate for the time you are running on a worker at the full CPU/memory size of that instance. There is no per-execution billing and multiple Function apps are loaded onto the same worker if there is capacity.

Notes on moving functions across zones that include premium - https://github.com/Azure-Samples/functions-csharp-premium-scaler#setup .

SAMPLES

SECURITY

SERVICE FABRIC V AZURE FUNCTIONS

SWAGGER

Status 09/19 . v1 framework can spit out swagger def. v2 framework in portal cannot. need to augment with nswag or something like it.

UNIT TESTING

VERSUS WEBJOBS

MISC

SEE ALSO