honestly i think what http server frameworks get majorly wrong is allowing programmers to have excessive amounts of local state, instead of forcing a better model of using a database backend/memory caches/etc properly by being like, well your script only runs for this request and then it terminates. this is one of the few things php actually gets right
because shit like synapse is inherently unscalable only because it was architected wrong and i blame unrestrictive programming frameworks for letting that happen
i'm thinking abt running services across many small non-coherent nodes and it's like
nextcloud? yeah it's probably trivial
synapse? well,,,,
fuchsiaaaaaaaaaaaaaaaaa
@f0x i mean it's php
i assume you just set up nfs for the filesystem, connect all the nodes to nfs, connect them all to postgres, start up php-fpm on each node and load balance across them with a reverse proxy and that's about it
i don't think they're using any weird tricks to circumvent global state in php but i may be wrong