The author | edition (Tudor) source | Serverless public number

Human’s pursuit of freedom has never stopped, we use the fight to obtain national freedom, we use the code to obtain both hands of freedom, at the same time as the slave of the server code, also began to be ready to move, the revolution has begun, when the code to turn the initiative, as a developer we how to adapt to the arrival of the new era?

Everything As Code

Code has always been a prisoner in the server, but the revolution has come to look at code and how it takes control of the environment step by step and moves towards services.

1. Revolution: Code control compilation and packaging

Pipeline as code: represents Technical Jenkins Pipeline

2. Revolution: Control the server with code

Machine as code: stands for technical Docker

3. Revolution: Control the server cluster with code

Server Cluster as Code: technology K8S

4. Revolution: Control base resources with code

Infrastructure as Code: Stands for technology Terraform

When everything is code, A=B can get B=A, code as A service era has arrived.

Second, the advent of code as a service era

1. Code warehouses in the traditional era

In traditional code repository instructions, the “Runtime environment installation wizard” document is required. Take SpringBoot code as an example, it comes with the installation wizard document.

2. The code warehouse of the new age

Refer to the code repository AWS -lamda-spring-boot2, which includes all the code required by Springboot to run to AWS for LAMda.

3. Mainstream technology’s embrace of the new era

Take the development of Spring as an example. Starting from SpringBoot, environmental control is continuously integrated until SpringNative can directly build images.

Third, code as a service under the cloud native architecture

Container services: Control everything with code

2. Microservice engines: Trust standard platforms and give some control to them

3. Functional computing: Trust standard platforms and give them most of the control

4. The r&d platform war under code as a service

In the era of code as a service, major manufacturers are establishing their own cloud R&D closed-loop, who do a good job on the cloud development platform, who can seize the heart of the next cloud native developers.

1. Code hosting Wars: Get the code

  • Microsoft is buying GitHub
  • Google invested in Gitlab
  • AWS builds its own private repository, CodeCommit
  • Aliyun enterprise code hosting platform Codeup

2. Online development wars

  • Microsoft is integrating VS Code with Github to launch Github Codespace
  • Google has taken a new approach by creating Cloud Code, an offline IDE plug-in that connects to Google Cloud
  • AWS Online Cloud IDE: Cloud 9
  • Ali Cloud IDE: DevStudio

3. Build DevOps battles online

  • Azure DevOps
  • Google DevOps
  • AWS DevOps
  • Ali Yun Yun effect

4. R&d system development

  • In the era of code as a service, Git as a code version management software, coupled with WebHook, can easily manage the entire code operation life cycle, GitOps came into being. GitHub has incorporated the ideas of GitOps into GitHub Actions.

  • AWS launched Proton, a service and environment template with fully configured code, opening up platform building and reuse capabilities to platform developers, allowing ordinary developers to focus more on business implementation.

5. Aliyun Development Platform

1. Cloud development platform: through the integration of cloud native products and cloud effects, the cloud native development loop is completed

2. Cloud development platform, build application-level cloud native applications, and preset standard cloud architecture

3. Cloud development platform, application sharing

  • Cloud development platform and Tmall genie, Dingding team cooperation, integration of small program before and after the end of the development and deployment together, to solve the small program cloud and user cloud can not get through the problem, add user cloud ability to the small program.
  • Cloud development platform applications can be shared among teams, and technical exchanges between teams are no longer just clone code.
  • Cloud development platform market sharing, the subsequent technical solutions of partners can be directly built on the market, so that cloud service providers no longer need to help users build and maintain the cloud environment on site.

Six, the concluding

We sincerely invite you to join the cloud development platform, together to build a cloud research and development platform serving the millions of Ali Cloud developers ali Cloud.

Reference:

  1. Performance of running Spring Boot as AWS Lambda functions

This article is compiled from ali Cloud technology expert — Tudor share PPT on “Ali Cloud Serverless Developer Meetup In Shanghai”. Access method: Pay attention to Serverless public account, background dialog box reply “PPT” can live playback watch address: developer.aliyun.com/live/246653