TheSwingBetweenClientAndServer

In web-applications there's TheSwingBetween doing work on the client and the server.

When either becomes cluttered and full of cruft, and TechnicalDebt, the other

GraphQL was invented because creating lots of server-side end-points for rapidly evolving clients, was too heavy.

Better to have fewer, fixed end-points with more expressivity to cope with the churning demands from the client.

But this creates security risks as your server needs to expose more, possibly to hostile outsiders. The solution, move more back to the server ...

https://intercoolerjs.org/2016/02/17/api-churn-vs-security.html