Hi, we rewrote in UserEngage few modules from python3 to golang.
On python we use Django, DB postgres&citus, rabbitmq, redis.
Our main cluster have more than 25mln API requests daily.
For us Golang is >70 times faster than Django.
On python we use Django, DB postgres&citus, rabbitmq, redis.
Our main cluster have more than 25mln API requests daily.
For us Golang is >70 times faster than Django.
Well it depends. It does handle clickjacking, XSS, i18n, l18n, identification, authentification, database handling, CRSF and much more out of the box.
Things that you eventually code yourself, or that you should disable if you don't need it.
What usually happens is that people delegate this complexity more and more to the front end, which becomes, indeed, bloated. Or install more libs. And code glue for them because they are not integrated.
All in all, Django is slow compared to go, but it's not bloated if you take it in the context of what necessary work it saves you. It's opinionated. It has sane default. It's ready to use.
Unless you plan to have static website or an unsafe one.
If you're in the 10% yeah it can be a pain in the butt. However it's not impossible or even particularly difficult to migrate to something else.