Re: Architectural suggestions for (Django + API)

2015-08-17 Thread julio . lacerda
Hi Carl, > I don't quite understand why the situation you describe requires > duplicating models files. Is the canonical data storage now in Project B > instead of Project A, and Project A gets the data via Project B's REST > API? In that case, why does Project A need those models anymore?

Re: Architectural suggestions for (Django + API)

2015-08-17 Thread julio . lacerda
Hi James, I'm going to build a separated instance to provide only REST services to be consumed by Project A. It's ok to use the same views to provide a REST interface in API but in this case I need to remove models from project A, right? Thank you very much! Em domingo, 16 de agosto de 2015 2

Re: Architectural suggestions for (Django + API)

2015-08-16 Thread Carl Meyer
Hi Julio, On 08/16/2015 04:59 PM, julio.lace...@m2agro.com.br wrote: > 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 ord

Re: Architectural suggestions for (Django + API)

2015-08-16 Thread James Schneider
Are you adding REST functionality to an existing project? Or will you be using a separate instance to provide only REST services and maintain two different code bases? I believe you can use the django-rest-framework to utilize the same views (literally) to provide a REST interface, so you may not

Architectural suggestions for (Django + API)

2015-08-16 Thread julio . lacerda
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