Hosting Plans in Azure

00:00

when you create a function nappy natural

00:02

you require to choose a hosting plan for your function up,

00:06

let's see what the hosting plan is and what choices you have.

00:12

Microsoft offers three different costing plans for functions. Consumption plan,

00:18

premium

00:19

and dedicated.

00:21

When you create a function app, you required to choose one of those plans, as well as a storage account

00:28

that will be used to store the files and triggers for your function up.

00:33

Let's look at each individual plan and see how they differ.

00:38

The consumption plan is that the four plan that you can choose for the gradual functions

00:45

the consumption plans scales out and in automatically. But keep in mind that each execution has a warm a period that may impact the performance of your application.

00:56

The benefit of this plan is that you pay only when the function is running.

01:02

If your application is used irregularly, this can save you a lot of money because you don't need to pay for infrastructure. When it is not used,

01:11

you can coming go more people function naps on the same hosting plan if you are. If they are deporting the same region.

01:19

However, be careful with that because if you have many functions that consume resources concurrently, Europe may suffering performance

01:30

functions. Running on the consumption plan have Hartley meets for how long they can run

01:36

the default time out these five minutes and the maximum you can set istan.

01:42

This means that the execution of your coat needs to be complete before the time out expires, which does not allow you to have long running processes.

01:53

The consumption plan also does not allow you to vary the size of the execution environment.

01:59

You're limited to 1.5 gigabytes of memory in a single CPU core.

02:04

If you need more, you need to choose one of the other plans.

02:08

As I mentioned earlier, the consumption plan is the most cost effective plan, and you're built their execution and the amount of memory used by your function.

02:21

The premium hosting plan is similar to the consumption plan in a sense that it scares automatically to your needs.

02:28

However, the premium plan gives you more flexible choices in advanced capabilities.

02:34

With the premium plan, for example, you can have perpetual work instances that do not require startup time and improve your application performance.

02:44

You have also the option off unlimited execution time

02:47

and Severo instance, sizes that you can choose from.

02:53

The premium plan also allows you to have virtual network connectivity, which means that the access to your functions is restricted to the virtual network. This increases your security.

03:05

Of course, the pricing of the premium plan is different, and it is based on the number of course seconds and the memory Europe functions use.

03:15

The dedicated plan is intended for customers who have under utilized instances that are used for other APP service applications like Web apps. For example,

03:27

with this plan, you have the option to provide your own images images for your functions.

03:34

The dedicated plan requires many or scaling by default, which means that you need to be careful when there is unpredictable demand for your functions.

03:42

There is, of course, out of scaling option,

03:45

but you need to explicitly configure it.

03:49

The pricing of the dedicated plan is the same as for the other upset of ESOPs like Web ups.

03:57

One thing that you need to be aware of when using dedicated plan

04:00

is that if you plan to deport functions that require other triggers, then the http trigger like for example, Q or scheduled triggers.

04:10

You need to turn on the always on feature on the plan.

04:14

Else you risk that your triggers do not fire the function.

04:17

The default time out for the functions. Deporting the dedicated plan is 30 minutes, and, of course, you can configure them with unlimited time outs.

04:30

Let's finish with the visual showing how the hosting plans work

04:34

so you can have a single hosting plan that can cause multiple function ups.

04:40

Each function up can have multiple functions inside that implementing different functionality