I built the same app 3 times | Which Python Framework is best? Django vs Flask vs FastAPI

[@maithriashokan]

I absolutely enjoyed this video. Not only did I learn about the 3 frameworks, but was in awe of the how you edited this video. Perfection!

[@epicserve]

I've been using Django for over 10 years, before version 1 was even released. I think one of the biggest advantages to Django is the ORM. The downside to Django is for an API most people use the Django Rest Framework, which doesn't seem as nice as FastAPI in my opinion. Another key advantage to Django is the structure and organization it provides with its concept of Apps. This is especially helpful and important for large applications. I think it would be really hard for me to switch from Django's ORM to SQLAlchemy.

[@mke7605]

Same here. I used Django since version 1.3. Did jab a bit with flash but always find myself back at django after a while.

[@rustytheded]

Same, working since 1.4. DRF is not that bad, but it's much harder to learn than FastAPI. Looks uglier too and the configuration just isn't worth it, especially for smaller projects. I'm still working with DRF at my job, but personal projects are all FastAPI now. Will probably change most of the job project to FastAPI anyways.

[@NishantCosmos]

@@komkaitkanchai8766 wow i'm amaze to see django vets here, i just learnt making basic django apps.

[@rawmetal3052]

with Django Ninja introduced, I don't think API should be a problem anymore in Django

[@mayankpant5376]

Why use ORM even 😂😂 just use normal SQL

[@WineZ22]

as someone who had experienced pain and headache due to non typed code, I am definitely going for FastAPI Not to mention the auto OpenAPI Docs which make it easy to integrate security automation tools like OWASP ZAP. For an api project this is great. Things like the admin panel and the front end can be built separately using Vue or something like that. I just need an API, so FastAPI it is. Thanks for the video. this is really helpful.

[@phipag1997]

Great video. Awesome how you managed to compare the three frameworks in such a short video while still being clear and concise about the pros and cons.

[@uju02]

Started Flask last year, it is currently rising up into my favourite framework, I’m enjoying my transition from PHP to Python

[@irotochukwu6313]

same too, I transitioned from php to python 3 years ago. python is so much cool.

[@kevinlesieutre]

@@spooddyy developp in something you like, so you'll dive deeper without even noticing and you'll become way better and your time way more valuable.

[@TortelliniSRL]

Hey how does flask feel compared to laravel? I've been using and loving Laravel for years now but i want to try something else cuz php still feels kinda ancient, how would you compare the two? Is Laravel more similiar to Django instead? (I would only need it for backend, usually my frontend is angular/react)

[@spooddyy]

@@TortelliniSRL you should stick with it, laravel is good, you just need a backend framework doesn’t mean you have to learn all of those are exists.

[@TortelliniSRL]

@@spooddyy i agree with you for that but learning multiple framework kinda is my job ahahaha, anyways in our company we main laravel for backend and our cto is now giving us the chance to switch to one that could potentially suit our needs better, the learning curve won't be a problem since it will most likely be a gradual change (most of our stuff still run laravel backend), i was just wondering if it was worth to switch (if the writing time efficiency / potential less package support ratio was)

[@DanhWasHere]

Really great speedrun of the different web frameworks -I'm glad that you didn't give a definitive answer for which is best, only giving the pros and tradeoffs of each so a good dev can pick which one fits with their use case

[@Voidstroyer]

I mean, not giving a definitive answer is good and all, but an opinion at the very least would be appreciated

[@davidmcken]

