Web Application Design: Session or Session

Question

I wanted others to explain to me which approach is better: using a session or creating one without a session. We are starting to develop a new web application and have not yet decided which path to follow.

An ion-free design is preferred:

Pros:

• Scalability. We can have as many servers as we want, without having to use a user session. Each of them can process requests (for example, load balancing using a cyclic cycle).
• Saves server resources. We do not need to allocate memory on the server side (again - scalability).
• No need to recover after server reboot.

Minuses:

• Some user-related information needs to be stored in cookies (not critical).
• More coding is required (but not very much code).

Are there any topics that we need to remember before making a final decision?

Answer 1

( ", " , pastebin, jsfiddle ..!). - 16- ( " , bla-bla", http- ), , , , , " " - ! , , .

- : mySQL . , .