Architectural suggestions for (Django + API)

Hey guys,

I have a question about an architectural issue and I would like to hear some suggestions about it.

I created a project using Django (let's call this Project A) and now I decided to start a new one but this time it is an API using Django REST. So, for now I have to refactor Project A to consume data from API, but in order to do that I need to duplicate all my models files in both projects. The question is how can I avoid this? Is there another way to do that?

I see that moving models from Project A to API as something natural but to have an empty models file in Project A I need to change some concepts, for removing ModelForms and put all validation logic using Form.

How do you guys see this? Would you recommend something different? Is that a good idea?

1. Project A (Models) <---> API (same models??? How can I handle that?)
2. Project A (No models) <---> API (Models)
   

Thanks in advance!

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/11d2f88e-a159-4e7b-903f-80d0f6e8e74a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.