Others ask you: What is serverless? How do you respond in a way that makes you sound professional and knowledgeable?
If your answer is serverless, then it’s gone. There’s a hundred question marks in that guy’s head!
So what’s the more profound answer?
As a technical person, I’ll take the hottest technology concept Serverless, the hardest to explain, as an example:
A: Serverless is A service architecture based on cloud deployment.
B: It consists of two parts, FaaS (Functions as a Service) and BasS: Backend as a Sevice.
C: Serverless to achieve cloud functions and back-end servitization. Cloud function is a new way to organize and provide computing power, which makes users no longer need to care about server management and configuration, but only focus on the writing of core business logic business code. Back-end servitization includes but is not limited to database operations, object storage, account authentication, message queuing, social media integration, AI capabilities… And other functions are packaged into SDK or API to connect and call.
D: Serverless does not mean simply running your cloud functions and back-end services on a cloud server. Rather, it means implementing a computing framework for functions that must be event-driven, stateless, cold-started, dynamically scalable, time-limited and on-demand (request).
E: The core difference between serverless and FaaS is the computational payment model.
Like to read technical management articles, please pay attention to the public account “qunyu Bay”, grow up with you.
