lundi 2 mars 2015

Should I implement Enterprise Web based apps without backend only REST?


I keep seeing conversations about frontend driven application and using a frontend with REST API directly.


For me, the "cover all cases" architecture is:



  • REST API - allow users to use your data too

  • Backend - UI custom stuff. like session - write encrypted cookies that are not available from frontend

  • Frontend - can talk to Backend and REST.


And so usually there would be a team writing REST API in the company, and the UI team would write backend+frontend.


However, lately the need of a backend on top of REST has become game changing due to CORS, websockets and such.


I am still sticking to having a backend - but I can't say if there's a real need for it or if I am only doing it because it is "safer".


Regarding problematic issues here are the solutions:



  • SEO - we can resolve this in nginx. However SEO is not our concern. no need for server side HTML rendering

  • Session - lets assume I can keep a token in the frontend


Is there a feature that will require me to have a backend rather than a REST API or can I just delete my backend and start maintaining frontend alone?





Aucun commentaire:

Enregistrer un commentaire