The Web Semantic

“show the latest ….” is a common prefix to user stories these days.  Others have noted the same and given this symptom a moniker; ”The real time web“.  Typically we just throw things into a table with an indexed timestamp column and query accordingly.

In jo4neo, finding the most recent additions requires two simple steps:

1. annotation your type with @neo(recency=true)
2. use the ObjectGraph.getMostRecent() method to retrieve the latest inserts.

In this small example, we’re indicating to jo4neo that we’d like it to remember our “Post” inserts in most recent order. » Read the rest of this entry «

Graphs in and of themselves are not self indexing like relational databases, however, you can construct indexes via strong relationships between the nodes of interest.  The pattern I’ll be discussing in this post maps time (year, month, day, hour) into a graph format as nodes and edges.  Once time, or some subset, is represented as a graph we can then associate events or moment intervals as nodes related to a particular hour of a particular day, month and year.  ( This post is based on a full example here.) » Read the rest of this entry «

neoblog is a simple application I built to test drive jo4neo.  You are welcome to browse the code here for details not covered in this post. It demonstrates the feasibility of utilizing view tier objects to persist graph relationships.

neoblog with 3 posts

» Read the rest of this entry «

Roles and Users is a classic domain model well suited to representation as a directed graph. The neo4j team has provided us with a good summary of how to implement this pattern using neo4j here . Utilizing jo4neo we can also solve this problem via a combination of the neo graph database and simple java objects.  The code and maven build for this example are posted here.  I encourage you to run the example and browse the code.  We’ll need two domain classes, » Read the rest of this entry «