Hi Tom, Using the Go driver you get a Go interface to the database. The driver handles all the details of the HTTP interface so you don't have to care about those details. - Performance: it will not give you more performance that the HTTP API because the driver uses the HTTP API itself. - Async: The driver is fully synchronous but support (in all but Cursor) requests from concurrent Go-routines. - context package: The driver is using the context package for all functions. Using that you can cancel requests, set timeouts etc. The driver also uses WithXyz functions to configure less frequently used settings of the API. (Note you can always pass nil for the context parameter) - Cluster behavior: The driver will take care of cluster detection & failover for you. Again this is something you can build yourself but it is rather tricky to get it right. - New protocols: ArangoDB supports a binary protocol (Velocypack). The Go driver will support this protocol in a future release. Using the driver interface it will be a configuration switch to start using this protocol. - Fully tested: The Go driver comes with a large set of unit tests to make sure the mapping between Go & ArangoDB works as expected.
Hope this helps. Regards Ewout Op zaterdag 8 april 2017 16:22:42 UTC+2 schreef Tom Glod: > > Hi everyone, > > I'm wondering if anyone could shed light on the performance considerations > of using the golang driver for arrangodb vs using the http api? > > I know which one is easier to implement, but what advantages does using > the driver have over http? is it more performant? by alot? is it still > async? > > any words of wisdom would be appreciated. Thanks > > Tom > -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
