I think you are referring to the GIL, but that is for threads, not for processes (They confirmed they were referring to the GIL). That is CPython implementation detail, not a python spec. Regardless, The GIL makes sure no two threads are acting at the same time, however in a server this is mostly irrelevant because tasks are just waiting on I/O, the process is I/O bound, not CPU bound. Also, the task server I am describing here, like I said already, is placed in the same python server because I was only given a few hours to create it. In the real world, this task manager is representing what would be either a "lambda function" a queue processor, or any other external data processor (I imagine it would be Map-Reduce or similar at scale)