• C#
  • .NET 7
  • Blazor WebAssembly
  • Serverless API

Being an engineer focusing most of my time on C#.NET. I wanted to learn something new to put into practice for this project. There have been significant steps in Microsoft technologies I wanted to use that I have yet to use professionally, taking it all the way to production.

Since this was a learning activity. I decided to use Blazor WebAssembly because the idea of running the C# client side is interesting. This choice opened the door to hosting the application on Azure Static Web Apps. The content delivery to serve the WebAssembly assets, the API can use the Azure Function component of the Azure Static Web App. These decisions allowed for a short delivery cycle to a low-cost environment that can handle large traffic loads.

See the code homepage screenshot list of possible answers screenshot