Concept of pre –

1. Mid-long tail applications

Long tail apps are those that have little or no traffic for most of the day.

2. Load balancing service

The load balancing service distributes traffic evenly to application machines.

3. Reverse proxy

The reverse proxy resolves the domain name information from the request and forwards the request to the upstream listening address. Common examples are: Nginx.

ServerlessWhat is the

Serverless = Server + less

  • ServerServer, yesServerlessResolving the boundaries of the problem;
  • lessLess care, yesServerlessThe purpose of solving the problem.

Serverless “care less about the server side”.

1. ServerThe service side

MVCThe architecture of theWebapplication

Developer icon Internet User Icon

Modern R&D system is mainly divided into front-end and back-end:

  • The front end is responsible for the customer terminal experience, i.eViewLayer;
  • The back end is responsible for the business logic and data processing of the business, i.eControlLayer and theModalLayer.

Serverless the frontier of problem solving is the frontier of the server side, namely the server-side operation and maintenance, which is responsible for the online operation and maintenance of applications or code.

2. lessLess concerned about

Serverfull vs. Serverless

concept describe
Serverfull We are responsible for the operation and maintenance of the server.
Serverless We are less responsible for the service side operation and maintenance, and most of the operation and maintenance work is handed over to usAutomation toolBe responsible for.

Serverless is an extreme abstraction of an o&M system that provides a minimalist model for application development and deployment. This highly abstract model allows a person with zero operational experience to deploy and service a Web application online in a matter of minutes.

3. ServerlessThe server is o&M free

Server defines the boundary of Serverless to solve problems, that is, the Server is free of operation and maintenance; Less describes the problem solving purpose of Serverless, which is to avoid operating and maintaining NoOps.

Serverless: The server does not need o&M.

  1. Serverless = Serverless Computing architecture = FaaS architecture = Trigger (event-driven) + FaaS (function-as-a-service) + BaaS (back-end as-a-service, persistent or third-party services) = FaaS + BaaS

    • FaaS:Function as a Service 或 Service Computing, functions as services;
    • BaaS:Backend as a Service, back-end as a service;
    • XaaS:X as a Service.XAs a service. Such as:SaaS,PaaS,IaaSAnd so on.

    The narrow senseServerless = Serverless ComputingArchitecture =Trigger + FaaS + BaaS

  2. The generalizedServerless= Server o&M free = YesServerlessFeature cloud services

    1. Users do not need to care about the service side (fault tolerance, DISASTER recovery, security verification, automatic capacity expansion, log debugging, etc.).
    2. Pay by usage (number of calls, duration, etc.), low cost and high performance in parallel, saving in most scenarios;
    3. Fast iteration and trial-and-error ability (multi-version control, gray scale, etc.).

MVCThe architecture of theWebapplication

Trigger + FaaSimproved BaaS + View + FaaSrefactoring