Using GDB with TinkerPop: Transaction Management and DAO Implementation

This article introduces the use of Alibaba Graph Database (GDB) as a storage backend in server‑side development, focusing on the pitfalls and best practices when integrating with the TinkerPop framework.

It first compares several popular graph databases (GDB, GraphCompute, TuGraph, Neo4j) in terms of query language, data loading, commercial support, and management features, highlighting that most support Gremlin and that GDB was chosen for its ACID transaction guarantees.

The author points out three main challenges when using GDB with TinkerPop: (1) complex string‑based script construction makes type inference difficult; (2) transaction handling is not documented in the official API; (3) some TinkerPop APIs (e.g., SessionedClient, tx) are incompatible with GDB, leading to errors such as Invalid OpProcessor requested .

To address these issues, the DAO layer is implemented in two ways. The first approach uses MyBatis‑style interfaces with script templates (omitted for brevity). The second approach builds Gremlin scripts manually via StringBuilder and submits them with GdbClient.submitAsync . Example code for inserting a vertex is shown below.

public String insert(DataDo dataDO) throws CoreSystemException {
    //Param Checker...
    StringBuilder sb = new StringBuilder();
    sb.append(String.format("g.addV('%s')", dataDO.getLabel()));
    for (String property : dataDO.getPropertyCreationParamList()) {
        sb.append(String.format(".property('%s', %s)", property, property));
    }
    sb.append(String.format(".property('propId', '%s')", id));
    sb.append(String.format(".property('creatorId', %d)", dataDO.getCreatorId()));
    sb.append(String.format(".property('area', %d)", dataDO.getArea()));
    String id = UUID.randomUUID().toString();
    sb.append(String.format(".property(id, '%s')", id));
    List
results = gdbClient.queryResultSync(sb.toString(), dataDO.getPropertyCreationParamMap());
    dataDO.setId(id);
    if (results.size() != 1) { return null; }
    return id;
}

The alternative DAO method uses Gremlin GraphTraversal to build a bytecode operation flow, which can later be submitted via the client. A representative traversal method is:

public GraphTraversal insertTraversal(DataDO dataDO, GraphTraversal traversal) {
    traversal = traversal.addV(dataDO.getLabel());
    for (String property : dataDO.getPropertyCreationParamList()) {
        traversal = traversal.property(property, dataDO.getPropertyCreationParamMap().get(property));
    }
    traversal = traversal.property("propId", id)
        .property("creatorId", dataDO.getCreatorId())
        .property("area", dataDO.getArea());
    String id = UUID.randomUUID().toString();
    dataDO.setId(id);
    traversal = traversal.property(T.id, id);
    return traversal; // not executed yet
}

For transaction handling, GDB does not expose the standard g.tx() API. Instead, the SDK provides open , commit , and rollback methods through GdbClient . A complete transaction example using bytecode is presented:

GdbClient.SessionedClient client = GdbCluster.build(host)
    .port(port)
    .credentials(user, password)
    .serializer(Serializers.GRAPHBINARY_V1D0)
    .create()
    .connect(UUID.randomUUID().toString())
    .init();
try {
    client.batchTransaction((tx, gtx) -> {
        List
personResult = tx.exec(gtx.addV("person").property("name", "John"), GQL_TIMEOUT);
        List
softwareResult = tx.exec(gtx.addV("software").property("name", "YYDS"), GQL_TIMEOUT);
        Vertex person = personResult.get(0).getVertex();
        Vertex software = softwareResult.get(0).getVertex();
        List
edgeResult = tx.exec(gtx.addE("create").from(gtx.V(person.id())).to(gtx.V(software.id())), GQL_TIMEOUT);
        log.info("Success create Record [{} -create-> {}]", "John", "YYDS");
    });
} finally {
    client.close();
}

The article concludes with a summary of the differences between GDB and standard TinkerPop usage, notes on transaction semantics, and a reminder that many GDB‑specific operations cannot be replaced by vanilla TinkerPop code. It also provides references for further reading and acknowledges the team behind the work.