~/talk

Rails+React+GraphQL+Apollo: 2 years on

Talkat Twin Cities Drupal Camp 2019 · 2019-06-06..06-08· [ruby-on-rails, react]
links:none on file
slides:none on file

A legacy Rails+jQuery app moves toward a React front end and a GraphQL API implemented with GraphQL Ruby, and the team spends two years swapping approaches. Apollo Client works well in production—Apollo Client caching reduces payloads—and GraphQL simplifies precise data fetching, but starting with the massive job-details page fails: too many tiny interactions and mixed jQuery/React lead to bugs and slow progress. The team pivots to incremental React components rendered via Rails and tighter repo conventions; refactoring and documentation finally make on‑boarding and maintenance feasible.

AI-written summary · about

  1. 0:00Introduction and context
  2. 5:32Initial strategy (2017)
  3. 8:46Lessons and obstacles
  4. 15:00New strategy (2019)
  5. 17:22Technological reflections
  6. 22:51Refactoring and improvement
  7. 29:48Q&A and closing
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.