Know your data – why we use
Oracle Property Graph for
data modeling and more
Do you know your data?
Being aware of the lack of explicit joins between tables, we started looking at implicit joins in JOIN conditions of queries in an application. So there we have it: we know the tables and their joins – who else wants to draw the model? We do. And we choose Oracle Property Graph to do it. If you’re not familiar with property graphs, let’s take a quick look at the basics.
From graph databases and property graphs
Property graphs consist of nodes (the entities of the graph, also known as vertices) and edges (the connections between nodes). Both nodes and edges can have multiple properties (attributes), which are represented as key/value pairs. This means that the structure of a graph does not need to be predefined, as you can simply add new key/value pairs when more attributes are needed.
Although there is no standardized notation for property graphs, both drawing and reading them is quite easy – even for non-technical users. In addition – and this is the exciting part – there are a number of graph algorithms for solving problems such as shortest path, cycle detection, clustering and many, many more.
Why Oracle Property Graph?
Last but not least, PGQL, Oracle’s query language for property graphs, is based on SQL, so it is quite easy to learn for users with SQL background.
This might also interest you:
BMBF funding project for digital software documentation – Interview with Andreas Gaede