this is fine but makes the backend extremely slow and hard to maintain. it's effectively just glorified RPC - restful api low logic on backend and lots of logi

this is fine but makes the backend extremely slow and hard to maintain. it's effectively just glorified RPC - restful api low logic on backend and lots of logic on front-end - grpc style as the author suggests, more logic on backend no logic on front-end - keep api restful on backend, add backend for front-end(graphql/rpc), front-end remains simple, most logic is in the middle. this also allows you to isolate presentation spaghetti code in one place, keeps your backend api clean for use for other clients worked in all 3 probably having a custom presentation layer works best but require more setup upfront. another advantage of having a restful api and have the front-end do more work is being able to incrementally load data into the UI therefore reducing TTI/TTFB