Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
If we're talking about performance, GoLang outperforms the two in both concurrent requests and latency. What nodejs has over Python in general, is its async nature -- making it not only easier to handle more concurrent requests, but much more reliable.
At the end of the day, it really all comes down to use case and scalability, but from local tests and what I've gathered, Python is a nightmare for handling concurrency.
I should also add our data tier service is coupled with multiple other services, further explaining my rant.
So I'm getting brought into a team for our backend services of our administration application, and they're explicitly using Flask (Python library) for their exposed API in their application and data tiers.
As I'm familiarizing myself with their code, utilities, and dependencies, I notice they're stacking 7-8 decorators on their routes from their in-house utility module.. After further investigation, I realized half of them were entirely unnecessary, and they were proofing payload responses three times for the same JSON format.
The fact that we're using Python instead of Node or GoLang for our REST services is pain enough, but these god damn in house utilities are killing me.
undefined
wk60