A Monstera deliciosa evolved in a Central American rainforest where humidity runs at 80 to 90 percent, where light filters through a canopy and shifts with cloud cover, where air moves continuously from convection and wind. None of that is present in a Czech apartment in winter. So the plant now lives in an IKEA Milsbo cabinet with a small USB humidifier, a full-spectrum LED strip light on a timer, and a mini fan mounted inside the door. The plant doesn’t know the difference. The conditions are met.
Serverless computing makes the same offer. AWS Lambda runs your code without you managing a server: no provisioning, no patching, no capacity planning. The pitch is “NoOps”: the environment is handled. Martin Fowler’s survey of FaaS corrected this in 2016: the ops work didn’t disappear, it changed form. You still monitor, still secure, still debug — through IAM policies, execution timeouts, cold start latency, reserved concurrency limits. The function runs. The conditions are met.
Both systems work by translating the environment, not eliminating it. The rainforest’s humidity becomes a humidifier spec. The server’s process manager becomes a Lambda timeout. What changed is who maintains it, and how the maintenance is described.
The plant doesn’t know it’s not in a rainforest. The function doesn’t know it’s not on a server. The work of knowing belongs to the person who set up the cabinet.