Functions as a Service (FaaS) are only a narrow subset of Serverless. And yet, FaaS (a form of serverless compute) dominates most discussions of the topic. This narrow focus on FaaS, and the endless debates around it make it difficult for us to understand & explore what it really means to be serverless. The wider concept of serverless holds much more promise than just compute. A (Partially) Serverless Architecture from Microsoft...
There’s a glut of FaaS providers on the market right now. Cloud providers, database vendors, notification services, your plumber (probably): everyone’s doing it. And they’re constantly telling you how great it is. Needless to say, it’s getting increasingly difficult to untangle this writhing pile of hype beasts. How do you choose between them? On what dimensions should you assess them? Note: I’m going to try really hard not to talk about specific providers here even though we all know the main players are: AWS Lambda, Azure Functions, Google Cloud Functions and IBM Cloud Functions....
We need a good name for when a word is so overused it loses all meaning. Semantic Satiation doesn’t quite cut it (too bland). No, we need something like “enshittification” that really captures our collective disappointment at a good thing ruined. And yes, the word “Serverless” is most definitely ruined. Sementic Tomfoolery It is no longer possible to use the word “Serverless” (in good faith) without immediately clarifying what you mean....