re: Coupling of front end and backend VIEW POST


Personally, I like more and recommend to decouple the Frontend from the API. This let you update them individually so you can change your frontend without redeploying your API or improve the API without re-building your Frontend.

On the other side, coupling them and using template based view can give you a faster start when coding a project and if you're a FullStack dev with more Backend background you can just go this way and eventually split them if the Frontend grows in complexity (or you get a Frontend dev to work with you).

Also for simple projects like a CRUD admin for a little company or similar project without too many frontend stuffs aside of CSS (and maybe using Bootstrap or similars) the coupled approach is more than enough because in that case you most probably have everything already done for you and doesn't make sense to use something like React, Angular, Vue, etc. and decouple the Frontend.

code of conduct - report abuse