Building a cloud friendly application

on YouTube ↗01h 00m

" summary

Clear rules: keep code on a read-only file system as a built artifact and keep user content in writable storage (DB or S3), inject all runtime values via environment variables and use dot env for local dev only, never check secrets into git. Platform.sh example uses a base64 JSON blob env var for service credentials and glue code maps that into drivers. Favor a multi‑modal monolith (fast startup, single deployable) over microservices unless scale justifies added latency, API‑versioning and team overhead.

AI-written summary · about

" chapters (9)

1. 0:00Introduction
2. 2:59Cloud computing basics
3. 7:16Code vs content separation
4. 15:34Config management
5. 26:52Dependency injection
6. 33:56Avoiding vendor lock-in
7. 41:17Microservices vs monoliths
8. 47:47Summary
9. 48:48Q&A

" related talks

• 20mBuilding a cloud-friendly applicationLarry Garfield · APIdays San Francisco 2019
• 51mBuilding a cloud-friendly applicationLarry Garfield · PHP Yorkshire 2019
• 41mThink Cloud, Develop LocallyMichael Blakeney · All Things Open 2020
• 24mA Cloud Native Foundation For Developer/Application PlatformsMax Korbacher · Cloud Native DevX Day North America 2021
• 31mSimplifying and Standardizing Developer Environments for the CloudElson Yuen, Serhii Leshchenko · Cloud IDE Day 2021
• 42mBuilding Scalable Mobile Projects: Fast Builds, High Reusability and Clear OwnershipCyril Mottier · AndroidMakers by droidcon 2025
• 30mImproving the Cloud Development Experience: The Good, The Bad...Arsh Sharma, Ramiro Berrelleza · KubeDay India 2023
• 30mBuilding Applications in the Cloud: Best PracticesChristopher Skene · apidays Singapore 2019