Django REST framework

My Situation: I am both

1. Working on a startup/side hustle app, an interactive fitness journal that tracks and recommends exercise as well as makes creating meal plans trivial, in Flutter where the back-end will tentatively be written using Django REST framework as a REST API. For what it's worth Microsoft Azure will be my cloud of choice.

2. I'm also trying to transition away from an on-prem senior engineer to a Cloud Engineer.

Flutter is a firm choice for the FE however I'd really appreciate some guidance on which tools I should consider using to be in line with contemporary cloud languages and tools as well, if it is a good idea to suck it up and put Python on the back burner so I can learn JavaScript. I need things like ORMs, User Auth, etc.

Can anyone please advise?

Hello all,

I've been following the Django style guide from HackSoft (https://github.com/HackSoftware/Django-Styleguide) for a while now and I really liked it.

So currently at my workplace the project I'm working on, our lead architect (he's from .NET background I have asked a question a month back on a similar note) has asked me to write the Django code as per DDD principles (service layer, repository layer, entity layer etc) so after going through many articles and videos regarding DDD found out that following DDD principles in Django is an overkill.

Since I really like Django style guide and Django way of doing things, I am unable to convince our lead architect on following Django way of doing things/the style guide from HackSoft. He wants me to strictly use DDD principles. So with DDD I believe we cannot make use of any 3rd party Django libraries.

For example, I'm using Django REST framework for API development he's asking me not to use serializers, authentication & permission classes, and a lot of other things. Instead, he's asking me to write all these things without depending on Django/Django libraries. So his way of thinking is, code should be framework agnostic. For that if we want to migrate to some new framework then with DDD principles easily we'll be able to achieve is what he says. Also he said with DDD we can write pure unit test cases.

But from my POV, I guess it is doable. But since many people are using Django, DRF, and a lot of great 3rd party Django libraries it is battle tested and integrates great with Django. But if we follow DDD then we're missing out on these things, and again we have to reinvent the wheel for all the tasks which Django actually provides I think.

Seb Corben who gave DjangoCon 2022 talk on DDD Django says that for simpler projects and short term projects, it's not effective.

Lastly, I want to know have you guys tried DDD with Django? Can you please share your thoughts on this?

So currently I have experience in Node.js, but just to expand my stack knowledge and for getting backend developer roles, I thought of learning another backend-related language/framework. I have heard about Django, Golang, and Spring. I am mostly trying for backend API roles, and far as I've heard, Django REST framework can be a pain to work with. I've heard there are issues with Golang for package management (like how recently the Gorilla web toolkit is archived) and as for Spring, it's a vast ecosystem to learn so not sure if it's worth investing in. I would like to know which tool/framework to learn, which can help me get high-paying jobs and has a lot of scopes, and also which is great for making REST APIs. Any other tool that can do the job better than these three is also welcome!

I am planning on creating an application using the following tech-stack. Vue.js (TypeScript) for the front-end, Django (specifically Django REST framework) for the server-side work, and using PostgreSQL as the database. Is there any reason NOT to use this tech stack mentioned or are there better options? Without giving away too much info, my app will be logging information from the user, displaying this information, setting goals, displaying visual graphs, a friend system where you can add other people etc...

Hey everyone! I'm planning on building a personal project - this will be my first full-stack project and will be a web app.

The way it will work is that users will be able to post groups. This can be, groups for studying or groups for work, etc. They can also set the desired group size (e.g. limit the group to 3 members). Other users can then join said group - once the group is full, it will automatically close.

What tech stack would you all recommend for this? I have a lot of experience with Django so maybe that will be good for the backend but I'm not sure where to go from there. I've heard using the Django REST framework with a React frontend might be good. Always open to learning new technologies and thanks in advance!

Hey Everyone,

I am using the Django with Django REST framework for backend and API.. for front-end using React..

1. What will be the best way for deployment. Backend and front-end are at different domains or both at the same domain...
2. My app will be used concurrently by more than 1000 users. How will I achieve performance? Is there any suggestions...

Hi

I’ve been using Django for the last year on and off to do my backend API. I’m getting a bit frustrated with the Django REST framework with the setup of the serializers and Django for the lack of web sockets. I’m considering either Spring or .NET Core. I’m familiar with Kotlin and C# but I’ve not built any substantial projects with them. I like OOP, building a desktop app, web API, and also the potential to get a job in the future or building a tool at work to manage my documents, dashboard and processes point cloud data.

I’m familiar with c/cpp, TypeScript.

I would love your insights on where I should go.

Python's GraphQL version – Graphene – has some critical disadvantages, that we found critical: - Lack of code optimisation. It is also hard to write optimized code because of graphene node API. - Nonsecure by default. By using reversed fks, you can get a lot of extra data. To stop this, we have to explicit exclude wrong fields, which seems to be error prone. - Nonflexible code structure. You can't make abstract graphene.ObjectType class, this limits us a lot.

These are some reasons, that make us move to Django REST framework .