That's bad advice, given how expensive it is to upgrade later.
You aren't gonna convince people familiar with Django that your API library is a Django replacement. That's like saying Express.js replaces Spring. Well, no...
> Also in my experience Django is extremely slow generally than Flask or FastAPI.
Nobody cares. Seriously. I can handle 100rps on a $5 server for most of the pages on my Django sites. Do you know how many $100m+ ARR businesses I've worked for that never hit 100rps on a regular basis? Most of them.
> for Flask / FastAPI
What about the dozen other dependencies you now need to use? and now you need to test those upgrades carefully, because python.
> Nobody cares... Seriously. I can handle 100rps on a $5 server for most of the pages on my Django sites. Do you know how many $100m+ ARR businesses I've worked for that never hit 100rps on a regular basis? Most of them.
I dunno, my clients paying my business care, speed is important in certain sectors such as mine.
I run and own a pest control SaaS on Flask that pulls in $1.7M+ ARR, when you're an upstart, speed is an advantage, I would imagine the $100m+ ARR business you worked for would be slow anyway.
> What about the dozen other dependencies you now need to use? and now you need to test those upgrades carefully, because python.
I just pin my dependencies, and since I'm making money it just runs itself really.
I should have rephrased it as "nobody picking Django cares". People pick Django because of how quickly you can build something valuable. Everyone knows it's slow IMO.
> when you're an upstart, speed is an advantage,
Yes, this is kind of the whole point of FastComments :) but still, the SLAs are like 30ms for most endpoints. I wouldn't use Django for this - but I wouldn't (didn't) choose Python either.
> I just pin my dependencies, and since I'm making money it just runs itself really.
Pinning is good. Never updating them is bad, gets a lot harder later.
You aren't gonna convince people familiar with Django that your API library is a Django replacement. That's like saying Express.js replaces Spring. Well, no...