<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>WebAssembly Component Model on Thorsten Hans</title>
    <link>https://thorsten-hans.com/tags/webassembly-component-model/</link>
    <description>Recent content in WebAssembly Component Model on Thorsten Hans</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 14 Aug 2026 19:15:00 +0200</lastBuildDate>
    <atom:link href="https://thorsten-hans.com/tags/webassembly-component-model/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Component Composition with Spin 4.0</title>
      <link>https://thorsten-hans.com/component-composition-with-spin-4/</link>
      <pubDate>Fri, 14 Aug 2026 19:15:00 +0200</pubDate>
      <guid>https://thorsten-hans.com/component-composition-with-spin-4/</guid>
      <description>&lt;p&gt;Thanks to the WebAssembly Component Model we can stitch together multiple WebAssembly Components. Reusing Wasm Components boost developer velocity dramatically while language barriers vanish. In this hands-on article, I&amp;rsquo;ll explain how you can compose Wasm Components using Spin 4.0.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-you-need-to-follow-along&#34;&gt;What You Need To Follow Along&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ll try to keep things as simple as possible. That&amp;rsquo;s why we&amp;rsquo;ll implement both components using Rust, resulting in the following - short - list of requirements:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
