base on high-performance graph database for real-time use cases <picture> <source srcset="/logo-dark.png" media="(prefers-color-scheme: dark)" /> <source srcset="/logo.png" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" /> <img alt="Dgraph Logo" src="/logo.png"> </picture> [](https://github.com/dgraph-io/dgraph/stargazers) [](https://github.com/dgraph-io/dgraph/commits/main/) [](https://goreportcard.com/report/github.com/dgraph-io/dgraph) Dgraph is a horizontally scalable and distributed GraphQL database with a graph backend. It provides ACID transactions, consistent replication, and linearizable reads. It's built from the ground up to perform a rich set of queries. Being a native GraphQL database, it tightly controls how the data is arranged on disk to optimize for query performance and throughput, reducing disk seeks and network calls in a cluster. Dgraph's goal is to provide Google production-level scale and throughput, with low enough latency to serve real-time user queries over terabytes of structured data. Dgraph supports [GraphQL query syntax](https://docs.dgraph.io/graphql), and responds in [JSON](http://www.json.org/) and [Protocol Buffers](https://developers.google.com/protocol-buffers/) over [GRPC](http://www.grpc.io/) and HTTP. Dgraph is written using the Go Programming Language. ## Status Dgraph is at [version v25][rel] and is production-ready. Apart from the vast open source community, it is being used in production at multiple Fortune 500 companies, and by [Intuit Katlas](https://github.com/intuit/katlas) and [VMware Purser](https://github.com/vmware/purser). [rel]: https://github.com/dgraph-io/dgraph/releases/tag/v25.0.0 ## Supported Platforms Dgraph officially supports the Linux/amd64 and Linux/arm64 architectures. In order to take advantage of memory performance gains and other architecture-specific advancements in Linux, we dropped official support for Mac and Windows in 2021, see [this blog post](https://discuss.dgraph.io/t/dropping-support-for-windows-and-mac/12913) for more information. You can still build and use Dgraph on other platforms (for live or bulk loading for instance), but support for platforms other than Linux/amd64 and Linux/arm64 is not available. Running Dgraph in a Docker environment is the recommended testing and deployment method. ## Install with Docker If you're using Docker, you can use the [official Dgraph image](https://hub.docker.com/r/dgraph/dgraph/). ```bash docker pull dgraph/dgraph:latest ``` For more information on a variety Docker deployment methods including Docker Compose and Kubernetes, see the [docs](https://docs.dgraph.io/installation/). ## Run a Quick Standalone Cluster ```bash docker run -it -p 8080:8080 -p 9080:9080 -v ~/dgraph:/dgraph dgraph/standalone:latest ``` ## Install from Source If you want to install from source, install Go 1.24+ or later and the following dependencies: ### Ubuntu ```bash sudo apt-get update sudo apt-get install build-essential ``` ### Build and Install Then clone the Dgraph repository and use `make install` to install the Dgraph binary in the directory named by the GOBIN environment variable, which defaults to $GOPATH/bin or $HOME/go/bin if the GOPATH environment variable is not set. ```bash git clone https://github.com/dgraph-io/dgraph.git cd dgraph make install ``` ## Get Started **To get started with Dgraph, follow:** - [Installation to queries in 4 quick steps](https://docs.dgraph.io/quick-start). - Tutorial and presentation videos on [YouTube channel](https://www.youtube.com/playlist?list=PLzOEKEHv-5e3u2Tgv52O2rs5u3md58JON). ## Is Dgraph the right choice for me? - Do you have more than 10 SQL tables connected via foreign keys? - Do you have sparse data, which doesn't elegantly fit into SQL tables? - Do you want a simple and flexible schema, which is readable and maintainable over time? - Do you care about speed and performance at scale? If the answers to the above are YES, then Dgraph would be a great fit for your application. Dgraph provides NoSQL like scalability while providing SQL like transactions and the ability to select, filter, and aggregate data points. It combines that with distributed joins, traversals, and graph operations, which makes it easy to build applications with it. ## Dgraph compared to other graph DBs | Features | Dgraph | Neo4j | Janus Graph | | ----------------------------------- | ----------------------------- | -------------------------------------------------------- | ------------------------------------- | | Architecture | Sharded and Distributed | Single server (+ replicas in enterprise) | Layer on top of other distributed DBs | | Replication | Consistent | None in community edition (only available in enterprise) | Via underlying DB | | Data movement for shard rebalancing | Automatic | Not applicable (all data lies on each server) | Via underlying DB | | Language | GraphQL inspired | Cypher | Gremlin | | Protocols | Grpc / HTTP + JSON / RDF | Bolt + Cypher | Websocket / HTTP | | Transactions | Distributed ACID transactions | Single server ACID transactions | Not typically ACID | | Full-Text Search | Native support | Native support | Via External Indexing System | | Regular Expressions | Native support | Native support | Via External Indexing System | | Geo Search | Native support | External support only | Via External Indexing System | | License | Apache 2.0 | GPL v3 | Apache 2.0 | ## Users - **Dgraph official documentation is present at [docs.dgraph.io](https://docs.dgraph.io).** - For general information and questions, visit [Github discussions](https://github.com/dgraph-io/dgraph/discussions). - Please see [releases tab](https://github.com/dgraph-io/dgraph/releases) to find the latest release and corresponding release notes. ## Developers Please see [Contributing to Dgraph](https://github.com/dgraph-io/dgraph/blob/main/CONTRIBUTING.md) for guidelines on contributions. ## Client Libraries The Dgraph team maintains several [officially supported client libraries](https://docs.dgraph.io/clients/). There are also libraries contributed by the community [unofficial client libraries](https://docs.dgraph.io/clients/unofficial-clients). ## ## Contact - Please use [Github discussions](https://github.com/dgraph-io/dgraph/discussions) for questions, feature requests and discussions. - Please use [GitHub Issues](https://github.com/dgraph-io/dgraph/issues) for filing bugs or feature requests. ", Assign "at most 3 tags" to the expected json: {"id":"8536","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"