makes your http://localhost:3000 accessible

on YouTube ↗24m

" summary

A concrete how‑to that actually moves http://localhost:3000 into a cloud setup with real tradeoffs: drop‑in SAS (Vercel Netlify Amplify) reaches production fast but limits control, self‑managed stacks (Kubernetes EKS, Cloud Run) add plumbing—DNS, load balancers, secrets, TLS, policy and compliance and a quick dig shows two IPs implying load balancing. Coverage includes practical tools and a demo of DNS/IP discovery, networking abstractions, API endpoints and when the deployment needs a platform team versus a plate‑and‑ship result.

AI-written summary · about

" chapters (16)

1. 0:00Introduction
2. 1:06Production deployment beyond code
3. 3:14Scaling beyond simple hosting
4. 6:25Control versus abstraction
5. 8:11Policy as code and compliance
6. 9:13Networking fundamentals
7. 11:20Data to application flow
8. 12:25IP addresses and DNS
9. 14:52Subnetting and routing
10. 15:58DNS in API communication
11. 17:23APIs as endpoints
12. 19:29Tracing API request
13. 20:52SAS versus enterprise production
14. 21:15Hacking APIs for infrastructure
15. 23:22Downtime equals lost revenue
16. 24:04Q&A

" related talks

• 42mFrom Localhost to ProductionGautam Arora · JSHeroes 2017
• 24mLets go liveDano Gillette · UtahJS Conf 2023
• 41mBuilding & testing Cloud applications locally using LocalStackHarsh Bardhan Mishra · Python Web Conf 2023
• 01h 27mSpring Cloud at NetflixJon Schneider, Taylor Wicksell · SpringOne2GX 2015
• 37mAre you being servered? — exploring a serverless webPhil Hawksworth · International JavaScript Conference Munich 2019
• 34mCutting Through the Fog of CloudKyle Rames · LoneStarRuby Conf 2013
• 43mServing for the win - Deploys and hosting for the rest of usPhil Hawksworth · Render Conference 2018
• 05mLightning talk: Give a try to the JAM(stack)Konstantin Bifert · Nordic.js 2019