Jack Linke 🦄<p>Talk me out of building a <a href="https://social.jacklinke.com/tags/Neo4j" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Neo4j</span></a> implementation in parallel to my existing <a href="https://social.jacklinke.com/tags/PostgreSQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PostgreSQL</span></a> DB (with a subset of tables as nodes) for queries that tend to be "graph-like" in nature.</p><p>In particular, I'm thinking of failure analysis, predictive maintenance, etc in relation to physical infrastructure I model as a directed acyclic graph.</p><p>Is this just my <a href="https://social.jacklinke.com/tags/ADHD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ADHD</span></a> wanting to try something new, or could I actually find value in this side-quest? 😬</p><p><a href="https://social.jacklinke.com/tags/Modeling" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Modeling</span></a> <a href="https://social.jacklinke.com/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareEngineering</span></a> <a href="https://social.jacklinke.com/tags/Database" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Database</span></a> <a href="https://social.jacklinke.com/tags/Graphs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Graphs</span></a> <a href="https://social.jacklinke.com/tags/Django" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Django</span></a> <a href="https://social.jacklinke.com/tags/UhOh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UhOh</span></a></p>