question

karishmatiwari-msft avatar image
karishmatiwari-msft asked ·

[MSDN Redirect] Best suitable approach to host Angular 8 application into Azure web app

Hi All,

Have one angular 8 app and wanted to host that into azure web app as anonymous access. I have gone through all the available option while creating App Service Plan (Free, Basic, Standard and Premium V2) but confused about the best approach and plan.

Just for your reference:

  1. Angular app is very much light (3.5 MB) after production build.

  2. All CRUD operations are happening using logic app

  3. SharePoint list has been used for DB

  4. This app will be accessed by more than 7000 users

  5. Traffic will be very high in this app as this will be access by anonymously by anyone.

Please help me to figure out the best web app plan with minimized pricing and high availability.

let me know your suggestion on this.

Thanks...

Source: (https://social.msdn.microsoft.com/Forums/en-US/3bb4d3dd-1807-44a6-b9e7-f8307d995967/best-suitable-approach-to-host-angular-8-application-into-azure-web-app?forum=windowsazuredevelopment)

azure-webapps-development
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

BryanTrachMSFT avatar image
BryanTrachMSFT answered ·

lalitmishra1988, before replying, I want to say only you will ultimately be able to determine the needs of your app. The below are only suggestions and should not be taken as consulting due to the number of factors that can impact the needs of your app.

With that being said, this sounds like a production app. We typically only recommend production apps to be run on standard/premium/isolated tiers. You can see the availability SLA along with the other attributes here. The basic tier might be able to run your application but if you're concerned about availability, you might want to stick to standard tier or higher. If you only plan on running a single site on an instance, you'll likely be okay with something like a standard small (S1) instance. If you have a resource intensive site or multiple sites in your app service plan, you might consider a medium (S2) or large (S3) instance.

You also might want to consider scaling out vs scaling up. What you talked about, basic/standard/premium is in regards to instance size. If your concern is having a high number of visitors, you might want to consider scaling out by adding more instances to your App Service Plan. This is the better approach to handling large amounts of requests rather than changing your instance size. While this blog is older, it talks about the basic concepts of when to scale up vs when to scale out.

Since you mentioned high availability, one thing to be careful about is to not think that having two instances in the same app service plan will provide redundancy. While unlikely, if the network goes down in your data center, both instance will be unable to communicate with the internet. To resolve this problem, you would want to consider using Azure Traffic Manager (ATM), which is a load balancer that can direct traffic to multiple apps in different regions. You in theory could create a West US app and East US app and then use ATM to route traffic to whatever region is available. This option is best for mission critical sites or store fronts that could lose money caused by a single instance outage. For more information on ATM, this is a good place to start.

Let me know if you have any further questions or concerns.

Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.