The /healthcheck is more or less used by most load balancers to test if a server is available.
The health check is only one of the features that IIS ARR can use to determine the best server to dispatch http requests. For wisej that is the first request that upgrades the connection to WebSocket mode.
Yes, if the application server goes down the session is lost.
We are talking about ARR, right?
Quoting Web farms in .NET and IIS part 3: Application Request Routing ARR
ARR doesn’t have its own solution for high availability so it cannot handle failures to the server hosting ARR – the result is that the ARR server becomes a single point of failure.
So my Wisej web server no. 1 is part of a Web Farm. If my server no. 1 goes down, what happens to this guy that was in session on web server no. 1? Since Wisej sessions aren’t transferable, I guess he will get a new session on server no.2 but all context will be gone. Will he have to start from the beginning, login, etc?
We don’t use ASP.NET sessions. Wisej sessions work in memory. You can plug in a custom session manager if you like, but it sill must be in memory.
Deserializing from a string on every request like a traditional web page would cripple the system to becoming unusable. Wisej uses many tiny packets back and forth all the times through a live WebSocket connection, which cannot be transfered to another server.
Load balancing works with the /healthcheck configuration. Wisej is able to tell the load balancer when to stop hitting a specific server depending on session count, cpu load, memory percentage, etc.