I exaggerate here because graphql does not solve the datalake problem. And it doesn’t do graphs (you can). The curb appeal looked super promising, but then it was just rpc with a bespoke ORM syntax.
I don’t mean to exaggerate, but your code will tend to mirror your organization structure. I have worked at companies where I thought our product was great because the API rocked.
Then in my last 3 months I got to meet the frontend (definitely a jobsmell: not seeing the frontend every day.)
Definitely misjudged the quality of our product, because apparently we wrote two different products (shrug) ;)
Pretty strong argument for htmx, actually. But again, in a weird way where we fire the frontend and become actual full-stack engineers for everrrrything.
https://max.engineer/server-informed-ui