@@Voidstroyer The pros for each library showed their strengths and where they should be used. Django enforces a specific file structure and layout and comes with the python-esque "batteries included". I would hazard a guess its used in larger projects because of that structure so there is less conflict between the teams (e.g. frontend guys are primarily in the templates, backend would be between models and views). Flask is extremely light-weight and you can build something functional in an extremely small codebase (I believe he said 47 lines of code excluding the HTML template). One of Flask's major pros is you can choose what library you want for every part of the process, don't like the templating engine? Cool, pick a different one. Want to write your SQL by hand and bypass the ORM entirely, np. In that way it completely gets out of you way and allows you to choose the right tools for your use case. FastAPI seems to follow Flask's general structure but adds batteries for an extremely common use case which is RESTful APIs (while not throwing in the kitchen sink like Django) and makes use of the type-hinting in python 3 avoiding issues the other two had to contend with prior to that feature being added to python. Its relative youth would be a double-edged sword, for greenfield uses you don't have any technical debt in the form of backwards compatibility with existing code, however on the other hand how well has it been battle tested? On pypi its still listed as Beta, should I expect breaking changes in the future? If you are confident you can keep up with its development it probably would be the most performant of the three especially with all the performance enhancements coming in python 3.11 and later.

[@Voidstroyer]

@@davidmcken Thank you very much for the detailed explanations of the pros/cons for each choice.

[@Deadlious]

I prefer using Flask, because it gives a lot of flexibility. You can easily use it to build a similar structure to the Django app and separate stuff (yes with a bit more manual work, but possible), but it is not something obliging to make an application work. And especially for smaller projects, it gives a lot of freedom. In addition to that, latest versions of flask support async/await functions. FastAPI seems like it is build for APIs and not fully fledged websites, so probably it is best to keep it that way.

[@youssefchaabi5402]

I can programme big and fast Web projects by Flask only ?

[@Deadlious]

@@youssefchaabi5402 why not?

[@youssefchaabi5402]

@@Deadlious Flask good in scaling ??

[@youssefchaabi5402]

@@Deadlious OK bro thank you

[@kamal-hassan]

@@youssefchaabi5402 what did you go with? Flask?

[@tjbredow]

I love flask for rapid development. Our projects never get very big because we run a microservice model. I can build out new logic for a new api feature, run the pipeline and publish the swagger file, all before lunchtime. Even moderately sized apps can be managed with blueprints fairly easily, and Flask 2+ supports nested blueprints. SQLAlchemy and Pandas do enough for me, I don't feel the need to abstract away the DB like an ORM coerces. Rails does a lot better than Django in that aspect IMO. Also, you should be escaping query arguments and variables used in the URI ;)

[@adityadeshmukh2390]

For microservices flask and fastAPI For full stack django It depends on use cases what kind of application you want to develop

[@iamlegqdev7743]

@manny I'm definitely not an expert, but I would say FastAPI given that you'll probably want to build backend microservices for your app, and then just create frontend clients (for web, android, ios, etc) that communicate with your FastAPI backend.

[@GurashishSingh1]

Love this!! That FastAPI docs generation is super neat!

[@iamqaasim]

This is just the video I needed 👌 I can't belive you managed to do this is under 20min 😅 well done 🙏

[@patloeber]

thank you!

[@SiaTheWizard]

Man, it was awesome. I have started Flask for a while & this was a nice big picture for the backend roadmap.

[@d3f3kt57]

Thanks to this video I switched from Django to FastAPI and I don't regret it one bit. Django does a lot of things that are hidden to the developer and has a very complicated structure which is overkill for simple apps. With FastAPI it actually feels like you're coding. I wish I had checked it out sooner rather than wasting my time/energy on Django.

[@johnnygarcia7297]

I did the same, fastapi also gives you more freedom since django only lets you use its dependancies while fastapi lets you install and work with whatever, not to mention faster and more lightweight only the tools you need

[@nayrbbg5508]

I agree.

[@pawlack]

I regret starting with Django instead of Flask. If I knew Flask earlier then I would have better grasp of what is going on in django :)

[@HaBhBo]

true, if i would start again i would learn flask then learn django, as flask helps you understands how django does things under the hood.

[@creed404]

Yup flask is a gem

[@tejas4054]

Flask is complicated because of code written in one file,,, there is no MVT structure which is easy to wrte codes in different files

[@tejas4054]

