dgraph-io / dgraph-io/dgraph

Support for ISO/IEC 39075:2024 (GQL) in Dgraph

Open
#9,362 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Stale
Dominant language
Go
Stars
21.8k
Forks
1.6k
Avg merge
2d 5h
Merged PRs (30d)
9

Description

Hi there,

I’ve been working a lot with graph data lately and tried out different solutions like Neo4j and Apache AGE for Postgres. Currently, I’m building a Go-based project to process large-scale graph data for mapping Dutch addresses. That’s how I came across Dgraph — I followed the quickstart guide and was impressed with the setup and performance.

One thing I noticed: mutations rely on RDF N-Quads (spec), while queries are done using GraphQL. It works fine in practice, but the split between input and query formats adds a bit of cognitive overhead when working at scale.

In my current role at a larger enterprise organization in the Netherlands, there’s a strong focus on aligning with international standards, especially ISO standards. With the recent publication of ISO/IEC 39075:2024 (Information technology — Database languages — GQL), I see a significant opportunity for Dgraph to appeal more directly to enterprise use cases. Supporting GQL could help adoption in organizations where ISO compliance, interoperability, and vendor neutrality are key decision factors.

I’m aware there have been some discussions in the Dgraph community about GQL support. For example, in a forum thread from April 2024, a team member mentioned being aware of GQL and noted that community priorities would play a big role in whether it gets implemented.

Just wondering if there are any plans to explore ISO GQL support more concretely — and if it might be considered for the roadmap?

Thanks for all your work on Dgraph — it’s a great project and I’m excited to see where it goes.


Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing Dgraph’s existing query and mutation interfaces, then read the linked community discussion about GQL support. The issue does not name implementation files, tests, or a defined compatibility scope; done would require an agreed roadmap and implementation plan for ISO/IEC 39075:2024 support.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.