<?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/58cc8100c67144fc98389e633761a2fe&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/58cc8100c67144fc98389e633761a2fe-b3eb268c359db6b6.gif</thumbnail_url><duration>170.362</duration><title>Transitioning to Microservices in E-Endorsement</title><description>In this video, I share my experience as a web developer working on the E-Endorsement project, a review management application. I discuss the challenges I faced while migrating the legacy monolithic architecture to a microservice architecture, including the need for asynchronous communication and database distribution. I also reflect on the valuable lessons I learned from my project manager, Michael, about creating scalable applications. Please let me know if you have any questions or need further clarification on the migration process.</description></oembed>