<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Websockets on Murat Useinov</title>
    <link>https://useinov.com/tags/websockets/</link>
    <description>Recent content in Websockets on Murat Useinov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 03 Jul 2024 23:10:00 +0300</lastBuildDate>
    <atom:link href="https://useinov.com/tags/websockets/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WebSockets change your operational model</title>
      <link>https://useinov.com/posts/2024/reverb-operations/</link>
      <pubDate>Wed, 03 Jul 2024 23:10:00 +0300</pubDate>
      <guid>https://useinov.com/posts/2024/reverb-operations/</guid>
      <description>&lt;p&gt;Every client reconnects at once. That is what a deploy means now on one project of mine, since Reverb made WebSockets a first-party Laravel feature this spring and order updates go to the browser instead of polling. The code was the easy part.&lt;/p&gt;
&lt;p&gt;A classic PHP app is stateless between requests. An FPM worker takes a request, answers, forgets. Capacity planning is requests per second. A WebSocket server is the opposite animal: thousands of open connections that mostly do nothing, but each one holds memory and a file descriptor, and each one is state that dies with the process. Your quiet realtime feature has a thundering herd built in. Plan for reconnect storms, raise descriptor limits, and make the client reconnect with jitter, never on a fixed timer.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
