# Migrating Strava's My Routes Page to a React Microfrontend

DevFeed: [Migrating Strava's My Routes Page to a React Microfrontend](<https://devfeed.tech/articles/searching-for-success-at-strava-26577.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/searching-for-success-at-strava-22b9bf205dbf?source=rss----89d4108ce2a3---4>)

Author: Navika Budhraja

Published: 2022-11-15T17:01:28Z

Content type: article

Language: en

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

Topics: [React](<https://devfeed.tech/topics/react.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Ruby on Rails](<https://devfeed.tech/topics/ruby-on-rails.md>), [monorepo](<https://devfeed.tech/topics/monorepo.md>)

Tags: [frontend](<https://devfeed.tech/tags/frontend.md>), [micro-frontends](<https://devfeed.tech/tags/micro-frontends.md>), [react](<https://devfeed.tech/tags/react.md>), [search](<https://devfeed.tech/tags/search.md>)

## AI overview

A Strava web-frontend intern describes migrating the My Routes page from the Active Ruby on Rails monolith to a React microfrontend, then adding filtering and search for athletes' saved routes.

## Source excerpt

Me and my mentors Patrick & NomnomsIntroduction Hi, my name is Navika Budhraja and I'm a rising senior at UC San Diego studying Computer Science. This summer I was a web-frontend engineering intern on the Athlete Services team and consequently, got to learn a lot about how to develop athlete-facing products! During my internship, I worked with 3 other interns, Emily (Server), Sahil (iOS), and Ryan(Android), on a project to add filtering and searching logic to athlete's saved routes, which in my case, meant working on the My Routes page on the web. "Old" My Routes that I would be improving Like the paths of many Strava routes, adding this feature on the web was not going to be a straightforward process. As you may already know, Strava is currently in the process of moving code out of their Ruby on Rails monolith called Active to React-based frontends. Since the code for the current My Routes page lives in active, I was also tasked with migrating the page from active to a React microfrontend before adding filtering/search logic. 😱...My Face exactly when I first read my project description, especially with super rusty React skills and no conception of what a microfrontend was (was it like a tiny frontend or like a craft, hipster frontend sort of like a microbrew?). However, what I came to learn is that when you work in an incredibly supportive and encouraging environment, the process of rolling out a requested feature in just 12 weeks with no experience isn't actually as daunting as it sounds. In the spirit of the Warriors winning the championship earlier this summer (Yes, I am still riding the high), I will break down these past 12 weeks in terms of quarters of a basketball game! First Quarter: Onboarding & Jams Although I wanted to jump in and start working on a project right away, I first had to get acclimated to a new code base, actually 2 new code bases: active (the monolith) and web (the monorepo where my microfrontend will live). By fixing some minor bugs on the w