ArangoDB java-driver reuse of objects

Question

In many of the examples using the java arangoDB driver, they use method chaining

arangoDB.db("myDatabase").createCollection("myCollection", null);

or

arangoDB.db("myDatabase").collection("myCollection").insertDocument(myObject);

Are there any drawbacks with re-using objects?

ArangoDatabase db = arangoDB.db("myDatabase");
...
db.createCollection("myCollection", null);
ArangoCollection coll = db.collection("myCollection");
...
coll.insertDocument(myObject);

I am not sure if chaining approach is preferred or just for simplicity (fewer lines for an example).

Is there much of a performance benefit to reuse? Less object creation overhead...
Are connection, database and collection objects thread safe? i.e after getting a database can the object be shared between multiple threads?

mpv89 · Accepted Answer · 2017-10-05 09:04:41Z

2

Yes, you can reuse instances of ArangoDatabase, ArangoCollection, ArangoGraph, ArangoVertexCollection, ArangoEdgeCollection.

Yes, there is a small performance benefit through less object creation.
Yes, all of them are thread-safe. You can share them between threads.

answered Oct 5, 2017 at 9:04

mpv89

1,89111 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

ArangoDB java-driver reuse of objects

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related