<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gremlin on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/gremlin/</link>
    <description>Recent content in Gremlin on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 04 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/gremlin/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Graph Query Engines: Apache TinkerPop vs Apache Jena vs Eclipse RDF4J</title>
      <link>https://www.pistack.xyz/posts/2026-06-04-apache-tinkerpop-jena-rdf4j-self-hosted-graph-query-engines-guide/</link>
      <pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-04-apache-tinkerpop-jena-rdf4j-self-hosted-graph-query-engines-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Graph data is everywhere — social networks, recommendation systems, knowledge graphs, and supply chain mapping all rely on graph structures to model complex relationships. While graph databases like Neo4j and Dgraph handle storage and indexing, &lt;strong&gt;graph query engines&lt;/strong&gt; define how you traverse, query, and analyze those relationships. The query engine you choose shapes your entire data model: property graphs with Gremlin traversals versus RDF triple stores with SPARQL queries.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
