3 ms·
I think having a separate repo for the frontend and backend is important. It is the same separation I want for my Android and iOS code. If they were mixed with
by cyberpanther 12y ago
I think having a separate repo for the frontend and backend is important. It is the same separation I want for my Android and iOS code. If they were mixed with the backend it becomes messy. So the frontend is just another client like other platforms.
- X-Cubed 12y agoThe idea here is that the frontend as rendered on the client is the same as the frontend rendered on the server. This isn't about putting the API and service code in with the UI.
- Romoku 12y agoI think isomorphic JavaScript applications are going to replace the current frontend paradigm. Microservices are becoming more popular, so imagine an isomorphic JavaScript application as a frontend consumer of many backend microservices. Plus there are a slew of security considerations that cannot be solved with current frontend JavaScript. For instance, how do I call a protected API without leaking the API credentials to the consumer? Currently you can do this with trusted hardware or the traditional server side rendering. An isomorphic JavaScript application can solve this problem using server side rendering without needing a separate backend.
- cnp 12y agoThis is precisely what we're moving towards right now. It allows us to break away from our current, sub-optimal backend server serving up all the services to an isomorphic JS app that consumes variety and spits back out results from API calls. It allows for great flexibility -- not to mention speed and consistency.