<?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>Swoole on Murat Useinov</title>
    <link>https://useinov.com/tags/swoole/</link>
    <description>Recent content in Swoole on Murat Useinov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 05 May 2021 22:20:00 +0300</lastBuildDate>
    <atom:link href="https://useinov.com/tags/swoole/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Octane and state that outlives the request</title>
      <link>https://useinov.com/posts/2021/octane-shared-state/</link>
      <pubDate>Wed, 05 May 2021 22:20:00 +0300</pubDate>
      <guid>https://useinov.com/posts/2021/octane-shared-state/</guid>
      <description>&lt;p&gt;One customer sees another customer&amp;rsquo;s cart. No crash, no error in the log. That is the bug Laravel Octane brings to an old codebase, and the benchmarks are the least interesting part of the story.&lt;/p&gt;
&lt;p&gt;Octane is out in beta, Swoole and RoadRunner became first-class overnight. In FPM every request gets a fresh application. Boot, handle, die. The model forgives everything. Under Octane the framework boots once and workers reuse it. Bootstrap cost drops to near zero, hence the pretty numbers. But every singleton is now shared between requests, and between users.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
