<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/b80ac0825e3f4804ab519c2c6ca52d42&quot; frameborder=&quot;0&quot; width=&quot;1154&quot; height=&quot;865&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>865</height><width>1154</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>865</thumbnail_height><thumbnail_width>1154</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b80ac0825e3f4804ab519c2c6ca52d42-a3f066e5262c3e0c.gif</thumbnail_url><duration>40.3808</duration><title>Multi-Worker Wrangler dev (single instance!)</title><description>In this video, I demonstrate how Worker A is connected to Worker B through a service binding, enhancing the response from Worker B with a prefixed string. The traditional need for two Wrangler instances is eliminated, showcasing the simultaneous operation of both workers using a single Wrangler instance. I discuss the current use of multiple config files and hint at the potential future streamlining with a project config file. Watch to grasp the efficiency of service binding in Wrangler!</description></oembed>