Django is super easy that the most complecated fastapi and flask

[@miguelfrosales01]

Once you work long enough using Django you end up knowing what is going on inside. What you find in django is a very well developped structure. I personally dont care if fastapi is faster, because I can just scale horizontally my django service. microservice. In the long run the bottleneck is 99% of the time the database. Whe programming you want a mvp asap you don't get to waste time trying to integrate stuff, you just want something that works well fast, that's why I'll stick with Django. That being said I it is not very good when it comes to handling websockets, I'll usually go with node

[@jakeditslear1678]

Big fan of Flask, but I might have to experiment with FastAPI!

[@vitalnikod7197]

me too

[@meizufluxx]

fastapi has awful docs

[@NishantCosmos]

@@meizufluxx but faster and better development if you learn it right?

[@meizufluxx]

@@NishantCosmos no fastapi is awful because the docs are awful. they desperately need an api reference

[@d34dplayer]

For any "basic" app the documentation is enough, the only times I have had to dive into the fastapi code was for more customized OAuth and even then the source code isn't that cryptic, I've been using it for over a year and it's my go to for rest APIs that don't require massive scalability. The biggest difference with flask and django is that if forces you to make a distinction between frontend and backend, ideally only making a rest api that a static frontend consumes, but I see this as a better way to build web apps as it forces you to learn about frontend frameworks that are way better than anything a python framework can provide.

[@grantbellar3267]

I’ve recently gotten into python development and this was a video I didn’t know I needed! Thanks for your hard work!

[@oncedidactic]

Super helpful video thanks!! This is exactly what I needed: a QUICK overview of these Python options, how you get up and running, how they differ. I have a spaghetti monster Django app at work and I need to make an on-the-side api service, wondering if I should just start completely fresh or try and integrate with the existing beast. Separation of concerns, ease of implementation, and developer role structure says Flask it is. 👌👌

[@kierencoetzee2517]

i like Flask's context management with the app factory pattern, very easy to get hold of application-wide config and db instances

[@devdex.]

true

[@minorandrianarivo661]

Best thing about Django is that it's a fullstack framework. In a structure that needs frontend development, building backend API is easier and faster with Flask and FastAPI, but I need typing so... Going for FastAPI !

[@IUfidi]

Ca va, mon ami.

[@oliverreviews8496]

I can tell you more. In large projects nobody writes code without typing :D So you made a good choice :D

[@huacai168]

Django-ninja is a good choice

[@spooddyy]

@@huacai168 it really doesn't matter what you use, end of the day its all about python and how you're implementing your python mechanism into web.

[@biskitpagla]

@@spooddyy tech debt is a real issue lmao

[@balloney2175]

Awesome! but not for beginners. This is how programming should be taught, I believe. Straight to the point and not long video.

[@talanky]

Great editing on this! It was the perfect speed for me instead of watching a 2hr code along

[@Balkac]

Very nice comparison! Even though I'm Django dev myself, I can imagine how complicated it must seem compared to Flask for instance. Maybe you should have shown an example with class based views to see even more power of Django.

[@marcelmoraisluna]

Great man. I don't work with Python, but the simplicity is just great.

[@d.TheFrreman]

Thank you so much for the great video! The direct comparison shows a lot of the specific possibilities. 👍👍👍

[@jonasls]

I've used flask for a long time but switched to Django for a new project at work - man, it's really a good all-around package for full stack production web apps. Love the way things are organized into apps, and all the libraries which make your life easier. Like Celery for background tasks.

[@josedominguez8782]

Celery is an standalone tool. You can use it with Flask, FastAPI and any other framework.

[@dipenketanbhaidave154]

Brother can you suggest best project in flask , for Intern resume.

[@jonasls]

@@josedominguez8782 True, but I was thinking about celerys direct integration to django - "django-celery".

[@jonasls]

@@dipenketanbhaidave154 Issue tracking system

[@Semmelein]

