The Neo4j Server uses HTTP APIs as well, as you just send a query that is executed within the server and returns data the protocol doesn't matter so much.
Depends on your use-cases if that performance is enough for your SLAs or not. There is also the embedded option and we'll be working on a binary remoting protocol too. Michael > Am 24.04.2015 um 16:02 schrieb Mustafa Duman <[email protected]>: > > > Hello, > > I wonder about your thoughts and experiences on hosting neo4j in production > environment. > > For GrapheneDb, the idea of making http calls for DB access sounds bad for me > for performance. What do you think? > > What do you think about self-hosting? > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Neo4j" 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.
