What's the best SPA architecture for edge deploys?
Sam and Ryan talk about the architecture of Zeit's Next.js framework and the concept of edge deploys. They discuss the difference between data that must be fetched at runtime vs. data that can be cached, and how application developers might best express which parts of their apps can tolerate stale data.
Audio is streamed directly from the publisher (cdn.simplecast.com) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
Topics include:
- 6:00 - Exploring Next.js's architecture
- 22:33 - Is runtime SSR an antipattern?
- 44:04 - Are there any downsides to this architecture?
- 1:11:25 - React's single shot SSR vs. Ember's asynchronous FastBoot rendering
Links:
- [CAP theorem](https://en.wikipedia.org/wiki/CAP_theorem)
- [Tweet from Guillermo: "Most use cases of SSR are better served by SSG"](https://twitter.com/rauchg/status/1226353359759634432)