Using Django since 0.96 or so and I just love it because of all the batteries included.

[@wilhelmngoma9009]

Great content. Thanks Patrick. This was my first experience of Flask and FastAPI. So far Flask and Django are my favorite. I'm experience all of them more

[@rishiyogil.n.7222]

1000 thanks to you, Iam a Cloud Arichtect wanted to choose one py framework to learn and was confused, you cleared everything, I decided to go with flask, thanks man

[@JohnnySins-zf4fb]

Coming from FLASK to Django it is so much easier in Django when it comes to scalability for further upgrade than Flask

[@zoozalp]

Great video! All the info needed in just 16 minutes.

[@bogdanf6698]

I really enjoy the constancy of your voice and the equidistance when presenting the 3 frameworks

[@josesebastiancolaneri7125]

I use django in backend and react js in frontend.. For me its really awesome the organization and structure you get with django. I also used django-rest-framework, and for API apps drf is the best choice in my opinion.

[@jonathanidioseph5101]

How do u merge the two together?

[@asii_k]

@@jonathanidioseph5101 not the original commenter but we do the same where I work. Front end services just either make HTTP calls to the backend and/or can listen to or send RabbitMQ (sometimes pub/sub) messages. They're all microservices so each component is it's own discreet unit that just pass data between themselves

[@waititsnilson]

@@jonathanidioseph5101 you merge front and backend through rest api, where the frontend makes requests to the backend

[@gh0stb0y98]

​@@asii_kresourses to learn microservices with django-react ?

[@NagibDev]

Thank you for this. I have mostly been using python for data science but I'm looking to start building out web apps.

[@ND-gn8tc]

What you should notice about FastAPI is that it has dependency injection built in. Try configure tests for complicated microservices without DI. Oh boy patching all the consumer/producer/external api/sdk calls will be a huge mess. Just impossible to integration test without messy mocks instead of clean DI.

[@MoneylessWorld]

@Francisco Mendoza Torres yes

[@ND-gn8tc]

@Francisco Mendoza Torres yes it is a killer feature

[@subipan4593]

Why do you need DI in Python? As far as my understanding, DI is just bundling different modules/components together at RUNTIME. In static languages like Java and C# you'd need DI. In Python, you can assign any variable to any object at runtime. I would like to know why you'd need it in Python? Python has DI built-in isn't it?

[@ND-gn8tc]

@@subipan4593 makes it easy to setup tests and test, thus, you can achieve extremely high coverage

[@subipan4593]

@@ND-gn8tc ONLY when you're using static languages like Java. Python is dynamic language that can change data types in RUNTIME. No need for DI in python.

[@michaelmarkoulides7068]

Very helpful video saved me a ton of time thank you . I’ve used fast api for purely api and backend in the past I love it , I have never had to develop anything with a frontend or view or using any jinja templates so this was very useful . My favourite is fast api , I built a websockets framework with tornado in the past , I love tornado it’s solid when it comes to websockets and async aswell so but at the time fast api didn’t exist , django was too cumbersome for my needs at the time and flask was too light weight . I had redeveloped a small api with fast api and it’s definitely my first port of call for a web framework in python the autodoc feature the auto reload the pydantic built in so easy validation makes it a pleasurable experience once you get over the learning curve which is not so bad cos the documentation is really good and the speed for a python framework is really fast in production . Overall a pleasurable development experience

[@mariuszzawierucha1310]

Thank you! That's a comparison which I was looking for! Summarising : Flask - easy & nice to develope, low entrance level. FastAPI - great performance, with a little more code we are able to handle 2-3x more requests. Django - the hardest to learn, not that obiviouse, but comes with great features if you dive into. Last one prefered by compannies which use python. So for home & hobby project (flask or fastapi), or for people concetrated on python job dev position - Django is right way. BTW Parick -which one of these is your favourite one?

[@cedric1731]

Flask-restx features Automatic Swagger creation as well :)

[@johnmahugu3527]

