I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I'm afraid I'm struggling to see the rationale for this.
PHP persists state with sessions, and the Apache, FPM, even old-school CGI systems are almost the equivalent of being "event driven". With some of these, you even have a PHP process resident so it's always available. There are many existing queuing systems that will let you defer activities so you don't block responses.
It's true that unless you use some kind of cron job you won't get timers, but the loop is otherwise the same. This seems like creating microservices for every individual task - each of which will tie up another PHP process.
What am I missing?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm afraid I'm struggling to see the rationale for this.
PHP persists state with sessions, and the Apache, FPM, even old-school CGI systems are almost the equivalent of being "event driven". With some of these, you even have a PHP process resident so it's always available. There are many existing queuing systems that will let you defer activities so you don't block responses.
It's true that unless you use some kind of cron job you won't get timers, but the loop is otherwise the same. This seems like creating microservices for every individual task - each of which will tie up another PHP process.
What am I missing?