Blazor Hosting Cost Analyst


 

I have spent some time looking at if Server-Side Blazor App is better than the Client-Side Blazor App, Blazor Hosting Models post.  I decided to look at it from a cost position and see if there is any benefit of one way over the other.  

I took a simple Blazor Application that I wrote Inspirational Quotes and create both a server-side application and a client-side application.  I then deployed each.  For the server-side application, I deployed as an Azure app service, free trier.  For the cient-side application, I deployed that with Azure blob storage statice web site.  The goal was to just focus on the cost of each deployment.

After the deployment I had several users access each web site several times a day.  This was to simulate a light usage, such as a sample app from a blog or portfolio would get.  I monitored the sites for 30 days.


Actual Cost

I was a little surprised to see the cost for each deployment and utilization for 30 days was $0.00!

Other Interesting Findings

Even though there was no winner in the cost aspect of the test, I was able to learn a couple of other tidbits of comparison information.


1. Custom Domain Names

  Advantage: Client-Side 

I wanted to add a custom domain name to each web site.  For the client-side, it is very straight forward to add the custom domain.   And there is no additional cost.

On the server-side, in order to add a custom domain, you have to upgrade to the next service tier.  This increased the cost to $9.99 per month.


2. Ease of deployment

Advantage: Server-side

Deploying to Azure app service is quick and easy, whether you are doing it via Visual Studio, Azure DevOps, or Github.

On the client-side, We deployed by publishing to a file folder and updating the Azure blob storage.  You can set up a Github for the publish folders and then automatically deploy on check-in.  This is still an additional overhead than using an app service.


Best Of both 

The most reveling find was that I can combine both the free Client-Side for the front end and deploy my API based backend to an Azure App Service on the free tier since the APIs do not need a custom domain.  





Doing this exercise helped me be better prepared going forward to solve problems using Blazor in a cost-effective manner.

Comments

Post a Comment

Popular posts from this blog

Yes, Blazor Server can scale!

Image
From the very beginning of the release of Blazor Server naysayers have incorrectly stated that Blazor Server can not scale.  They usually state that the limit is 5,000 concurrent users. There are several misconceptions and wrong assumptions about their statement.  Let's break it down and get a better understanding of Blazor server-side scaling. What is the "limit" for users When Microsoft talks about the need to scale an application, what they are saying is that when a normal response for any concurrent user is taking longer than 200 ms, the system is not performant and needs to scale. We will accept that definition: If any normal user response is taking longer than 200 ms, the system needs to scale for concurrent users. By a normal response, we are referring to a page get, a post, etc.  Large database access requests would not be included in this measurement. What is scaling There are 2 common ways to scale, scale, out horizontally, and scale-up, up vertically. In our di
Read more

Blazor new and improved Search Box

 Back in March, I posted a new Blazor data grid with a search box ( see post ).  Since then I have found a new and improved search box that I wanted to implement.  The search part is implemented the same.  What I added was the ability for the user to narrow down the search by selecting which field they wanted to search on.  This will help the user find what they are looking for and in a large collection, the search will end up being faster. The goal of making the change was to make the search box a new component and have it handle the UI functionality part. Prep Work Here is the prep work I did before adding the search box: Started with the source code from the post listed above. Upgraded the project to .Net 5 Upgraded the Nuget packages that were out of date. Ensured every build and run. Change to a Component I wanted to create a component for the search box so I could use it in other applications.   1. Create a Folder under UIControls called "SearchBox" 2. Created a new raz
Read more

Blazor Wizard Step Component

Image
 I like using step wizards in my applications, sign-up forms, shopping cart checkout, and complex data entry, but I had not been able to find a wizard step indicator that I liked so I built this one. As it turned out, it was not as hard as I thought it would have been.  There are a couple of key parts you have to keep in mind when using a step wizard, such as: 1. What step am I on? 2. Should the "Prev" / "Next" buttons be enabled or disabled on this step? 3. What kind of visual clues do I show the user? I will walk you through how we answer these questions in this sample project.   HTML The main container has a div that holds the progress divs, one div for each "step" of your process.  Below that we have our "Prev" and "Next" buttons We will need to wire in the on-click events for the two buttons.  The buttons will need to be able to be disabled and enabled via CSS class settings.           <div class="container">       
Read more