Artwork

Frontend First, Sam Selikoff, and Ryan Toronto에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Frontend First, Sam Selikoff, and Ryan Toronto 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.
Player FM -팟 캐스트 앱
Player FM 앱으로 오프라인으로 전환하세요!

Can you self-host Next.js?

58:03
 
공유
 

Manage episode 444554316 series 1635850
Frontend First, Sam Selikoff, and Ryan Toronto에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Frontend First, Sam Selikoff, and Ryan Toronto 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.

Sam and Ryan talk about how frameworks and infrastructure evolve with each other, using Next.js as a representative example. They discuss how hosting providers like Heroku have always imposed certain constraints on apps, what features those constraints enable hosting providers to support, how burdensome those constraints are across different frameworks, and how frameworks that add infra-specific APIs can best communicate the costs of those APIs and benefits they enable.

Timestamps:

  • 0:00 - Intro
  • 3:03 - Heroku and the Twelve-Factor App
  • 7:39 - GitHub Pages and static sites
  • 13:57 - Serverless and JAMstack
  • 17:30 - Vercel and CDNs, self-hosting, and Next.js
  • 19:00 - How framework APIs can nudge an app towards a particular hosting solution
  • 23:09 - What constraints does Next.js impose on your app (e.g. middleware doesn't run node), and what benefits do those constraints give you?
  • 36:13 - How Next.js APIs are motivated by wanting to tease apart static and dynamic code, in an attempt to support the needs of any web app with a single stack
  • 40:33 - What is the relationship between frameworks and infra?
  • 47:37 - How can frameworks that add infra-specific APIs best communicate the costs of those APIs and the benefits they enable?

Links:

  continue reading

201 에피소드

Artwork

Can you self-host Next.js?

Frontend First

213 subscribers

published

icon공유
 
Manage episode 444554316 series 1635850
Frontend First, Sam Selikoff, and Ryan Toronto에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Frontend First, Sam Selikoff, and Ryan Toronto 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.

Sam and Ryan talk about how frameworks and infrastructure evolve with each other, using Next.js as a representative example. They discuss how hosting providers like Heroku have always imposed certain constraints on apps, what features those constraints enable hosting providers to support, how burdensome those constraints are across different frameworks, and how frameworks that add infra-specific APIs can best communicate the costs of those APIs and benefits they enable.

Timestamps:

  • 0:00 - Intro
  • 3:03 - Heroku and the Twelve-Factor App
  • 7:39 - GitHub Pages and static sites
  • 13:57 - Serverless and JAMstack
  • 17:30 - Vercel and CDNs, self-hosting, and Next.js
  • 19:00 - How framework APIs can nudge an app towards a particular hosting solution
  • 23:09 - What constraints does Next.js impose on your app (e.g. middleware doesn't run node), and what benefits do those constraints give you?
  • 36:13 - How Next.js APIs are motivated by wanting to tease apart static and dynamic code, in an attempt to support the needs of any web app with a single stack
  • 40:33 - What is the relationship between frameworks and infra?
  • 47:37 - How can frameworks that add infra-specific APIs best communicate the costs of those APIs and the benefits they enable?

Links:

  continue reading

201 에피소드

सभी एपिसोड

×
 
Loading …

플레이어 FM에 오신것을 환영합니다!

플레이어 FM은 웹에서 고품질 팟캐스트를 검색하여 지금 바로 즐길 수 있도록 합니다. 최고의 팟캐스트 앱이며 Android, iPhone 및 웹에서도 작동합니다. 장치 간 구독 동기화를 위해 가입하세요.

 

빠른 참조 가이드