Hi ElegantCoyote26 , by default, sessions simply generate a time-limited token and do not consume server resources. You can keep such a session, or start a new one, it shouldn't make any difference (of course, generating a token requires a little bit of work on the server side, so constantly doing that is not a good practice)
Generating a token is another API call the server needs to handle, so if you have a lot of services constantly running, using the same session in each service saves up on API calls and thus puts less load on the server
can you elaborate a bit on the token side? i'm not sure exactly what would be a bad practice here