Serverless Rendering with Azure Functions and TypeScript
summary
Pendulum settles in the middle: choose static, client or server rendering per route and per component. Shows concrete serverless setup using Azure Functions, TypeScript and template.jsx to render JSX to HTML strings, plus Next.js routes switched between getStaticProps and getServerSideProps. Builds a notes app with database reads embedded in server components, deploys to Azure Functions and mostly succeeds live, demonstrating hydration, proxies for pretty routes, and tiny server responses instead of shipping megabytes of JS.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker intro
- 1:58History of server-side rendering
- 9:45Client-side rendering and AJAX
- 12:16Rise of client-side applications
- 16:53Hydration and server-side rendering
- 19:43Static site generation and JAMstack
- 21:52Setting up serverless rendering demo
- 27:09Creating HTML with TypeScript and JSX
- 33:14Using proxies for routing
- 36:29Deploying to Azure Functions
- 37:55Serverless rendering benefits
- 38:57Next.js static vs server-side rendering
- 41:49Yest tool for serverless rendering
- 43:34Status quo in modern rendering
- 44:37Server components in React
- 48:48Conclusion and resources
related talks
59mServerless frontend, serverless backend, serverless security!
29mBuilding a Serverless Compute Platform with AWS and TypeScript
28mBuild Serverless Apps with Blazor
59mAzure Serverless for JavaScript TypeScript Folks
35mServerless Functions and Vue.js
46mBuild serverless, full stack applications in Azure with Azure SQL
41mStatic Sites and Serverless Functions - A Dynamic Combination
22mVue.js and Serverless