# A Journey from Monolith to Micro frontends at Udemy -- Part 1 of 3

DevFeed: [A Journey from Monolith to Micro frontends at Udemy -- Part 1 of 3](<https://devfeed.tech/articles/a-journey-from-monolith-to-micro-frontends-at-udemy-part-1-of-3-26357.md>)

Original publisher: [Read original article](<https://medium.com/udemy-engineering/transforming-frontend-architecture-a-journey-from-monolith-to-micro-frontends-at-udemy-part-1-e0a9c19c47bf?source=rss----19c6d3367ed4---4>)

Author: Hamza ERBAY

Published: 2024-01-02T18:47:48Z

Content type: article

Language: en

Sources: [Udemy Engineering](<https://devfeed.tech/sources/udemy-engineering.md>)

Topics: [Front end](<https://devfeed.tech/topics/frontend.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [development](<https://devfeed.tech/tags/development.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [innovation](<https://devfeed.tech/tags/innovation.md>), [modular](<https://devfeed.tech/tags/modular.md>), [monolithic-architecture](<https://devfeed.tech/tags/monolithic-architecture.md>), [performance](<https://devfeed.tech/tags/performance.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>)

## AI overview

Udemy describes its migration from a monolithic frontend architecture toward micro frontends. The article explains that scaling created bottlenecks in development speed, release processes, CDN use, and user experience, motivating a more modular and scalable architecture.

## Source excerpt

Transforming Frontend Architecture: A Journey from Monolith to Micro Frontends at Udemy -- Part 1 of 3 By: Chris Nienhuis, Hamza Erbay, Matthew Bise, Nathan Chapman, Seth Hodgson, Trey Briggs, Charles Pham Photo by Annie Spratt on UnsplashIntroduction At Udemy, we have over 67M learners and over 75K instructors, and we're working on a fast and accessible experience for them. Our underlying application architecture is a monolith -- a single, unified codebase that houses our marketplace, consumer subscription services, and business applications. The engine that powers our global platform is constantly being improved by our dedicated teams working to enhance the learning and teaching experience. In the spirit of innovation, we pitched an idea at the 2021 hackathon to decouple frontend engineering from the monolithic structure. The concept resonated with the hackathon committee (Shark Tank Council), earning a decisive nod. Thus began our odyssey toward a more modular, resilient, and scalable frontend architecture. Motivation to migrate monolith to micro frontend At the heart of our decision to migrate from a monolithic architecture to micro frontends was the need to address critical pain points impeding our ability to scale and innovate effectively. Development Speed and Scalability Our monolithic application served us well in the early days, but as we scaled, it became a double-edged sword. Development speed slowed to a crawl due to two main bottlenecks: When you start a new project, the build process takes approximately 10-15 mins. Cold Start (blue and orange), Warm Start (only orange boxes)Complex Release Process Deploying our code was a difficult and time-consuming process. Any changes to the code had to go through a slow and tedious cycle of review, approval, and queuing, which often took several days, especially during release freezes. This slow process was not sustainable for a growing global team generating many experiments. The release process can take days.In 20