Should I use Blazor WASM over Blazor Server?

Question

I am new to Blazor. Articles suggest that Blazor WASM should be preferred over Blazor Server.

I am building a small Blazor Server app that needs to manipulate data stored in different Azure Table Storage Accounts. As of today, the connection strings to these storages are saved inside a static list.

If I understand it correctly, Blazor Server will run on Asp.Net Core with SignalR sending binary messages to the client for DOM-manipulation, while Blazor WASM will run inside the client browser and can thus be hosted on a very simple and cheap static web server. WASM can't however keep secrets (like the connection strings).

If I used WASM instead of Server, wouldn't I need a separate server with an API to serve my WASM Client connection strings and the like? Or should I put the connection strings in a table storage and somehow expose claims (?) for the storage to the application in Azure Integration Platform?

Any thoughts on this?

If you build your application correctly, you don't need to choose at the outset. The code base for both is basically the same. I have a Github Repo here that demonstrates how to structure your code/projects to run a version of the out-of-the-box WeatherForecast templates in either mode within the same VS solution. - github.com/ShaunCurtis/Blazr.Demo . — MrC aka Shaun Curtis