Dgraph client libraries allow you to run DQL transactions, queries and mutations in various programming languages.
If you are interested in clients for GraphQL endpoint, please refer to GraphQL clients section.
It’s possible to interface with Dgraph directly via gRPC or HTTP. However, if a client library exists for your language, that will be an easier option.
*grpc.ClientConnper Dgraph instance, or routing traffic through a load balancer. Mutations will be made in a round robin fashion, resulting in a semi-random initial predicate distribution.
Dgraph clients perform mutations and queries using transactions. A transaction bounds a sequence of queries and mutations that are committed by Dgraph as a single unit: that is, on commit, either all the changes are accepted by Dgraph or none are.
A transaction always sees the database state at the moment it began, plus any changes it makes — changes from concurrent transactions aren’t visible.
On commit, Dgraph will abort a transaction, rather than committing changes, when a conflicting, concurrently running transaction has already been committed. Two transactions conflict when both transactions:
- write values to the same scalar predicate of the same node (e.g both
attempting to set a particular node’s
- write to a singular
uidpredicate of the same node (changes to
[uid]predicates can be concurrently written); or
- write a value that conflicts on an index for a predicate with
@upsertset in the schema (see upserts).
When a transaction is aborted, all its changes are discarded. Transactions can be manually aborted.