<?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/bbe613c041c14ef3b4747d1ee01c0e48&quot; frameborder=&quot;0&quot; width=&quot;854&quot; height=&quot;640&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>640</height><width>854</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>640</thumbnail_height><thumbnail_width>854</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/bbe613c041c14ef3b4747d1ee01c0e48-38654d67ba38fd39.gif</thumbnail_url><duration>150.444</duration><title>Federated Search at Enterprise Scale</title><description>In this video, I share my experience tackling the complexities of a federated search system within a large enterprise platform that serves over 100 million users across 50 websites. The challenge was not just to build features but to deeply understand the existing architecture, which involved revisiting the fundamentals of Apache Lucene, Solr, and Fusion. I reverse-engineered the platform, documented my findings, and designed a federated architecture that scales to 150 sites while reducing human bottlenecks. This ongoing project empowers Drupal admins to control federation logic without direct interaction with the search platform, ultimately saving costs. I encourage you to consider the importance of clarity in system design as we move forward.</description></oembed>