<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Noah</title>
    <description>The latest articles on DEV Community by Noah (@noah_austin).</description>
    <link>https://dev.to/noah_austin</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4204679%2F7a762431-a2eb-4d9f-a8fb-70937df61655.png</url>
      <title>DEV Community: Noah</title>
      <link>https://dev.to/noah_austin</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/noah_austin"/>
    <language>en</language>
    <item>
      <title>NIO-Pulse</title>
      <dc:creator>Noah</dc:creator>
      <pubDate>Sat, 24 Oct 2026 12:48:50 +0000</pubDate>
      <link>https://dev.to/noah_austin/nio-pulse-11jp</link>
      <guid>https://dev.to/noah_austin/nio-pulse-11jp</guid>
      <description>&lt;p&gt;I wanted to understand how asynchronous, non-blocking I/O works under the hood of frameworks like Netty, so I built a lightweight HTTP/1.1 web server from scratch with zero external dependencies so I built NIO-Pulse.&lt;/p&gt;

&lt;p&gt;What is NIO-Pulse?&lt;/p&gt;

&lt;p&gt;Traditional web servers use a thread per connection architecture, which easily bottlenecks under heavy concurrent loads. NIO-Pulse uses an event-driven Selector architecture and a worker thread pool to manage thousands of concurrent connections efficiently.&lt;/p&gt;

&lt;p&gt;Check it out! 👇&lt;br&gt;
&lt;a href="https://github.com/clementezeusgabriel01-iswrtg/NIO-Pulse/tree/main" rel="noopener noreferrer"&gt;https://github.com/clementezeusgabriel01-iswrtg/NIO-Pulse/tree/main&lt;/a&gt;&lt;/p&gt;

</description>
      <category>java</category>
      <category>nio</category>
      <category>webdev</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
