On JAMstack Architectures
summary
Describes moving a content site from WordPress to a JAMstack static workflow to gain performance and security: cites a migration of ~3,000 articles and ~200,000 comments that runs about 6× faster and notes widespread WordPress vulnerabilities. The architecture uses Markdown as the content store, static site generators such as Jekyll, atomic builds with incremental deploys, and serverless Lambda functions for dynamic hooks like Stripe/PayPal payments.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:12Tech stack importance
- 3:23Quality attributes
- 4:49Web dev evolution
- 7:23Modern dev complexity
- 8:52JAMstack architecture
- 10:36Static site generators
- 12:08JAMstack workflow
- 14:43E-commerce in JAMstack
- 17:56JAMstack advantages
- 19:44Websites vs apps
- 21:07Real JAMstack example
- 22:57Netlify ecosystem
- 25:10Performance optimization
- 26:19Q&A
- 26:40User auth in JAMstack
- 27:42Microservices in JAMstack
- 28:48Search in static sites
- 30:14Git workflow benefits
- 31:16Dynamic storage
- 32:25Cost considerations
- 32:47Avoiding JAMstack
- 33:30Dependency risks
- 35:16Closing
