In my experience it was overly complicated, unflexible, and a nightmare to work with. Flask and fastapi were more lightweight alternatives, where the development experience is much less 'dreaded'.
The only advantage I saw is it lets you do a lot of things out of the box - the most useful for us being the GUI to see and edit whatever tables you want in the DB. So our CS (and other internal users) can grant user permissions that way, without us needing to build dedicated UI features for it.
I actually found the opposite experience with Django 😅
It comes with a template rendering system, auth, and a lot more, but a lot of that is not needed nowadays with the decoupling of frontend and backend.
I found it works best with Django Rest Framework, so it's basically just used as a REST API with JWTs. However, I see a lot of newer companies built on Supabase nowadays because the dev experience is so much better.
I think they wanted to avoid introducing a database for storing the directed rooted tree. Because it increases operational complexity. Also they were comfortable running MySQL.
Perhaps you could read through the references for extra information. Thanks
I was curious to see that Django is still used in modern software 😅
hm, I wasn't lucky to work with Django.
But I know people running Django in modern apps.
What was your experience?
In my experience it was overly complicated, unflexible, and a nightmare to work with. Flask and fastapi were more lightweight alternatives, where the development experience is much less 'dreaded'.
The only advantage I saw is it lets you do a lot of things out of the box - the most useful for us being the GUI to see and edit whatever tables you want in the DB. So our CS (and other internal users) can grant user permissions that way, without us needing to build dedicated UI features for it.
I see, I tried Flask - and it was a pleasant experience.
Thanks for sharing these details.
I actually found the opposite experience with Django 😅
It comes with a template rendering system, auth, and a lot more, but a lot of that is not needed nowadays with the decoupling of frontend and backend.
I found it works best with Django Rest Framework, so it's basically just used as a REST API with JWTs. However, I see a lot of newer companies built on Supabase nowadays because the dev experience is so much better.
Why did they choose to store the workflow DAGs in MySQL?
I think they wanted to avoid introducing a database for storing the directed rooted tree. Because it increases operational complexity. Also they were comfortable running MySQL.
Perhaps you could read through the references for extra information. Thanks
This is the clear system design article I've been looking for as a beginner. Thank you, this was well worth the read!
I'm glad to read this, thank you
Can you share the process of learning all these? Like where did you get all these information from a company? Thanks!
Please see the references: https://newsletter.systemdesign.one/i/141865472/references
Awesome, in-depth article, NK.
Thank you for the shout-out too 🙏
thanks, Jordan