Cherished ideas about what GraphQL is and how it should be implemented may have to give way to a changing reality.

The New Stack is a publication covering trends and technologies in cloud-native development, DevOps, and software delivery. Developers can learn about containerization, Kubernetes, and cloud computing, as well as explore topics such as microservices architecture, serverless computing, and continuous integration/continuous delivery (CI/CD) pipelines.

The New Stack

GraphQL, developed by Facebook and open-sourced in 2015, has gained popularity for its flexible and efficient data query capabilities. However, its growth is now hindered by security, performance, and complexity issues. To ensure its future viability, the community may need to rethink how GraphQL is defined and implemented, leveraging it as a development tool and considering compiler-based implementations to overcome its current challenges.

Is GraphQL Over or Do We Just Need to Rethink It?

Coming from a graph database perspective, it’s still the most seamless and most natural extension for interacting with nodes and relationships.
In particular, Neo4j’s GraphQL library on top of their query language is fairly clean and transports notions of the database’ whiteboard-friendliness.
This is what GraphQL is made for.
(Performance and security issues aside, which definitely need to be tackled!)