Earlier quoted context omitted.
> - no state (which also means no memory leaks), Ehh, what? Sessions are state. > - just drop a file on web server and it works (no crazy CI pipeline) Except when I have to set-up php-fpm, opcache and configure countless parameters in php.ini. > - the documentation is fantastic, Yes, but I still have to check it for useless constructs like "mysql_real_escape_string" vs "mysql_escape_string" which should have never ex…
> Sessions are state Is database state? > php-fpm, opcache Nope > countless parameters Certainly not > "mysql_real_escape_string" vs "mysql_escape_string" There are only a handful of these, and you can learn about them with a simple google search.
Duh. I'm talking specifically about session_*. This data isn't magically stored in the air and if you use more than a single machine, you need to implement the SessionHandlerInterface with a solution like redis or memcached in a clustered setup. That's literally the same as using any other language, plus such map-reduce kv stores.
Since you mention that I wouldn't need php-fpm and opcache, I assume that you haven't worked at scale with php. php might be a good fit as long as you don't have any users, but this isn't true for everyone.