GraphQL kinda sucks | Hacker News

The author of this post argues that GraphQL is over-hyped and not suitable for all use cases. While it has its benefits such as easy data description, reduced bandwidth usage, and simple documentation for data consumers, it also has significant drawbacks like the need to manage multiple type systems if no code-first generators are available in a language, lack of map/table/dictionary support, and unclear path for API versioning. The author advises against using GraphQL unless you’re managing a solution intended for it by Facebook, and instead suggests exploring simpler solutions first.