{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/b80ac0825e3f4804ab519c2c6ca52d42\" frameborder=\"0\" width=\"1154\" height=\"865\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":865,"width":1154,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":865,"thumbnail_width":1154,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/b80ac0825e3f4804ab519c2c6ca52d42-a3f066e5262c3e0c.gif","duration":40.3808,"title":"Multi-Worker Wrangler dev (single instance!)","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!"}