<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Otp on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/otp/</link>
    <description>Recent content in Otp on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/otp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cowboy vs MochiWeb vs Yaws in 2026: Which Erlang HTTP Server Should You Use?</title>
      <link>https://www.pistack.xyz/posts/2026-09-04-erlang-http-servers-cowboy-mochiweb-yaws-comparison/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-04-erlang-http-servers-cowboy-mochiweb-yaws-comparison/</guid>
      <description>&lt;p&gt;Your RabbitMQ management console, your Phoenix endpoints, and the STOMP bridge your message broker exposes all have one thing in common: an Erlang HTTP server underneath. Erlang/OTP&amp;rsquo;s battle-tested concurrency model makes it a favorite for telecom-grade, low-latency backends, and the HTTP layer you pick determines latency, memory footprint, and how much boilerplate your team writes. In 2026 the choice still comes down to three projects: &lt;strong&gt;Cowboy&lt;/strong&gt;, &lt;strong&gt;MochiWeb&lt;/strong&gt;, and &lt;strong&gt;Yaws&lt;/strong&gt;. They look interchangeable at a glance — all three speak HTTP/1.1 on the Beam — but they target completely different jobs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
