Isomorphic React sans Node??
summary
Eventbrite integrates React with a Python/Django backend by running a small stateless render server that accepts a component path and props and returns HTML using React’s renderToString. Development uses on‑demand transpilation via babel register, restarts to avoid module cache, and yarn deduping to shrink node_modules from about 1 GB to a few hundred MB. One server round trip per page, colocated with Django, proves faster than the old handlebars piebars approach and now powers checkout, event creation beta, and login flows in production.
AI-written summary · about
chapters (31)
- 0:00Intro
- 0:54What isomorphic React
- 1:41Isomorphic vs Universal
- 2:45Warm up
- 3:59Bens introduction
- 5:19Why isomorphic
- 6:33Initial render
- 7:26Django and Python
- 7:51PieBars
- 8:55Developers
- 9:25Switching to Node
- 10:37The gamble
- 11:10The decision
- 11:30Stateless render server
- 12:21Sample React component
- 12:41Sample curl request
- 13:31Express server
- 15:27Node server
- 15:44Django props
- 16:42Django scaffolding
- 17:20Network overhead
- 19:00Pitfalls
- 19:43On Demand Translation
- 20:42On Demand Transformation
- 21:11Node Caches
- 22:22Node Register Hook
- 23:18Long Polling
- 24:54Node Module Size
- 26:11Getting to Production
- 27:46Hypernova
- 29:00Shoutouts
