SE Preparation Resources
Quick-access resource hub organized by topic area. Jump directly into any section of the study guide.
🎯 Top Interview Questions to Prepare
☁️ Azure vs Vercel — Compare & Contrast
Coming from Azure? This section maps every Azure concept to its Vercel equivalent so you can leverage your existing knowledge.
| Area | ☁️ Azure | ▲ Vercel | 💡 Key Insight |
|---|---|---|---|
| Compute | Azure App Service, Azure Functions, Azure Container Apps — you pick the compute, configure scaling rules, set up App Service Plans | Serverless Functions, Edge Functions, Fluid Compute — zero config, auto-scales per request, pay for active CPU time only | Vercel abstracts away all infrastructure. No App Service Plans, no scale sets. Your framework defines the infra. |
| CDN & Edge | Azure Front Door + Azure CDN — separate services to configure, custom rules engine, origin groups, WAF policies | Built-in Edge Network (100+ PoPs) — every deployment is globally distributed automatically. Edge Middleware runs code at the edge. | On Azure you wire up Front Door separately. On Vercel the edge is the default — no extra setup. |
| CI/CD & Deployments | Azure DevOps Pipelines or GitHub Actions → Azure App Service/Static Web Apps — you build the pipeline YAML | Git push → automatic build & deploy. Preview deployments for every PR. Zero pipeline config needed. | Azure gives full pipeline control. Vercel trades that for instant DX — every push is a deployment with a unique URL. |
| Static Sites | Azure Static Web Apps — good for JAMstack, integrates with Azure Functions for API routes | First-class SSG/ISR/PPR support — static pages with on-demand revalidation, no separate API layer needed | Azure SWA is the closest equivalent but lacks ISR and PPR. Vercel's rendering model is more granular. |
| Serverless Functions | Azure Functions — Consumption or Premium plan, cold starts on Consumption, you manage runtime versions | Serverless Functions with Fluid Compute — ~0 cold starts due to connection reuse, Active CPU pricing, auto-concurrency | Azure Functions are general-purpose. Vercel Functions are web-optimized with framework-aware routing and zero config. |
| AI / ML | Azure OpenAI Service, Azure AI Studio, Cognitive Services — deep model customization, fine-tuning, enterprise compliance | AI SDK (TypeScript-first), AI Gateway (multi-provider routing), streaming UI — optimized for front-end AI experiences | Azure excels at model training & enterprise AI. Vercel excels at shipping AI-powered user experiences fast. |
| Security & WAF | Azure WAF (via Front Door or App Gateway), NSGs, Private Endpoints, Azure DDoS Protection Standard | Built-in Configurable WAF, DDoS mitigation, Bot Management, BotID, Deployment Protection — all integrated | Azure gives granular network control. Vercel bundles security into the platform — simpler but less customizable at the network layer. |
| Caching | Azure CDN caching rules, Azure Redis Cache — manual configuration of cache headers, TTLs, purge policies | Multi-layer auto-caching: ISR Data Cache, Full Route Cache, CDN Cache — framework-aware cache invalidation with revalidateTag/Path | Vercel caching is framework-integrated. You revalidate from your code. Azure caching is infrastructure-level — more manual. |
| Domains & DNS | Azure DNS zones, custom domain mapping in App Service/Front Door, separate SSL cert management | Add domain in dashboard → automatic DNS + SSL. Wildcard domains, subdomain routing via middleware. | Azure requires manual DNS zone + cert binding. Vercel handles DNS and SSL automatically. |
| Monitoring | Azure Monitor, Application Insights, Log Analytics — powerful but requires setup and KQL queries | Speed Insights, Web Vitals, Runtime Logs, Observability suite — purpose-built for web performance | Azure Monitor is enterprise-grade and general. Vercel Observability is web-focused and zero-config. |
| Pricing Model | Pay for provisioned resources (VMs, App Service Plans, reserved capacity) — complex cost forecasting | Pay per request/execution. Hobby (free), Pro ($20/mo), Enterprise (custom). Active CPU billing for functions. | Azure bills for reserved infra. Vercel bills for usage. Vercel is cheaper for spiky web traffic; Azure may win for steady-state compute. |
| Developer Experience | Azure Portal, CLI, SDKs, Bicep/ARM templates — powerful but steep learning curve | vercel.com dashboard, `vercel` CLI, Git-based workflow — designed for frontend/fullstack developers | If you're used to Azure's depth, Vercel will feel magically simple. The trade-off is less infrastructure control. |
🚀 Tips for Azure SEs Transitioning to Vercel
Map Your Mental Models
Azure App Service → Vercel Project. Azure Functions → Vercel Serverless Functions. Azure Front Door → Vercel Edge Network. Azure DevOps → Git push.
Embrace Framework-Defined Infrastructure
In Azure, you define infra then deploy code. In Vercel, your Next.js code defines the infra. A Server Component becomes a serverless function automatically.
Rethink Caching
Move from CDN-rule-based caching to code-level revalidation. ISR's revalidate: 60 replaces Azure CDN TTL rules. revalidateTag() replaces cache purge APIs.
Leverage Your Enterprise Knowledge
Your Azure experience with SSO/SAML, RBAC, compliance, and enterprise sales cycles directly transfers. Vercel Enterprise has similar concepts — just platform-native.
Think Edge-First
Azure runs functions in regions you pick. Vercel Middleware runs at 100+ edge locations by default. Think: what can I push closer to the user?
Use Your Architecture Skills
Composable architecture, microservices, API gateways — all apply. On Vercel the building blocks are Next.js routes, API routes, Edge Middleware, and ISR instead of App Gateway + APIM + Functions.