
  <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>Sat, 16 May 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/hopsworks/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-feature-stores-feast-tecton-hopsworks-databricks-feldera-bytewax-materialize-2026-deep-dive.en</guid>
    <title>Feature Stores 2026 Deep Dive — Feast, Tecton, Hopsworks, Databricks, Vertex AI, SageMaker, Featureform, Bytewax, Materialize, RisingWave, Fennel, Chalk</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-feature-stores-feast-tecton-hopsworks-databricks-feldera-bytewax-materialize-2026-deep-dive.en</link>
    <description>A no-marketing tour of the 2026 feature store landscape: Feast (CNCF sandbox), Tecton (with the Eppo merger), Hopsworks, Vertex AI Feature Store, SageMaker Feature Store, Databricks Feature Engineering in Unity Catalog, Featureform, the streaming feature engines (Bytewax, Feldera, Materialize, ksqlDB, RisingWave), the transactional newcomers (Fennel — now inside Stripe — and Chalk), and the honest 2026 debate: do most teams actually need a separate feature store, or is dbt + warehouse + Redis enough? Online/offline split, point-in-time correctness, streaming freshness, embeddings convergence, and Korea/Japan adoption.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>feature-store</category><category>feast</category><category>tecton</category><category>hopsworks</category><category>databricks</category><category>bytewax</category><category>materialize</category><category>streaming</category><category>mlops</category><category>lakehouse</category><category>flink</category><category>redis</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-feature-stores-feast-tecton-hopsworks-databricks-feldera-bytewax-materialize-2026-deep-dive.ja</guid>
    <title>Feature Store 2026 完全ガイド - Feast・Tecton・Hopsworks・Databricks・Vertex AI・SageMaker・Featureform・Bytewax・Materialize・RisingWave・Fennel・Chalk 徹底比較</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-feature-stores-feast-tecton-hopsworks-databricks-feldera-bytewax-materialize-2026-deep-dive.ja</link>
    <description>2026年5月時点のフィーチャーストア市場を本気で整理する。Feast(CNCF サンドボックス)、Tecton(Eppo 一部資産統合)、Hopsworks、Vertex AI Feature Store、SageMaker Feature Store、Databricks Feature Engineering in Unity Catalog、Featureform、ストリーミング基盤の Bytewax/Feldera/Materialize/ksqlDB/RisingWave、決済領域に強い Fennel(Stripe 買収)と Chalk、そして「そもそも別物のフィーチャーストアは要るのか? dbt + ウェアハウス + Redis キャッシュで十分では?」という 2026 年の本音論争まで。オンライン/オフライン分離、ポイントインタイム整合性、ストリーミング鮮度、埋め込みとの収束、韓国・日本の導入事例まで一気通貫で扱う。</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>feature-store</category><category>feast</category><category>tecton</category><category>hopsworks</category><category>databricks</category><category>bytewax</category><category>materialize</category><category>streaming</category><category>mlops</category><category>lakehouse</category><category>flink</category><category>redis</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-feature-stores-feast-tecton-hopsworks-databricks-feldera-bytewax-materialize-2026-deep-dive</guid>
    <title>피처 스토어 2026 완벽 가이드 - Feast · Tecton · Hopsworks · Databricks · Vertex AI · SageMaker · Featureform · Bytewax · Materialize · RisingWave · Fennel · Chalk 심층 분석</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-feature-stores-feast-tecton-hopsworks-databricks-feldera-bytewax-materialize-2026-deep-dive</link>
    <description>2026년 5월 기준 피처 스토어 시장을 끝까지 본다. Feast(CNCF 샌드박스), Tecton(Eppo 인수 통합), Hopsworks, Vertex AI Feature Store, SageMaker Feature Store, Databricks Feature Engineering in Unity Catalog, Featureform, Bytewax/Feldera/Materialize/ksqlDB/RisingWave 같은 스트리밍 피처 엔진, Fennel(Stripe 인수)·Chalk의 트랜잭셔널 피처 스토어, 그리고 &quot;정말 피처 스토어가 필요한가? dbt + 웨어하우스 + Redis 캐시면 충분한가?&quot;라는 2026년의 진짜 논쟁까지. 온라인/오프라인 스토어 분리, 포인트인타임 정합성, 스트리밍 신선도, 임베딩 통합, 한국·일본 도입 사례까지 한 글에서 정직하게 정리한다.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>feature-store</category><category>feast</category><category>tecton</category><category>hopsworks</category><category>databricks</category><category>bytewax</category><category>materialize</category><category>streaming</category><category>mlops</category><category>lakehouse</category><category>flink</category><category>redis</category>
  </item>

    </channel>
  </rss>
