Hello all,
My team is evaluating Blazor as an alternative to Angular for some upcoming front end work, and have been thoroughly impressed with it. At this stage of its development we think it will serve our needs nicely, but we still are in need of some guidance.
Our remaining questions have to do with how the server side version of Blazor would behave in a load balanced environment. The State Management section of the Blazor docs (https://docs.microsoft.com/en-us/aspnet/core/blazor/state-management?view=aspnetcore-3.0) does a great job of answering most of the questions we’ve had, and we plan on following that article’s recommendations. Here is what we are still wondering:
- Are there any changes necessary to the load balancer itself for this to work? We use sticky sessions for our current apps. I will need to explain any such changes to our infrastructure team.
- Aside from the changes necessary for .NET Core apps in general, are there any configuration changes necessary on the servers for Blazor to work in a load balanced environment? We are using Windows Server 2012, and will upgrade to 2016 at some point.
- Are there any other pitfalls we should be aware of? We have no experience with SignalR or other Websockets-based frameworks.
Thank you in advance to anyone who can weigh in on this.
-Craig