Re: Front End and Back End separation

2016-02-11 Thread Dheerendra Rathor
For validation, I tend to write very lousy validations in JS. Serializers handle most of the validations in BE itself. If you want to depend on JSON, then you can write JSON schema validation in BE and use the same schema validation in JS. We tend to write BE such that it remains compatible with F

Re: Front End and Back End separation

2016-02-11 Thread Radek Svarz
Thanks for supporting my gut feeling :) - ad validation - do you somehow propagate the validation rules to the FE app? Or do you need to rewrite some of them in JS? - ad app versioning - how do you give the impulse towards FE app that it needs to reload itself in order to be compatib

Re: Front End and Back End separation

2016-02-10 Thread Dheerendra Rathor
If you don't want FE guys to touch your Python code, I will suggest to go with option 1. DRF is a great library and creating REST API is dead simple. Data validation is pretty easy in DRF using serializers. I tend to write my own authorization methods with DRF but they are also easy. It is just plu

Front End and Back End separation

2016-02-10 Thread Radek Svarz
Hi, I am deciding about the new architecture of the Django business app. The web frontend app constists of 1 highly interactive part - visual editor (using D3js) and several configuration pages. I am strong in the Django backend part, but outsourcing the JS front end to the freelancer.com guys