Migrating from an Isomorphic App to a Static Site Generator: the revolut.com Case Study
summary
A case study of Revolut’s migration from an isomorphic (server/client-rendered) web app to a static site generator. Covers reasons for the migration, the concrete problems encountered during the move, the solutions applied, and the results achieved.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 10:36Isomorphic apps pros and cons
- 22:39Gatsby beta dev
- 24:27Localization and routing
- 34:09Performance issues and fixes
- 42:52Optimizations for large projects
- 54:11Dynamic content with Nginx
- 1:00:16Summary and Q&A
related talks
43mHow We Implemented Decoupled Drupal as Static for a Bank
10mHow to migrate 50,000 lines of code to React Server Components
15mMigrating Notion’s marketing site to Next.js
10mGradual Migration Strategies for Next.js
20mIncremental Static Regeneration: Static sites on steroids
17mReact Off the Grid
20mLarge Scale Projects Challenges (NextJS - Contentful)
19mNavigating the web in a world full of constraints