devFC

Am I wrong for thinking GraphQL is how builds APIs today?

GraphQL as core (anyone can select just the data they need)
Then some default queries offered via one call as REST endpoints (just a wrapper over the GraphQL)

and then for typesafety and production use on the client side combine GraphQL with effect to get end to end typesafety and return type validation in something like

What am I missing / where does this go wrong? trying to open my mind on GraphQL

Am I wrong for thinking GraphQL is how builds APIs today?

GraphQL as core (anyone can select just the data they need)
Then some default queries offered via one call as REST endpoints (just a wrapper over the GraphQL)

and then for typesafety and production use on the client side combine GraphQL with effect to get end to end typesafety and return type validation in something like

What am I missing / where does this go wrong? trying to open my mind on GraphQL

https://gist.github.com/tim-smart/e10e4cbaeff35242d8352adead30bef9

Farcaster Product Studio @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

GraphQL also has many downsides that usually appear on a large scale. Often, the way to go on a large scale is rest api microservices.

But on a very small scale, like when creating a full-stack app that you fully own, GraphQL also adds some unnecessary complexity.