<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HugeGraph Architecture Overview on Apache HugeGraph</title><link>https://hugegraph.apache.org/docs/guides/architectural/</link><description>Recent content in HugeGraph Architecture Overview on Apache HugeGraph</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 02 Nov 2026 21:54:08 +0800</lastBuildDate><atom:link href="https://hugegraph.apache.org/docs/guides/architectural/index.xml" rel="self" type="application/rss+xml"/><item><title>HugeGraph Plugin mechanism and plug-in extension process</title><link>https://hugegraph.apache.org/docs/guides/architectural/custom-plugin/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hugegraph.apache.org/docs/guides/architectural/custom-plugin/</guid><description>&lt;p&gt;For plugins targeting the planned 1.8.0 shared-foundation API, follow the&#10;&lt;a href="https://hugegraph.apache.org/docs/guides/shared-foundation-migration/"&gt;Java/SPI migration guide&lt;/a&gt; and recompile against matching artifacts.&#10;The examples below describe the 1.7.0 API.&lt;/p&gt;&#10;&lt;h3 id="background"&gt;Background&#10;&lt;/h3&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;HugeGraph is not only open source and open, but also simple and easy to use. General users can easily add plug-in extension functions without changing the source code.&lt;/li&gt;&#10;&lt;li&gt;HugeGraph supports a variety of built-in storage backends, and also allows users to extend custom backends without changing the existing source code.&lt;/li&gt;&#10;&lt;li&gt;HugeGraph supports full-text search. The full-text search function involves word segmentation in various languages. Currently, there are 7 built-in word&#10;breakers (ansj, hanlp, smartcn, jieba, jcseg, mmseg4j, ikanalyzer), and it also allows users to expand custom word breakers without changing the existing source code.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;h3 id="scalable-dimension"&gt;Scalable dimension&#10;&lt;/h3&gt;&#10;&lt;p&gt;Currently, the plug-in method provides extensions in the following dimensions:&lt;/p&gt;</description></item><item><title>HugeGraph Design Concepts</title><link>https://hugegraph.apache.org/docs/guides/architectural/desgin-concept/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hugegraph.apache.org/docs/guides/architectural/desgin-concept/</guid><description>&lt;h3 id="1-property-graph"&gt;1. Property Graph&#10;&lt;/h3&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;Version note&lt;/strong&gt;: This page retains early design material. The property graph model and vertex ID strategies remain consistent with current master, but figures, partitioning conclusions, and transaction descriptions have the scope stated in each section. They are not current deployment or storage implementation guarantees.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;There are two common graph data representation models, namely the RDF (Resource Description Framework) model and the Property Graph (Property Graph) model.&#10;Both RDF and Property Graph are the most basic and well-known graph representation modes, and both can represent entity-relationship modeling of various graphs.&#10;RDF is a W3C standard, while Property Graph is an industry standard and is widely supported by graph database vendors. HugeGraph currently uses Property Graph.&lt;/p&gt;</description></item></channel></rss>