Sunrise of Platforms as Services (PaaS)
summary
Claims that companies often overspend 25–200% on cloud due to wrong service-model choices and shows a concrete architecture: a PaaS with two outlets (a SaaS setup endpoint and an API/SDK for infrastructure), an API gateway, integrated auth (access/refresh tokens like Azure/AWS IAM), and event-driven scaling that issues SDK/API calls to on‑prem or IaaS. Examples include using AWS Lambda / Elastic Beanstalk as workloads and an EEG device SDK that emits events into the platform for bioinformatics pipelines.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 2:08What is PaaS and why it matters
- 5:58Cloud service models overview
- 9:02Scaling and event flow in PaaS
- 11:41Authentication in PaaS
- 12:04PaaS in bioinformatics
- 16:38Conclusion and key takeaways
related talks
33m“PaaS”, The Secret Weapon of Coders in Cloud Wars
25mMaking the Leap: Transitioning Enterprises to a PaaS Mindset
29mLet's call platforms what they really are, ways to provide something-as-a-Service
15mPaaS isn’t enough: your internal platform in Multi Cloud
24mIs PaaS the DevOps Killer
28mPanel: Emerging Trends in Cloud Engineering: Platform as product, APIs, self-service & more
29mPlatforms, Architecture and Sustainability
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines