Refactoring to a Single Page Application
summary
Describes migrating a legacy monolithic web frontend (HTML, CSS, JavaScript served from a single-language stack like Java or Rails) into a Single Page Application. Covers progressive extraction of frontend code and practical techniques for incrementally converting parts of the UI into an SPA, drawing on experience from Workshare.
AI-written summary · about
chapters (28)
- 0:00Refactoring intro
- 1:14MPA versus SPA
- 3:21Refactoring definition
- 4:04Business context
- 7:00First monolith: Circus
- 9:50SPA evolution plan
- 10:11Spike: Supernova
- 11:57First microservice: Bruxelles
- 13:22Backend transformation
- 14:04Embracing JavaScript
- 15:54Results and takeaways
- 16:15JavaScript build
- 19:10Frontend dependencies
- 20:57SPA app structure
- 22:02App layout
- 24:30Authentication handling
- 25:56Strategic iframe use
- 28:26Legacy app integration
- 30:10Testing and maintenance
- 31:56Deployment and coexistence
- 34:06CSS in hybrid apps
- 35:08Current state and future
- 36:15Designer involvement
- 37:19Performance issues and fixes
- 37:59Existing small SPAs
- 38:41Browser support and SEO
- 40:56Team collaboration
- 42:22Q&A
related talks
41mMigrating from Monolithic to Future-Proof MFs
32mFrom Monolith to Micro Frontend
24mA Frameworkless Approach to Building Your Single Page Application
24mScaling Frontend Development using Micro-frontends
22mBreak Up With Your Frontend Monolith
25mMicro Frontend: a microservice architecture from your frontend web apps
23mRefactoring for Progressive Web Apps
28mMaking Single Page Apps accessible
