Migrating a Rails & React SPA to Remix by Diogo Biazus
Maintaining a stack with multiple programming languages can drastically increase the cognitive load of a team.
Unifying the frontend and the backend under a single language has always been a tantalizing prospect.
With Remix this becomes an achievable goal, however, migrating without a big rewrite is always challenging, while migrating with a big rewrite is often disastrous.
This is the story of how we are planning a migration feature by feature, using an integrated authentication system that works on both our Rails backend and on the Remix server. We also disastrous leveraged resource routes to proxy the old application and integrate everything under the same domain, making the back and forth between legacy and rewritten features seamless.
Speaker bio: Diogo Biazus has been a software developer since the late 90s.
Since then, he has also worked as an open-source contributor, conference organizer, PostgreSQL instructor and consultant, systems integrator (yay, EDI!), "the DevOps guy", and team lead.
He has contributed to PostgREST (https://github.com/PostgREST/postgrest) and published PostgreSQL tools such as postgres-websockets (https://github.com/diogob/postgres-we..., postgres-copy (https://github.com/diogob/postgres-copy), and hasql-notifications (https://github.com/diogob/hasql-notif.... He now focuses on improving DX at Seasoned.
Diogo Biazus' GitHub: https://github.com/diogob
Repo: https://github.com/SeasonedSoftware/r...