Sehr Gut Patrick, Danke Schon hehehehe i really enjoyed this, now i can use it to introduce the concepts to my students. great work.

[@oseitutu598]

Amazing Video, Much appreciated. I learned a lot from this. Subscribed ❤

[@ekaetteessien4932]

Love this video! I use the FastAPI framework and it's absolutely amazing. I'm working on learning Django now but it was useful to learn the differences between the frameworks.

[@Gabrielowns321]

Managed to create a pretty cool app with a massive database using Flask in 6 weeks, its great.

[@SadiqueHajwane-d6l]

Django's syntax seems cleaner and more readable than others

[@MagnusAnand]

All of them are good, but I like the Django style

[@comedyclub333]

As a mostly-flask-user I've been using bottle for the last few months. Man, this framework really blew my mind. While the basics are nothing special, advanced in-depth knowledge really makes it one of the most powerful (as in flexiblility and performance) frameworks in my opinion.

[@sovietwarmachine1979]

You could say you've been "hitting the bottle" for the last few months! *badumtsss* (I'll see myself out now...)

[@youssefchaabi5402]

I can programme big and fast Web projects by Flask only ?

[@mohammedalbatati5529]

Many thanks that’s a lot of work well done. I started couple of years ago with Django and found my self stuck with it 😅 Maybe I need to explore more specially the fact API looks interesting

[@architkapoor2503]

It's called FAST API.

[@Ehsan-the]

Flask is so cool for small and medium size projects and can increase your speed in so many ways, i dont have any experience with fastapi but it looks the same.

[@JalalMujawar]

For those who are getting error for the flask code, at 2:37 replace line 18 with app.app_context(): # Creating the database tables db.create_all()

[@CesconetoG]

Iv been trying to puzzle out what he says @ 6:26 for more than 10 minutes but finally figured it out: type hints, not type in, nor tie pins (as the auto generated captions believes he means)

[@mikesturyan9]

I use fastapi for my api' and starlette for web apps. Fastapi is built over starlette, so there is little paradigm shifting. I don't personally like Django as it sets too many rules. I would just build a vuejs front end instead of Django, then an api layer with fastapi.

[@BehruzbekOtayev]

"vuejs front end instead of Django"? Really? How are Django and VueJS comparable?

[@johnniefujita]

@@BehruzbekOtayev i think he meant that he is not using the front end template engine provided by django out of the box. Using django just to build the api. Which is actually norm in production for quite sometime already.

[@yasayah7289]

I would love a fastapi + vuejs tutorial!

[@yoannguillard6877]

@@yasayah7289 take it separately, "vuejs tuto rest API" and "fastAPI tuto". The only glue is to serve your static files generated by vuejs.

[@herantd]

Vuejs and flask is match from heaven as well

[@manusharma8777]

A very clear comparison indeed. Thanks.

[@hipertracker]

For REST in Django use Django REST Framework and all CRUD operation can be defined in a single simple ViewSet class. Plus every CRUD can be paginated, filtered with a simple one more code line.

[@VanguardOnline2011]

Thanks for the detailed code comparison Patrick, especially with the in-depth code comparison. That was a lot of work. Much appreciated. Thanks. I also looked at your channel. Lots of useful tutorials. Thanks. Subscribed.

[@BrianStDenis-pj1tq]

I struggle with the idea of microservice versus framework. In our company, we aim to build microservices. A microservice is either a visualization layer or maybe business logic or maybe an entity store service. The first example (Flask) had all of those combined.

[@SarateanuDima]

As Java Senior for sure I would like to know about Fastapi. But still it's not so good structured as spring boot web. But I like it.)))

[@cupajoesir]

If I had more time I'd write a shorter letter. Thank you for a short and concise video. Very well done!

[@Ggldoork]

Super impressive video! Covered a lot of info concisely - must have taken a lot of time! FastAPI seems to pique my interest for a micro-service based app. Also seems to get a lot done without a huge learning curve. I’ve worked with Django and it’s awesome! if you know your way around.

[@xzex2609]

Awesome useful video , in the end I think that the Django is the best option , and it was cleaner and very powerful one. but those other two were good.

[@christianpenguin2651]

For sure, this video was a lot of work, thanks for it! Now I'm once again on the verge of deciding between an older well-tested Framework (Django) and a cool newcomer (FastAPI)... nerd problems...

[@abinmichael3661]

FastApi is best one for API development my experience Thank you

[@wackytheshaggy]

Great overview . My more opinionated take: Fastapi for simple APIs and micro services, django for anything more complicated. As soon as you have a db, you’ll want an admin app. Any large app in flask ends in the desire to have used django. And btw, with a class based view the django code could have been even simpler. And things like caching and django_q for queues bring the speed in complex apps.

[@davidmcken]

Agree fully, the batteries Django includes are hard-won battle scars from those that went before you. There is usually very little benefit in re-inventing the wheel, focus on whats unique to your app. For smaller projects you should be designing to avoid those issues in the first place.

[@Sam-tg4ii]

10:14 Can the FastAPI's documentation page be used as a GUI for the API where the user POSTs values and gets responses back? Can it be hosted on a server for public access?

[@alexturner6417]

No comments! Just subscribed 👍

[@TheAbhimait]

Hey i use Pyodbc and write raw sql queries in flask. I am able to do everything. I want to know is there any major benefits of using ORM?

[@professor-dad]

Great presentation! Thanks for all the time you put into it. 👍🏼

[@christianm4906]

As someone coming from other programming languages, I find FastApi the most attractive option.

[@PythonDevelopment]

Great content, dude! Awesome!

[@alisonhj]

I got to know FastAPI with this video and it looks great! Also great job with your video!

[@warloccarlos8522]

I have experienced Flask and Django both. Nice comparison. I liked Flask, as you mentioned, it is quick for beginner and also we can run custom scripts easily with flask to display output on web.(I know we can do the same with FastAPI and Django as well 😄)

[@ijazali8618]

I have completed 3 projects in Django now interested in API, but confused a little bit what now I choose DRF or FastAPI. I read on web that FastAPI is easy and fast but Django REST API is secured. Which I now choose become a conflict for me, now need guide from seniors Django developers with their experience in this regard.

[@facundogoiriz7323]

It is Flask for me, i love the simple and intuitive way of handling things with Flask, its the most Pythonic of the 3 and also the most functional, and i love working in a functional way.

[@robin888official]

Do you mean functional in a paradigmatic or in an efficiency way?

[@facundogoiriz7323]

@@robin888official in a paradigmatic way

[@majkelpl8611]

@@facundogoiriz7323 Can you give any examples? I moved from a functional language to Python and the whole language is by no means functional. Still, Pythonic way of writing most things fullfills my need for "clearness" and conciseness. I am using Flask too and I think it's very neat.

[@marcvanoldenborgh6218]

Thanks Patrick, for this excellent work.

[@mke7605]

Have been using Django since version 1.3. Also used flash for some minor service. But fast api looks very interesting.

[@davidarbanas6056]

Congrats on hitting 100K!

[@Alisson-Faoli]

well... the three of them are obviously really good. That's totally a matter of personal choice.

[@biojui1]

Great video! thanks for the examples

[@k2icc]

Similar stuff on Stremlit or out of the equation for what is used for?

[@ragsdale9]

This was a fun little exercise in the different frameworks. I think I must be using a different version of python or something because using flask exactly like you wrote it seems to give me an error regarding using it outside of the app context. Which can be fixed with a few lines of code appropriately placed, if you understand where and why. For the rest of them this is what I wanted to see coming here (although the post/get/put/delete not being fully hashed out did kind of bother me).

[@NagibDev]

@ragsdale9 can you provide the few lines of code for the fllask example. Im getting the same error

[@NagibDev]

