3 ms·
The same argument could be used for splitting backend to multiple services, or even micro services. Frontend/backend separation seems pretty arbitrary. If anyt
by vbezhenar 3y ago
The same argument could be used for splitting backend to multiple services, or even micro services. Frontend/backend separation seems pretty arbitrary.
If anything, I'd say that with server rendering, separating different modules is easier. You want to rewrite that page? No problems. With client-side rendering there's usually expectation of some monolith project using the single framework.
- jwells89 3y ago> If anything, I'd say that with server rendering, separating different modules is easier. You want to rewrite that page? No problems. It also gets you vastly more choice in language/tooling/etc, even allowing a mixture of different ones, which is what attracts me to SSR. Of course this may change in the future once WebAssembly has had most of the DOM interop overhead optimized away, bringing this freedom to CSR.
- edanm 3y agoFrontend-backend separation isn't arbitrary at all. A few things that are often different between FE and BE: 1. Written in different languages. 2. Completely different deployment paths. 3. Causing completely different ways of scaling. 4. Focus on UI and UX is a very different mindset, with often some people preferring it to be a focus of their work, or not.
- azmarks 3y agoYou can (and probably will) have multiple different frontends with website vs app. If you have a clean API for the backend, then you have one set of calls which can be made from multiple different user interfaces