Please log in to watch this conference skillscast.
Every model is motivated by a need; every model is constrained by its mode of representation. For decades our industry has favoured the directed graph as a means of expressing its modelling flights of fancy. We're surrounded by graphs: object graphs, entity-relationship diagrams--even our circle-and-lines whiteboard sketches. Why then do we surrender our graph competence at the last moment, when it comes to making our model durable? What mischief interrupts the path from thought to deed? In this session I'll discuss why and when we might consider applying a graph all the way down the stack, from whiteboard to persistent storage. I'll show how we encode our model's needs in the graph, and how a graph database helps fulfill the needs that motivate the model.
YOU MAY ALSO LIKE: