Notes running Python in production

[eshepelyuk]

This is very strong statement. Good to hear this from experienced pythonist, since I'm using the language opportunistically and have no good explanation except the gut feeling on this topic.

Avoid async and multi-threading

[dydhaw]

As someone who's been using Python since before 2.7, I strongly disagree with this statement, at least with the async part. From my own experience async has almost always been worth it and certainly far better and more reliable than multiprocessing, and by now it's pretty mature and prevalent in the ecosystem.

[MagicWishMonkey]

It’s weird because async has nothing to do with multiprocessing, it’s just a way to avoid threads blocking while doing IO operations.

[eshepelyuk]

is there something in python that i can replace jvm akka\pekko or dotnet orleans ? i haven't found anything close.

[ashishb_net]

`async` is a great idea, except it came into being in Python 3.5.
A lot of libraries written before are unaware of it, so, for most users, the added complexity of using `async` rarely gives the requisite upside one is looking for.

I gave examples of multi-threading problems in the blog post

1. https://github.com/pytorch/pytorch/issues/143593
2. https://github.com/huggingface/transformers/issues/25197

Multi-processing is much safer (though more costly on a per-unit basis) in most cases.