3 ms·
That's currently what I do. Also Django is useful for sketching your requirements out, then once you know what you're building you can move the real-time data r
by adamauckland 13y ago
That's currently what I do. Also Django is useful for sketching your requirements out, then once you know what you're building you can move the real-time data retrieval into NodeJS and let Django handle the boring stuff.
Not EVERYTHING in an app will need to be real-time. Especially boring maintenance functionality such as password reset etc.
- RussianCow 13y agoTrue, but for such basic things, you could just use something lightweight like Flask and not have to deal with all of Django's baggage. It all depends on the app, though. In my case, even "boring" stuff often needed to make HTTP requests to the outside world, so Django would never have scaled for me. (In hindsight, I should have just written the whole thing in Node, but it wasn't as mature back then and I didn't want to take the risk.)