Cloud, Hosting and Serverless
Understand what your team still owns when infrastructure is managed. · Technical Fluency · Lesson 24 · 3 min
Cloud, Hosting and Serverless · 3 min
Situation
“It’s serverless, so we don’t manage servers.”
A team proposes running file processing in a cloud function. That can reduce machine management, but it does not eliminate time limits, cost, failures, or operational responsibility.
Ask what the service manages for you and what the application team must still design and monitor.
Mental model
Hosting is where software runs.
A server is a system that responds to requests. Hosting provides a place for software or files to run and be served. Cloud platforms offer computing, storage, and networking as managed services.
A function executes code in response to an event. Serverless generally means the platform manages the underlying capacity and execution environment, with platform-specific limits and billing.
Example
A static library and a processing service differ.
A static learning site can serve prebuilt HTML and CSS from an edge network. No application database is required. A file-conversion product needs runtime code, storage, and a way to report progress.
Cloudflare- or AWS-style services can supply these building blocks. The relevant comparison is workload fit and operational burden, not the number of services in a diagram.
Failure case
A long job exceeds the execution model.
If a file takes several minutes to process, a short-lived request handler may time out. Raising expectations in the interface does not remove the limit.
A background job with durable status might fit better. Verify actual provider limits and behavior before promising file sizes, completion times, or unlimited processing.
PM question
Who operates the full experience?
Ask about deployment, logs, alerts, retries, regional availability, cost at expected volume, and what happens when the provider is unavailable.
A managed platform reduces some work, but your team still owns correctness, access rules, configuration, and the user-facing recovery path. Include those responsibilities in estimates.
Remember this
Managed does not mean ownerless.
Use the cloud to reduce undifferentiated work, while making limits and remaining responsibilities explicit. “Serverless” describes an operating model, not a guarantee of simplicity.