We are currently using sessions and session affinity in our apps. But going forward, especially in Micro Services/Docker model does it make scene?
Eg: If we bring up a new container due to high load, requests will still route to old continents due to the session. If we kill a container that is associated with some session where should the request go? We have written (I think) a session aware router for Docker. It's ok for external apps, but I think it defeats the purpose of containerization, due to about reasons. I think the correct way to do this in our apps is to, have authentication as a service. A micro service will translate the session-id to a token. App depends fully on the token. What do you think? -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : [email protected]
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