hey I was able to find the solution on github haha!

[@balloney2175]

Hey Patrick, Your video is awesome! thanks for sharing. On index 7:50, I have to exclude "autocommit=False" b/c it is not working, and it says "internal server error" or something like that. After I that, it is working like breeze!

[@Marco-cx6gp]

What's the theme you're using? it's so neat! I want it

[@DevlogBill]

I've only used Django for only 4 months, and I love the framework. Just out of curiosity have you tried creating a frontend project like Angular or React or maybe mobile like a flutter or React native with one of these backend technologies? Is Django easier when used for making a GET request for a frontend technology? Or would you recommend one of the other backend technologies like FastAPI or Flask instead? Not sure yet but I am thinking about focusing on Django with React or maybe Angular for Full Stack, any thoughts? thanks Patrick...

[@aariskazi9002]

Thank you so much for showing fast API database system I was stuck very long time thanks a lot for the video

[@fullStackInKannada]

Very nice & clear explanation.

[@fernandostahelin2972]

Great comparasion!

[@PedroGrilo13]

Clear and concise video. Thanks :D

[@GaborKalucza]

Hey, what theme are you using? Thanks!

[@shafaitahir4728]

Thank you for this video, it helped me get an idea of what to start (i didnt understand anything 😅😅) but it gave me an idea as what to expect from each one. A hard decision to make of which one to begin with. any suggestions or roadmap are welcome, Thanks.

[@anandraj2895]

I recommend django . Because it has better orm query lookups , clean architecture , easy to maintain , performance and optimization.

[@krissn8111]

I prefer Flask but the FastAPI automatic API documentation is really cool.

[@johnniefujita]

async support is incredible too

[@varossimonyan]

Very useful vide, thanks bro!)

[@dennis9567]

1:31 How can you create a python environment in terminal?

[@tukurhamid]

Thank you bro, this is helpful

[@LukePighetti]

was hoping for a retrospective at the end!

[@likithraj855]

Why are we creating a venv file? Aren't we already running the files inside a python interpreter within an environment? Also, my python environment which I created is in a different location, and the location for the folder scripts are in a different folder. How to run the export variables in this case if my flask library is installed in main interpreter location of the environment and not on script location? Current I am facing this error: export: The term 'export' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

[@joel9909]

The backend course I will be doing (Meta) uses Django, and I am also interested in Node. But mehn Fast Api seems powerful too, and Flask seems easy enough to prototype things with speed Subscribed

[@JaimeSilva]

Dam boooy! I have just read all the comments! I started using Django for fullstack about 3 years ago. I work mostly by myself so I don't need to separate frontend from backend. I'm curious about FastAPI but it's a struggle with the community when you're comming from the Django world. When I'm stuck with Django I'm likely to find the solution in the internet more easily than with FastAPI and that's easy to understand because Django been around for much longer. The most captivating thing for me in FastAPI is the assychronous part. I tried Django Channels but it's relatively complex. Still think that all the frameworks are being updated constantly so I'm not too dramatic about the "best choice".

[@vhaangol4785]

_"Still think that all the frameworks are being updated constantly so I'm not too dramatic about the "best choice""_ - Right on point sir. I agree that Django Channels is a bit complex, but there have been prod applications that have integrated Django Channels decently. Check out baserow.

[@JaimeSilva]

@@vhaangol4785 Thanks for pointing! I'm gonna take a look at that one!

[@nathanwebb2800]

I use flask & gunicorn in docker containers but FastAPI's self documenting seems kinda handy....

[@Hubert4515]

i used to do all my work in Flask but recently i switched to FastAPI and i like it a lot

[@kevinmerrell9952]

Very interesting. Thanks for posting this.

[@hallo-xp2wh]

congrats for 100K You are giving great content, thanks a ton!

[@timmehtimmeh576]

Thanks for the detailed walktthrough. I was hoping to get an overall judgement or review of each. What is your answer to the "which is best?" question?