4 ms·

One web request should not be served by one process at a time. This is a terrible software architecture which is just the fault of python. I love python, but it

One web request should not be served by one process at a time. This is a terrible software architecture which is just the fault of python. I love python, but it is not suitable for backend work at scale. Its simply too costly in terms of resources required. While its interesting to see improvements in the GC, it also makes equal if not more sense to migrate away from python. Just my 0.02$

sametmax 9y ago
> One web request should not be served by one process at a time It's doesn't have to be. You can use asyncio and deal with many requests at a time by one process. > I love python, but it is not suitable for backend work at scale. What's at scale ? Most projects I work on IRL, including in banks and administrations, never reach the level of scale this even remotely a problem. Too many people think they are Google.
- ComputerGuru 9y ago
  Do you mean intranet bank apps? Or public facing sites?
  - sametmax 9y ago
    It doesn't matter. In France, there are 70 millions people. Remove old and young ones, and the ones that are not clients in your bank. Then spread the usage on the week, then on 24h, divide by the number of requests that actually hit your Python backend (so no cache, no static files, etc). You got what ? 1000 requests/s top ? That's nothing. Bank sites are not youtube. Besides, operations on your bank account don't even hit the Python backend, but a dedicated system. Usually some COBOL dinosaure they froze, wrapped into a Java service and exposed through a RESTish API so that the rest of their system can use it without ever having to touch it again.
    - figgis 9y ago
      And if you were really wanting to get as much performance as you wanted out of python there's plenty of options like epoll...
danso 9y ago
How many systems are people working at that have greater scale than Instagram?
- ComputerGuru 9y ago
  Net connections means nothing. How many servers does IG dedicate to this task? Compare IG’s server budget with another company’s and then divide by the number of servers. Not so unimaginably, out-of-reach big any longer.

sametmax 9y ago

> One web request should not be served by one process at a time It's doesn't have to be. You can use asyncio and deal with many requests at a time by one process. > I love python, but it is not suitable for backend work at scale. What's at scale ? Most projects I work on IRL, including in banks and administrations, never reach the level of scale this even remotely a problem. Too many people think they are Google.

ComputerGuru 9y ago
Do you mean intranet bank apps? Or public facing sites?
- sametmax 9y ago
  It doesn't matter. In France, there are 70 millions people. Remove old and young ones, and the ones that are not clients in your bank. Then spread the usage on the week, then on 24h, divide by the number of requests that actually hit your Python backend (so no cache, no static files, etc). You got what ? 1000 requests/s top ? That's nothing. Bank sites are not youtube. Besides, operations on your bank account don't even hit the Python backend, but a dedicated system. Usually some COBOL dinosaure they froze, wrapped into a Java service and exposed through a RESTish API so that the rest of their system can use it without ever having to touch it again.
  - figgis 9y ago
    And if you were really wanting to get as much performance as you wanted out of python there's plenty of options like epoll...

danso 9y ago

How many systems are people working at that have greater scale than Instagram?

ComputerGuru 9y ago
Net connections means nothing. How many servers does IG dedicate to this task? Compare IG’s server budget with another company’s and then divide by the number of servers. Not so unimaginably, out-of-reach big any longer.