Building a cloud-friendly application
summary
Argues that cloud-friendly apps keep developer files immutable and user data writable, producing a build artifact (composer/pip/npm or compiled binary) that slots into environments with existing DBs and indices; Platform.sh proves the model by passing JSON-encoded DB creds into PHP/Node/Go glue code and using dotenv locally; recommends separate code and content, use environment variables to dependency-inject environment, avoid installers that write code at runtime, prefer a multimodal monolith over microservices unless operating at Netflix/Google scale.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:43The CloudTM: noun Someone else's hard drive
- 2:16Cloud computing: noun Abstracting away physical infrastructure
- 3:49What makes an application cloud-friendly?
- 7:56Your application is disposable Your data is not
- 9:50What is configuration?
- 12:51What happens at runtime stays at runtime
- 20:49Constants?
- 21:34User-configured connections
- 31:32(defined broadly) will produce a design whose structure is a copy of the organization's communication structure.
- 36:19Admin' application
- 37:34All asynchronous
related talks
20mBuilding a cloud-friendly application
34mThe Internet is your Application Blueprint
01h 00mBuilding Cloud-Native Applications
26mBeyond Dapps and Code?
46mPlatforms: Build abstractions, not illusions
31mI have a Dreamcode: Build Apps, not Backends
41mModernizing Legacy Apps - Platforms and Strategies
58mPlatforms: Build abstractions, not illusions