After many years of working with Django, I decided to take a closer and more serious look at FastAPI.
Extensively using both frameworks has helped me understand their actual strengths and weaknesses with greater accuracy.
More and more, I find it challenging to form a relevant opinion on tools I've never used. Reading documentation or blog posts like this one is not enough, as some things simply don't "click" in your mind until you experience them firsthand.

Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

The post compares Django and FastAPI, highlighting their strengths and weaknesses based on real-world experience. Django offers an 'all-batteries-included' approach with everything you need in one package, while FastAPI focuses more on flexibility and performance, requiring additional setup for many features. Django enforces a structured MVT architecture and has a more democratized governance model, whereas FastAPI offers more control and modern features like async support and type safety but relies heavily on external tools. Choosing between them depends on your specific project requirements and the type of skills you want to develop.

Django vs. FastAPI, An Honest Comparison

Muito bom! adorei, gostaria de um artigo que descreva se existe a possibilidade de integração de ambos, reunindo o poder dos dois mundos.

Thank you for your honest comparison

very interesting reading, great to have feedback from someone who worked with both

Nice article about django and FastAPI