GraphQL kinda sucks

Article summary

The article discusses the potential downsides of using GraphQL, including the complexity of managing multiple type systems, lack of support for maps and dictionaries, and difficulties with API versioning. The author argues that GraphQL is often overhyped and that its benefits may not outweigh its drawbacks for many use cases. The article also mentions that some developers may be misled into using GraphQL without fully understanding its limitations. The author suggests that simpler solutions, such as traditional APIs, may be more suitable for many projects.

Main themes

• GraphQL limitations
• API design
• versioning
• microservices
• technology choice
• complexity vs simplicity
• bandwidth usage
• schema stitching

What commenters say

• GraphQL's complexity and limitations make it a poor choice for many projects.
• Traditional APIs can be just as effective as GraphQL without the added complexity.
• API versioning is a necessary feature that GraphQL lacks.
• The benefits of GraphQL, such as reduced bandwidth usage, can be achieved through other means.
• GraphQL's schema stitching can be a major headache in microservices environments.
• The choice of technology should be driven by the needs of the project, rather than by the desire to use a particular technology.
• Some developers may be overly invested in GraphQL and downplay its limitations.
• Simpler solutions, such as server-side rendering, can be more effective and efficient than complex APIs.