Good question. Have you seen this already https://github.com/souenzzo/graph-demo ?

Listen, I have faced problems using the instructions on GitHub to make it work. Primary reason is that fulcro on GitHub is no longer fulcro3.git and also the SHA is different. I have tried to edit the .edn file to match the falcro.git on github but couldn't do it

If it is your repository and you can edit it to make it work, that would be great.

It's not my repo, but @U2J4FRT2T might be available to advise ^

@arto.eg unless you have a specific reason, don’t use github url as dependency for fulcro - you can just use the newest version from clojars:

com.fulcrologic/fulcro {:mvn/version "3.0.2"}

although my project is not yet used in production, it’s deployable to heroku/dokku - you can take a look on how I integrate fulcro with crux-jdbc https://github.com/roterski/syncrate-fulcro/blob/master/src/main/app/database/crux.clj

* it’s still wip so there’re some dirty parts for sure

Thanks for the advice @UHA0AQZ2M What I understand from your recommendation that the Fulcro version on Clojars is more of a stable version ready for production. Is that correct?

@UHA0AQZ2M I'd also be interested to know your overall feedback on Crux. What's your review after using it?

@arto.eg yes, https://github.com/souenzzo/graph-demo uses a fixed link to specific, dated commit - since then fulcro 3.0 has been released and it’s more stable with more fixes and tweaks

Neo4J and dGraph claim to have solved the data integrity problems. I wonder how true is that 🙂

This is great feedback, thanks for writing it up! We are certainly interested in how constraints and data integrity checks can be sensibly layered on top of Crux but we don't have any firm plans or advice just yet. Transaction functions are already implemented though (behind a flag!) so a lot of possibilities are already technically achievable as long as you are very careful not to break too much determinism when using eviction as well

@arto.eg interesting to hear about such claims by neo and dgraph. I would need to read about this in more detail before I could comment. Needless to say, everything gets a lot more complicated when you also have temporal axes to think about, oh and temporal integrity constraints are also a thing

I am not a lot into the technical aspects of these new technologies but I always wondered for example, what's the reason of the data integrity issue for MongoDB? Is the corruption happening during concurrent transactions on the network layer, or on the software level there are bugs when the tree/map is deep enough it cannot properly store the data. So unless I really know what causes the inconsistency, I might as well claim that PostgreSQL can have data inconsistencies if they are exposed to the same environment conditions.

I will bump graph-demo to fulcro3 with fulcro-inpect-native support next week

I do not use graph-demo in production, but it's the reference "template" for my production apps.

I do not forget about this my notebook is in technical support replacing some stuff I will do this when it come back

Working!