News for hackers. Stuff that matters.
Re:Neo4j nabs $80M Series E as graph database tech flourishes by johnymontana on Thursday November 01, 2018 @09:51AM (#18353842)
It's interesting that you mention GraphQL. For me, using Neo4j and GraphQL were similar experiences, in that once I started using them they offered a more intuitive and productive approach over the "standard" tools (RDBMS and REST, respectively).

Once I learned Cypher and some common graph data modeling constructs, I found I could build more complex applications faster using Neo4j, largely because I found the graph model of my project's domain more intuitive and easier to work with than a relational database model.

Similarly, building and using GraphQL APIs has been a huge productivity win once I figured out how to build GraphQL services.

Of course, when used together, Neo4j and GraphQL have some great synergies, since it's graph all the way down ;-)

It's also worth pointing out that Neo4j has some great GraphQL integrations [1].

[1] https://grandstack.io/docs/neo4j-graphql.html

Re:Neo4j nabs $80M Series E as graph database tech flourishes by jcims on Thursday November 01, 2018 @01:49PM (#18356540)
Oh man did I struggle with Cypher to start. Conceptually I felt like I understood it but 2/3rds of my queries would go out to lunch and never come back.

Lessons learned for me:

- start with very small datasets (mine was 10k nodes/40k edges/5 types and that still sent it to the moon in many cases)

- get to know the query planner right away

Cypher seems to reward a more deliberate and iterative approach to learning it rather than the ol' grip it and rip it. Once I settled down a bit it came together quite nicely.