In the Linux world everything is file, in the Serverless world everything is an HTTPS interface.

Serverless applications by their nature are heavily decomposed into a variety of services, such as autonomous functions, object storage, authentication services, document databases, and pub/sub message queues. The interfaces between these services are typically HTTPS. When you’re using the AWS SDK to call an AWS services, the interface it’s calling under the hood is an HTTPS interface. This is true for the majority of cloud platforms, with some alternative protocols occasionally being used (WebSockets and MQTT) in specific use cases.

In the same way that in Linux you can access all the resources of the underlying machine through the file system, in a serverless world you can access all the resources of the underlying cloud platform through an HTTPS interface.

The comparison though goes further than just use of a common interface, serverless application design best practice is starting to look a lot like the Unix Philosophy, which extends to Linux (lets not talk about systemd).

Doug McIlroy distilled the Unix Philosophy down to

“Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface.”

Adapting the Unix Philosophy for the serverless world is simply a matter of changing the interface.

“Write programs that do one thing and do it well. Write programs to work together. Write programs to handle https, because that is a universal interface”.

Doug McIlory in an extended definition of the Unix Philosophy makes these four points.

Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new features.

Expect the output of every program to become the input to another, as yet unknown, program. Don’t clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don’t insist on interactive input.

Design and build software, even operating systems, to be tried early, ideally within weeks. Don’t hesitate to throw away the clumsy parts and rebuild them.

Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw some of them out after you’ve finished using them.

Paul Johnston in his talk, What I Wish I’d Known Last Year, at ServerlessConf in NYC last year, touched on some simple principles he found useful for designing serverless applications, namely

Start with Deployment Management

You can afford to fail faster

Zero or 1 data transformation per function

Don’t overcomplicate your data schema

Paul’s points could almost be corollaries to Doug’s points.