←back to thread

320 points benocodes | 2 comments | | HN request time: 0.506s | source
Show context
CharlieDigital ◴[] No.41896683[source]
Very interesting choice of using Cypher[0]

In 2014, we built a similar type event-driven system (but specifically for document distribution (a document can be distributed to a target set of entities; if a new entity is added, we need to resolve which distributions match)) and also ended up using Cypher via Neo4j (because of the complex taxonomical structure of how we mapped entities).

It is a super underrated query language and while most of the queries could also be translated to relational SQL, Cypher's linear construction using WITH clauses is far, far easier to reason about, IMO.

EDIT: feel like the devs went overboard with the mix of languages. Shoehorned in C# Blazor? Using JS and Jest for e2e testing?

[0] https://drasi.io/reference/query-language/

replies(3): >>41896809 #>>41896856 #>>41896904 #
robertlagrant ◴[] No.41896904[source]
We made a health backend partly using Cypher and the only thing I found was the simple queries looked amazing, but as soon as you need to join non-linearly it started looking a lot like SQL again. And when you're using an ORM it stops mattering. And when you need migrations it gets painful!
replies(2): >>41896929 #>>41896952 #
1. UltraSane ◴[] No.41896952[source]
"you need to join non-linearly "

What does this mean?

replies(1): >>41906248 #
2. FromOmelas ◴[] No.41906248[source]
presumably it has a semantic model of sorts, defining intrinsic relationships between entities (parent-child, composed-of, sibling-of, and so on)

A bit similar how certain joins in SQL can be very straightforward with the "USING" clause, or when it can rely on extra information such as analytic views to derive materialized views (vendor specific)