3 ms·
I've experienced something similar using asyncio as well, but I think you're wrong to blame the inherent complexity of concurrent programming. I've used curio
by harpiaharpyja 4y ago
I've experienced something similar using asyncio as well, but I think you're wrong to blame the inherent complexity of concurrent programming.
I've used curio as an alternative concurrent programming engine for a med-large project (and many small ones). In comparison to asyncio, it's a joy to use.
- kissgyorgy 4y agoWhat I'm saying if you don't need concurrency, don't trade off simplicity. For REST APIs and websites, probably not needed.
- jerrygenser 4y agoRest APIs and websites are IO bound. Your python program is there purely coordinating between disk io, database (network) io, calls to other services (io). You can be choreographing thousands of requests concurrently and still barely doing any cpu. The overhead to do a similar service using threadpools is much higher and the reason asyncio exists.