restQL-core VS join-monster

/network/shortestPath?node1=<>&node2=<>

to get a list of all devices but I'm basically just writing custom Cipher code to do that query and the benefits of Neo4J basically go out the door. It still has some interesting Graph features but if all i'm doing is writing a custom endpoint for every use case it's mainly pointless.

You can do a simple POST statement which takes a Neo4J query and execute it with some caching on top of it for sure.

Either ways in order to make Neo4J worth it I need a way to make the queries more dynamic. So right now I'm thinking of:

- restQL http://restql.b2w.io/

GraphQL could be efficiently translated into SQL and things certainly try, but the only thing close to a "bulletproof" implementation I found was Join Monster (https://github.com/join-monster/join-monster) in NodeJS-land and even that I think is now mostly abandoned. GraphQL as a system was built assuming random-access to data stores is ~free because that's what Facebook has, but the rest of us don't :)

REST is not a strict specification and it's not a single implementation, you can just start doing it.

That said, I wouldn't recommend going the allow everything flexible resolver way like GraphQL: it's terrible for performance (eg. most APIs use N+1 queries unless you have something like https://github.com/join-monster/join-monster), the complexity of the codebase skyrockets and having to specify all the fields you want is not exactly ergonomic in most situations.