
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Wed, 15 Jul 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/frameworks/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/2026-07-15-knowledge-graph-tools-frameworks.en</guid>
    <title>A Map of Knowledge Graph Tools and Frameworks: What to Pick, When</title>
    <link>https://www.youngju.dev/blog/2026-07-15-knowledge-graph-tools-frameworks.en</link>
    <description>Graph databases, the RDF and ontology stack, and graph RAG frameworks have exploded over the last two years. Link lists are already abundant, so this post draws an honestly-opinionated map instead. For each category: what it is for, two or three representative tools, and a clear when-to-pick-what — embedded (Kùzu) vs server (Neo4j), formal OWL/RDF vs pragmatic property graph, a roll-your-own extraction pipeline vs Microsoft GraphRAG&#39;s batteries-included one. And the most important question: when NOT to use a graph at all, because plain vector RAG is enough. It closes the series with a small decision flow. Every tool here was verified to exist, and its maturity and positioning are represented honestly — including the fact that Kùzu was archived in 2025.</description>
    <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>tools</category><category>knowledge-graph</category><category>graph-rag</category><category>ontology</category><category>frameworks</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-07-15-knowledge-graph-tools-frameworks.ja</guid>
    <title>知識グラフのツール・フレームワーク地図 — 何を、いつ選ぶか</title>
    <link>https://www.youngju.dev/blog/2026-07-15-knowledge-graph-tools-frameworks.ja</link>
    <description>グラフデータベース、RDF・オントロジースタック、グラフRAGフレームワークは、この2年で爆発的に増えました。リンク集はもう十分にあるので、この記事は代わりに、正直に意見を込めた地図を描きます。カテゴリごとに、何のためのものか、代表的なツールを2〜3個、そして「いつ何を選ぶか」をはっきり述べます — 組み込み(Kùzu)vsサーバー(Neo4j)、形式的なOWL/RDF vs実用的なプロパティグラフ、自作の抽出パイプライン vs Microsoft GraphRAGのバッテリー同梱パイプライン。そして最も重要な問い: そもそもグラフを使うべきでないとき(ベクトルRAGで十分なとき)はいつか。小さな決定フローでシリーズを締めます。すべてのツールは実在を確認し、成熟度とポジショニングを誇張していません — Kùzuが2025年にアーカイブされた事実も含めて。</description>
    <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>tools</category><category>knowledge-graph</category><category>graph-rag</category><category>ontology</category><category>frameworks</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-07-15-knowledge-graph-tools-frameworks</guid>
    <title>지식 그래프 도구·프레임워크 지도 — 무엇을 언제 고르나</title>
    <link>https://www.youngju.dev/blog/2026-07-15-knowledge-graph-tools-frameworks</link>
    <description>그래프 데이터베이스, RDF·온톨로지 스택, 그래프 RAG 프레임워크는 지난 2년 사이 폭발적으로 늘었습니다. 링크 목록은 이미 많으니, 이 글은 대신 정직하게 의견을 담은 지도를 그립니다. 카테고리마다 무엇에 쓰는지, 대표 도구 두세 개, 그리고 &quot;언제 무엇을 고를지&quot;를 분명히 말합니다 — 임베디드(Kùzu) vs 서버(Neo4j), 형식 OWL/RDF vs 실용 프로퍼티 그래프, 직접 짜는 추출 파이프라인 vs Microsoft GraphRAG의 배터리 포함 파이프라인. 그리고 가장 중요한 질문: 애초에 그래프를 쓰지 말아야 할 때(벡터 RAG로 충분한 경우)는 언제인가. 작은 결정 흐름으로 시리즈를 닫습니다. 모든 도구는 실제로 존재하는지 확인했고, 성숙도와 포지셔닝을 부풀리지 않았습니다 — Kùzu가 2025년 아카이브된 사실까지 포함해서.</description>
    <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>tools</category><category>knowledge-graph</category><category>graph-rag</category><category>ontology</category><category>frameworks</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-07-15-knowledge-graph-tools-frameworks.zh</guid>
    <title>知识图谱工具与框架地图 — 什么时候该选什么</title>
    <link>https://www.youngju.dev/blog/2026-07-15-knowledge-graph-tools-frameworks.zh</link>
    <description>图数据库、RDF 与本体栈、图 RAG 框架，在过去两年里爆发式增长。链接清单已经太多，所以本文换一种做法，画一张带着诚实观点的地图。每个类别都讲清楚：拿它做什么、两三个代表性工具，以及「什么时候该选什么」— 嵌入式(Kùzu) vs 服务器(Neo4j)、形式化的 OWL/RDF vs 实用的属性图、自己搭的抽取流水线 vs Microsoft GraphRAG 那种自带电池的流水线。以及最重要的一个问题：什么时候压根就不该用图(向量 RAG 就够了的时候)。本文以一张小小的决策流程为整个系列收尾。所有工具都核实过确实存在，也没有夸大它们的成熟度与定位 — 包括 Kùzu 在 2025 年被归档这一事实。</description>
    <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>tools</category><category>knowledge-graph</category><category>graph-rag</category><category>ontology</category><category>frameworks</category>
  </item>

    </channel>
  </rss>
