by kolev on 9/10/15, 11:29 PM with 21 comments
by eranation on 9/11/15, 3:07 AM
Can I treat GraphQL as going toward being a "better tinker pop"? If not than what are the use cases for GraphQL in the context of existing graph databases?
by vimes656 on 9/11/15, 1:49 PM
I'm not implying that the bindings should have been used. I'm now considering writing a implementation of GraphQL in Haskell and I'm trying to assess whether it's worth using the Facebook C bindings or it's better to implement the whole protocol from scratch.
by Ciantic on 9/11/15, 7:30 AM
One reason is that you have to have a schema defined for database already e.g. using Slick, it should be reusable for GraphQL schema as is. Having same schema defined several times is pain.
by graffitici on 9/11/15, 8:21 AM
by morenoh149 on 9/11/15, 4:25 AM