Sticky sessions ensure that a user's requests are consistently routed to the same server in horizontal scaling. This maintains stateful interactions, such as user authentication, across multiple requests. Without sticky sessions, users might be directed to different servers that lack their session data, causing inconsistencies and a poor user experience.

Railway does not support sticky sessions (for now), as noted in their horizontal scaling documentation: https://docs.railway.app/guides/optimize-performance#load-balancing-between-replicas.

---

I'm reopening this thread, because the initial one has been closed as "solved" without literally any feedback:

• https://station.railway.com/feedback/sticky-sessions-fa65efc4