DEV Community

loading...

Discussion on: Front-End VS Back-End Web Development

Collapse
elmuerte profile image
Michiel Hendriks

This is a really oversimplification of what the backend does. In the classic (not old or outdated, because it is still valid) backend did all the lifting of processing input and presentation. It served static HTML and processed the input.
This really has not changed with the modern backend which comes with a companion frontend. Instead of serving HTML, the backend now has to server JSON, XML, or whatever format is deemed important. It still needs to fully process input, which is not JSON, multipart/form-encoded, XML, ... whatever. Still before authorization checks, which are also performed the modern frontend code. This is besides the algorithms, storage, etc. the backend has to perform.
Modern frontend does not really take away any responsibility from the backed. It just places responsibility at two ends.

So why this modern frontend stuff? It enables better UX, that's all. It increases complexity, but potentially improve performance. But in the end, it can* enable a better user experience.

*) "can" as your 25MiB compressed javascript frontend for a simple TODO application probably won't.

Collapse
lanrewaju profile image
Lanre Fagbeyiro Author

Thanks for sharing

Collapse
jasterix profile image
Jasterix

I get how this article might be simplifying the concepts for someone unfamiliar with the topic. But if you're a new dev, this is a great overview of how to start thinking about frontend and backend

Collapse
lanrewaju profile image
Lanre Fagbeyiro Author

Yea