3 ms·

We'd do it in Django. Just kidding. I don't know, that's a pretty hypothetical question. We've heard nice stories about people who split up their frontend an

We'd do it in Django. Just kidding. I don't know, that's a pretty hypothetical question. We've heard nice stories about people who split up their frontend and backend into two projects, one completely Angular/Grunt, one completely Rails, where the Rails serves solely as a RESTful API and even user sign in and access checking is done through a remote service. It still sounds like a cool concept, but I'd want to have time to play around with it as a smaller experiment before really investing on a design like that. It would be a big shift in thinking, and again I don't know if it would make our lives easier or harder in the long run.

craigching 13y ago
> where the Rails serves solely as a RESTful API Honestly I can't imagine not doing that, why wouldn't you? I'm not trolling, making the backend RESTful and interacting with it only via REST calls is a great way to separate your data from your user interface. You can base mobile on this, web, or even legacy applications and reuse your backend service. So if you didn't do that, what model did you follow? I'll admit, I've flagged this post to read the article later, so if it's addressed in the article, I can read it there.