Framework-defined infrastructure

This post introduces and explains the concept of Framework-Defined Infrastructure (FdI) as an evolution of Infrastructure as Code (IaC). It details how FdI allows frameworks to automatically infer and provision the necessary infrastructure based on application code and framework conventions, rather than requiring explicit IaC configuration. Examples are provided using Next.js to illustrate how different code patterns (e.g., `getServerSideProps` vs. `getStaticProps`) translate to different infrastructure deployments (serverless functions vs. static file serving). The post also touches upon how FdI applies to other frameworks like Gatsby, SvelteKit, and Remix, and how it integrates with Vercel's Build Output API.