Skip to first unread message
Andrey Devyatkin
Oct 31, 2016, 3:58:23 AM10/31/16
to Eiffel Community
Hi!
At the last summit, I mentioned that colleague of mine Sofus did a prototype of Eiffel <-> Neo4j bridge
you can find source code here
and here is a short demonstration https://www.youtube.com/watch?v=O0iUIVOFcX8
BR, Andrey
Daniel Ståhl
Nov 1, 2016, 3:33:23 AM11/1/16
to Eiffel Community
Thanks for sharing, Andrey!
One reflection on persistence (not related to Andrey's post per se) is to keep it dumb. As is so often the case, it's easy to get into a mode where you add more and more bells and whistles to cater to first one specific use case, then another.
You get a very, very long way by addressing only the following:
- Give me any object matching a specific pattern (typically an id, but you can do e.g. generic JPath queries)
- Optionally, also include anything upstream from any matches, along any of a specified list of link types (e.g. COMPOSITION and ARTIFACT).
- Optionally, also include anything downstream from any matches, along any of a specified list of link types (e.g. CAUSE).
Then you can build all kinds of sophisticated services on top of that very simple foundation.
One reflection on persistence (not related to Andrey's post per se) is to keep it dumb. As is so often the case, it's easy to get into a mode where you add more and more bells and whistles to cater to first one specific use case, then another.
You get a very, very long way by addressing only the following:
- Give me any object matching a specific pattern (typically an id, but you can do e.g. generic JPath queries)
- Optionally, also include anything upstream from any matches, along any of a specified list of link types (e.g. COMPOSITION and ARTIFACT).
- Optionally, also include anything downstream from any matches, along any of a specified list of link types (e.g. CAUSE).
Then you can build all kinds of sophisticated services on top of that very simple foundation.
Reply all
Reply to author
Forward
0 new messages