<?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/c631bb6b0b304244a1ab1f2bd6895531&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c631bb6b0b304244a1ab1f2bd6895531-e49bce59f1a15bea.gif</thumbnail_url><duration>334.835</duration><title>End-to-End Proof of Concept for Traces Exporter Implementation 🚀</title><description>In this video, I walk through the proof of concept (POC) I&apos;ve been working on, focusing on the implementation of the TracesExporter that sends traces to the HotelCollector for processing. I&apos;ve developed a custom plugin called HotelArrow that converts JSON schema into arrow format, which is then exported to our backend and stored in a database. I demonstrate the flow using a simple app that sends traces upon button clicks, and I show the resulting data in the database, including span and parent IDs. There are considerations regarding the scalability and development speed of our approach, and I invite viewers to think about whether we want a single collector or separate components for better flexibility. Please share your thoughts on this decision as we move forward.</description></oembed>