4 ms·
My biggest issue is that SPAs have a lot of overhead for your typical CRUD. The canonical example: a CRUD page with a dropdown of choices based on entitlement.
by silviogutierrez 10y ago
My biggest issue is that SPAs have a lot of overhead for your typical CRUD.
The canonical example: a CRUD page with a dropdown of choices based on entitlement.
Server rendered: in your template somewhere, {for choice in limited_choices} and so on.
SPA: you need to coordinate a REST endpoint that has options for entitlement of just this dropdown, etc. You now need a route for REST, a route for the SPA page, and view code for both.
Don't get me wrong, with unlimited time, build everything as REST services with a client that consumes it. But sometimes server-side rendering is just simpler.
- nojvek 10y agoSPA shines if you are building lots of CRUD. Rest end points are simpler and simply mush data out of the db. No templating crap. It's a lot faster to load template once and re-render on client with different data.