Rails+React+GraphQL+Apollo: 2 years on
Tamara Temple
On a long-term, Rails and jQuery based legacy project decided to modernize it's API and front end code. A bit over 2 years it ago, the team decided to adopt the new technology of GraphQL, and use the also new Apollo Client, within a React-based client front end.
Two years on, we've learned a lot, made a lot of mistakes, and discovered better ways of working with the mix of platforms, languages, frameworks, and libraries.
This talk will describe the experiences to date, and where we are going in the future.
Learning Objectives & Outcomes:
What's worked well, and what hasn't worked well, on revamping a legacy code base with modern tools.
https://2019.tcdrupal.org/session/railsreactgraphqlapollo-2-years
On a long-term, Rails and jQuery based legacy project decided to modernize it's API and front end code. A bit over 2 years it ago, the team decided to adopt the new technology of GraphQL, and use the also new Apollo Client, within a React-based client front end.
Two years on, we've learned a lot, made a lot of mistakes, and discovered better ways of working with the mix of platforms, languages, frameworks, and libraries.
This talk will describe the experiences to date, and where we are going in the future.
Learning Objectives & Outcomes:
What's worked well, and what hasn't worked well, on revamping a legacy code base with modern tools.
https://2019.tcdrupal.org/session/railsreactgraphqlapollo-2-years