The DB is all that matters. Python can scale very well through parallelization. So long as one doesn’t restrict themselves to one process, there’s really little chokepoint.
Nope… CPU and memory usage matter as well… if they get exhausted, you get throttling. This also has an impact on server-costs… Why run 2 instances of something that serves 4k requests/second over one instance that serves 9k/s (just an over-exaggerating example)
That’s why I say if you don’t restrict to single process. As to why something which might be slightly more inefficient (it’s not going to be that much), it’s because of ease of development and pool of potential developers to help you with it.
![Lemmy Developer removes comment in [email protected] for asking Russians if they are being oppressed by their government and if they support the ukraine war.](https://lemmy.blahaj.zone/pictrs/image/420f4965-78c7-427f-b3e7-64eaa58b84e6.webp){kind=link}
There’s no way Python and Flask are going to scale as well as Rust. It’s going to require more hardware to run and be able to handle fewer users.
The DB is all that matters. Python can scale very well through parallelization. So long as one doesn’t restrict themselves to one process, there’s really little chokepoint.
Nope… CPU and memory usage matter as well… if they get exhausted, you get throttling. This also has an impact on server-costs… Why run 2 instances of something that serves 4k requests/second over one instance that serves 9k/s (just an over-exaggerating example)
That’s why I say if you don’t restrict to single process. As to why something which might be slightly more inefficient (it’s not going to be that much), it’s because of ease of development and pool of potential developers to help you with it.