FastAPI

“My favorite combo is NextJS with static export and fastapi backend.”

“Python FastAPI was an easy decision, since an open and accessible API was a nonnegotiable”

“I already migrated all of my projects off rails, moving to fastapi”

“fastapi was picked simply because it was already known by the team and had a very thriving ecosystem”

“the solution seems to be an escape hatch where CPU-bound work is executed behind a thread-pool”

“by suggesting using dependency injection to manage database connections”

“FastAPI encourages you to open a db connection and a transaction at the front of every request”

“FastAPI is operating more at that level but also adds the often unnecessary complexity of async.”

“If you're in an ecosystem where a lot of the async boilerplate is free/cheap (ex: FastAPI)”

“their OpenAPI generation isn't always perfect if you have very polymorphic endpoints but it is really good compared to other tools”

“The agent uses Pydantic for validating FastAPI schemas”

“Everything else is bloated, slow and doesn't give you enough room for optimization.”

“Python with FastAPI, well known and stable library”

“Backend API Python with FastAPI, well known and stable library”

“This is a lot more flexible, and it has allowed me to work again on the project.”

“I've been doing a lot with Datastar and FastAPI recently”

“I'm beginning to come round to the benefits of OpenAPI now which seems like a big note in FastAPI's favor”

“If you're writing FastAPI (and you should be if you're doing a greenfield REST API project in Python in 2026)”

“the hard work that the original designers of libraries like FastAPI, Zod, Pydantic, have invested in”

“Django-ninja is essentially the fastapi of the django world so this library would be enough for me to go all in on fastapi.”

“Pydantic + FastAPI are my two favorite python shops right now”

“I briefly played with FastAPI, and after the same shock I discovered Django-Ninja”

“finding a lot of that is build-it-yourself (and easily break it) is a bit of a shock.”

“I chose FastAPI and Pydantic specifically to give that same "get out of my way" developer experience”

“which in terms of speed isn't too far from an equivalent app written in Go”

“it also constructs dependencies per request instead of singletons”

“The performance gains are lost, by double when you attempt to build real real software with it.”

“things hang together much more loosely and it means the integration just isn't as complete”

“I end up with a little more stylistic flexibility.”

“FastAPI is the best combination of an easy and a flexible Python library for web servers, from my experience.”

“in any meaningful benchmark it's one of the slowest commercially used pieces of web software the industry has adopted”

“making those rapid iterations that tools like fastapi allow can be pretty important”

“René actually had to implement a batching worker API to work around a limitation in Python's FastAPI, which handled requests per process”

“FastAPI ecosystem is type-first and works well.”

“FastAPI+Unicorn is good but it is barebones compared to what django already has.”

“this looks more sane decision as for me then rather radical jump into Node.js”

“it’s so easy to screw up async FastAPI and bring things to a halt.”

“auto enforcing json schemas on endpoints is huge”

“I would still pick FastAPI/SQLAlchemy over Express and PostHog.”

“FastAPI, which should have been the right tool for the job”