Lessons from Migrating a Legacy Frontend to Hotwire
Hotwire
Turbo
Stimulus
React Legacy Migration
Databases
Is Hotwire just for `rails new` scenarios and not worth it for mature applications? Absolutely not.
I share my learnings from leading a migration of Halalbooking.com, a large hotel booking website, from a mix of technologies centered on React to Hotwire.
Even though we couldn't enable Turbo Drive, we got a huge DX and performance boost from using other parts of Hotwire, making the migration more than worth it.
I’ll share specific examples and lessons learned along the way. You'll leave optimistic about introducing Hotwire to a mature codebase.
As a bonus, you’ll see:
- When it's beneficial
- How fast it pays back
- How to introduce it gradually
- Two concrete examples of complex Hotwire UIs
I share my learnings from leading a migration of Halalbooking.com, a large hotel booking website, from a mix of technologies centered on React to Hotwire.
Even though we couldn't enable Turbo Drive, we got a huge DX and performance boost from using other parts of Hotwire, making the migration more than worth it.
I’ll share specific examples and lessons learned along the way. You'll leave optimistic about introducing Hotwire to a mature codebase.
As a bonus, you’ll see:
- When it's beneficial
- How fast it pays back
- How to introduce it gradually
- Two concrete examples of complex Hotwire UIs
Sep 05 - 15:45 to 16:15
Track 2 - Graanbeurs
About the speaker
Radan Skoric
Lead Software Engineer
Full stack developer with over 17 years of professional experience solving problems with Software, mainly with Ruby and Rails. Author of "Master Hotwire" e-book. I split my time between coding the backend of (mostly complex) applications and leading and increasing efficiency of a team of developers. I am bullish on Hotwire approach.