Our team is writing an Angular + Dotnet Core 2.0 Web API project. We are expecting this application to scale rapidly in the near future and therefore have some questions below:
Is maintaining server side state using sessions in a web api project a good practice? I understand this is not how REST works however would like to find out if maintaining server side state would benefit my application. We are expecting this application to scale fast in the near feature.
Can someone help me with how to benchmark and find out numbers to validate our choice? - be it a REST ful approach where we send state with each request or persist session state at server and minimize request payload and database trips..? I don't know where to start hence seeking some guidance.