I just read through your post on servers[1], as I'm currently in a similar boat (webdev working with C++ devs). I think the biggest hurdle for such developers a

I just read through your post on servers[1], as I'm currently in a similar boat (webdev working with C++ devs). I think the biggest hurdle for such developers are things like: - statelessness of the server (REST) - the lifecycle of a single request - the lifecycle of a single (server-)app (microframweworks) OOP devs unfamiliar with server development tend to pollute the app lifecycle with hidden state in some singletons that are swirling around globally. The requirement that servers should be able to parallelize request-processing is mostly an afterthought and hidden app state makes it impossible to parallelize anything. A sequence diagram of a single request would help there a lot IMHO and a short explanation of how to keep the response times short, by doing long-running tasks in the background with message queues. [1]: https://blog.isquaredsoftware.com/2020/11/how-web-apps-work-http-server/ https://blog.isquaredsoftware.com/2020/11/how-web-apps-work-...