[ANNOUNCEMENT] New OrientDB Driver!

133 views
Skip to first unread message

philip.we...@gmail.com

unread,
Apr 27, 2015, 4:34:44 PM4/27/15
to orient-...@googlegroups.com
Hello All,

I have uploaded the OrientDB driver I have been working on to Github. It targets the OrientDB 2.0 Binary Protocol with Binary Serialization and aims to be a production-grade driver with a C API that makes life easier for non-Java users of OrientDB. I'd love to hear any comments that people have, and I'd love for more people to join me in developing this driver so that it becomes a community effort!

Sincerely,
Philip Wernersbach

Luca Garulli

unread,
Apr 27, 2015, 6:35:51 PM4/27/15
to orient-...@googlegroups.com
Hi Philip,
Well done!

Best Regards,

Luca Garulli
CEO at Orient Technologies LTD
the Company behind OrientDB


--

---
You received this message because you are subscribed to the Google Groups "OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orient-databa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Simon Gemmell

unread,
Apr 28, 2015, 7:38:05 AM4/28/15
to orient-...@googlegroups.com
Horray! As a native C++ developer I welcome all C based APIs! nim also looks pretty awesome - do you use it to serve as REST (or otherwise) frontend for orient? 

Philip Wernersbach

unread,
Apr 29, 2015, 3:23:43 PM4/29/15
to simong...@gmail.com, orient-...@googlegroups.com
Simon,

Thanks for the kind words. If you have any time, I'd love to get some more contributors on this, no matter how small the contribution. I agree that Nim is awesome, I chose to write this in Nim because it has a lot of functionality that makes it easier and safer to write these kinds of things. For example, when the code unpacks raw socket data into a variant data object, it sets the variant's type and then stores the data in the object. If someone forgot to set the variant's type before storing the data, it would be a compile time error because the compiler can't prove that the variant is the correct type for the data being stored. C would happily let you do this even though it is unsafe.

As far as what my company is using this for, we take the data straight from the database and use it in our web application which uses the jester library, no intermediate REST or HTTP involved. Our web application can be configured to use either an SQL database or OrientDB. Right now we use the SQL database configuration, but as OrientDB gets more stable we hope to transition to the OrientDB configuration.

Sincerely,
Philip Wernersbach

--

---
You received this message because you are subscribed to a topic in the Google Groups "OrientDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orient-database/tiXA7LaPuEw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orient-databa...@googlegroups.com.

Philip Wernersbach

unread,
Apr 29, 2015, 3:27:37 PM4/29/15
to simong...@gmail.com, orient-...@googlegroups.com
I'll also add that I think this has a lot of potential for the OrientDB community, as it could serve as the base library for other languages' OrientDB libraries via C interfacing in those languages (looking at you, Ruby!) 
Reply all
Reply to author
Forward
0 new messages