Re:Django Community Survey
by rattray on Friday May 08, 2015 @08:57AM
(#9511331)
I'm in the planning phase of porting a large C# application's frontend to React on Node (for isomorphism).
Basically we'll have our main application server (in this case, .net mvc api, but think django-rest-framework) talk to a node server as well as the client, with the same REST api. The plus is very real separation of concerns (django does all data handling, business logic; javascript does all UI). The downside is having two server stacks.
FWIW, I'm planning to use nuclear-js[1] for flux. And we're considering porting our .net code to django.
Basically we'll have our main application server (in this case, .net mvc api, but think django-rest-framework) talk to a node server as well as the client, with the same REST api. The plus is very real separation of concerns (django does all data handling, business logic; javascript does all UI). The downside is having two server stacks.
FWIW, I'm planning to use nuclear-js[1] for flux. And we're considering porting our .net code to django.
[1] https://github.com/optimizely/nuclear-js