Serverless Commerce: Higher, Stronger, FaaSter!
summary
Serverless commerce uses FaaS plus cloud-native APIs to replace servers with pay-per-use services and align provider/customer incentives, with cloud events for portability. Examples: Twilio functions deploy in minutes and integrate with protected phone flows; Braintree custom payment plug‑ins with five callback methods let providers add regional payment methods; demo: PO‑box fraud filter runs on both AWS Lambda and Google Cloud Functions and flags orders for manual review, proving cross‑cloud adapters work in production.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:32Serverless platform (according to CNCF)
- 2:441. Function-as-a-Service (FaaS)
- 3:362. Backend-as-a-Service (BaaS)
- 5:34Pay for what you use (no cost for idle)
- 6:56From Monolith...
- 8:45Problem with Cloud & Micro-Services: Extensibility & Customizing
- 10:57Multi-tenant architecture (1/2)
- 13:38How to extend a multi-tenant system?
- 14:47FaaS advantages over webhooks
related talks
58mServerless Under the Hood
30mServerless State of the Union
53mServerless is the Abstraction We Deserve
24mThe Future of Functions
24mServerless powered Low Code
04mServerless Architectures: What, why, why not, and where next?
50mWhere We’re Going, We Don’t Need Servers!
42mFaaS or not to FaaS: Visible & invisible benefits of the Serverless paradigm