re: Any NoSQL true believers out there? VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Hmmm, I read about the graph DBs... but how does it solve our problem? I see the problem as an aggregate root of Track (de-normalized all in one m...

Neo4j allows you to have entities, quite similar to what a row in a table is. The key difference, subjectively, is flexibility to declare relationships between these entities in an easier manner than in a relational database. Aggregates can be easily created using their query language, Cypher, which isn't too hard and too different from SQL.

Yet again, if read speeds are critical and you can live without immediate consistency, then a key value or a document database would do the job perfectly.

Thanks for the elaboration, very appreciated !

Surely, we will discuss that with the team to see how things go... guess we are probably gonna use Neo (or any other suitable graphdb) with the profile model as well.

code of conduct - report abuse