Hey everyone. Welcome to Alibaba Cloud essay to the vacation exam preparation training. In this chapter, I will introduce mostly the first layer of the whole training. The application deployment, including the following product. In this chapter, I divided into four sections. The first section I will give you an overview about if you want to deploy applications to Alibaba cloud, what kind of different product or service you can choose from. In the second section i will talk about the migration tools to help you to migrate the application to the cloud. Then in the 3rd section we talk about server based application deployment, majorly focusing on ECS and SAS. And the last section of this chapter, we talk about the cloud native solutions for your application like the contain the registry, like the ECI and also the function compute. Now let's take a quick overview about what kind of choices you may have to deploy applications in Alibaba cloud. So here I separate this product into the three major categories. The first one I call them virtual server based. The second one is container based and the 3rd 1 is called Service. The word user were based two products, we will immediately introduce the simple looking server and PCS. Also to migrate your existing application from the third party vendors, you can using our server migration center to migrate applications to ECS. But when we talk about a container based, we're talking about some application, they may not want to deploy on the service directly. They want to turn them into a so called containerized application so that it turned into a container image. And it can be stalled in the Alibaba cloud continued then later on, if you want to deploy that image and the container, you can go to the ECI to deploy applications directly. The ECI is Alibaba cloud less the container instance. So that one is more like a lightweight container based service to hold the application. And this kind of service can bring your application on and don't very fast speed and consume even less resources. And the last one is a server less category. When you talk about server less, I mean you don't need to see or be aware of the backhand servers, what do you all see? And the service can provide is something like the function compute which means you only need to upload a piece of code into the clown. And make sure you follow the guidelines of the programming methods and the API definition, then the piece of code can be triggered on whatever the situation is met. And together with the 3rd list work flow, you can integrate different compute services into a whole work flow to make them smoothly work together. And also in Alibaba cloud, we provide the API gateway. So API gateway at the same time, they can combine any different forms of the service you're providing through the either fund compute or through the ECI or through the ECS, right. So whatever your application is, it can just provide a standard http level well service interface. It can be integrated into the API gateway, then provide clients with centralized and unified service end point. So all in all, in Alibaba cloud you have different forms to consider and to be choose from to deploy your applications based on your business need and maybe the performance needs. Now, let's look into the application migration section, in this section of you majorly introduced Alibaba cloud server migration center. So the major purpose of using SMC is to give you the capability to migrate the different forms of education from the different source to Alibaba cloud. So your article server could be some virtual machines running on welfare or some other cloud vendors. And also it could from your IDC, right. And it's also SMC support to migrate your existing easiest server from the different regions in the Alibaba cloud to the other region. That is the major scenarios the MSC can help you to do. But the biggest benefit you can gain from using SMC is you do not need to create any image locally, which means the whole idea of using an SMC is like this chart shows. The only thing you need to do, the first thing is to install the SMC clients, sometimes we call it agent into your existing applications environment. Maybe the physical server, maybe the virtual server. Right, then you make the client running, then you go to the SMC council from the US Point of view. Now you need to create a migration task from the task you may clarify some memories and source information. After everything is settled, you can start the migration task when the migration was ongoing. The council can be used to check the immigration status from time to time. If something fails, you can go back to check the problem. Hopefully every migration task can finish finally successful. And what you have is now without creating any image from the south side you have a new generation image directly from Alibaba cloud. The last opposition leaves to our users is that you can decide if you want to use this image to generate a new us based on the different specification, right. So, you see the whole process is very user friendly by just migration of data through the SMS decline and the council and finally generated image on the cloth side. Our users can avoid a lot of problems by creating the image from their own site and upload image. And finally, the image can not be recognized or can not be convert to the Alibaba cloud. So all those problems will be disappear if you're using SMC. So all in all SMC is the product you can use to migrate existing application from the different original source. So, now let's look into one simple question which we might ask in the developer examination So the question is like which of the following is not required for the SMC to moderate the server to Alibaba cloud. This question is majorly based on the previous procedure. So we give you four options. This is a single choice question. The first option is in part the migration source information to the SMC console. I think this might be needed. Right. The second one from the SMC console conflict, the type of this image to be generated during the migration. Maybe we have a question mark here. So the SMC client, transfer the soft data to an intermediate ECS instance. So this is also correct. The SMC backend and so is generally the target image based on the migration source this step, I think we also see it from the previous chart. So finally we decided that maybe the option B is not the correct answer because we do not need the under user to configure the type of this image. So the options be. Now let's look into the two Titus so called the summer based application deployment. The first one is the most commonly used washing machine in the cloud is called the ECS, the elect computing service. For people who are being familiar with the ECS service, we can consider the ECS is suitable or applicable for the foreign scenarios. Definitely if you want to set up official website, our applications consider to deploy them into ECS and if your application needs to deal with some multimedia, only some high concurrent application precise. ECS for some special specifications can handle that definitely you can also use the easiest using its powerful computing capability to support your AI applications such as machine learning and deep learning. You know ECS is so general purpose build, you can use it for whatever the computing condensed application requirements with the ECS we can also support you to manage the whole virtual machine lifecycle by creating the snapshot to the image and finally duplicate your semen environment from here and there. Regarding the ECS. I give you one simple question. In Alibaba Cloud the developer finds that ECS instance he created does not have public IP address. The API method used to CreateInstance which of the following is the most likely reason. When you look through the options, the only one fall into our attention is the developer did not call or locate the public I P Address which is needed to assign a public I P. This option is the right one because when you called API to deal with the ECS configuration, it is not like building the council directly. You may choose different options at the same time for the API colleague you need to call the different methods one by one to fulfill a complete task. Public IP address is not a mandatory one for the ECS configuration. So you have to use this one to call it separately. So other options are not very directly related to this question. Another product you may want to consider to deploy application directly in the cloud. It's called a simple application server, which clearly we shot as SAS comparing he says SES is designed naturally for lightweight application environment deployment. So I also listed some applicable scenarios for SAS. Maybe you want to build a small size website. Maybe you want to build a personal blog if you want to build just a forum or community or you can just use it to build your personal learning environment or small ecommerce website. Right. Just for your own personal development requirements. Also as this chart shows the benefits of using SAS is that it naturally integrate some existing web application environment. So you can just pick up those existing environment and deploy your SAS in a few clicks at the same time, not like the individual ECS. SAS integrate some other services directly with the instance in deployed like the whip you see by default and certification as a sparrow dominant binding those kind of Alibaba cloud services, they were naturally integrated with S A S. So again, considering SAS and another way is more likely the way to deploy some applications which may not be a critical business requirements, but it can still fulfill some of the application deployment requirements. Now, let's look into one simple question for the S A S. So which of the following the application are suitable for deployment on simple application server. And compared with ECS. This is a multiple choice question. The correct answer is three. So comparing to the previous slide, the first one. Quickly build a personal blood website. Quickly build a small e commerce website. Quickly build a civilized site using function compute this is I leave a question mark here and set up a notable W service. Did you really need some good performance especially for the national database? So I don't think it's a proper answer. So quickly build a personal learning or testing environment. I think this one is definitely correct. So the answer should be A B and E here. I also give you a table to compare between the ECS and SAS when the list here, the sea is not supported. It means doesn't mean it cannot do. It just means they didn't integrate this kind of feature naturally to the product itself. So SAS support the domain binding in the council. And also we can manage from the application level, especially for the SAS remote connection. You can directly do it from the council. So using this table, you can quickly have understanding about the difference between SAS. It doesn't mean the ECS is not good enough. It's just saying that SAS maybe for your lightweight self maintain application, it is another good choice comparing with ECS. Okay, now let's look into the last section, some cloud native solutions you can think of to deploy application ways. The 1st 1 I want to introduce is container registry continent registry especially for Alibaba cloud. We call them the Alibaba cloud container registry and press edition. This one is used to stall your container images. Not only can stall your container image, but also it can start some other cloud native artifacts, like the How charts. What do you need to do is consider this and the central place to store your images. And at the same time, the ACR can support intelligent building, which means inside our SI saw it. We have some embedded build server to help you to build your application. Immediately after some soft code was changed. Not only we can do the auto build, we can also have the capability to set up ACR instance around the world so that you can always deploy the nearby registry for your business needs. When everything was generated the ACR, we also do the image scanning to make sure there's no vulnerabilities of safety problems in your images. Once the security check in the past, you can trigger some global distribution policy. With thousands or even millions of images the ACR can distribute using some P2P those kind of different mechanism to distribute them worldwide. Finally, if you also leverage the Alibaba Cloud Kubernetes of some other CICD tools to try to deploy the application in your different environment. You can just configure the trigger with called the web hook from the ACR to the ACK, so those kind of deployment can be ultimately triggered. So no matter the application environment is in cloud or in some IDC, you can always consider this kind of life cycle chain can be implemented automatically. By using ACR you can not only store your images globally, but also you can turn the whole DevOps value chain into a new one called the DevSecOps, which means you are emphasized in hiding more security features into your whole DevOps process. For contingent rather shape, I'll give you one simple question, which of the following features are unique to Alibaba Cloud Container Registry, as compared with Docker Hub? We all know that Hub is the community version for the Docker Image Repository. Let's check out the options one by one. Container Registry can ultimately build new Docker images when source code changes. Mm-hm, it looks like a good one. For source code hosted on websites outside China, the CR can use servers outside China to build the image, even when you are using hundreds of mainland China. This one looks good to me actually. You can create and delete image repositories in different regions based on your needs, maybe, I never know the Docker Hub has this kind of feature. So you can start the image repository access to public or private. This one I think most of the repository has this function. So comparing to some other two options, I think my choice will be B and C. Another cloud native solution to deploy application is called ECI, it's Elastic Container Instance. Comparing ECS, Elastic Continue Instance, we call it a civilized solution, because now the application is directly deployed into a container and the user you don't need to worry about the several measurement efforts. Also at the same time, we maintain a very stable and resilient system on the back hand to make sure the whole resources to support the ECI is stable and also cost the civic. Another benefit you can gain by deploying the application into the EC I is in the future. If you have some other requirement, you can easily integrate ECI into the Kubernetes clustered, which means in Alibaba Cloud, if you are running a serverless Kubernetes you can consider the ECI at the backbone of a serverless Kubernetes cluster. Or if you already have existing Kubernetes cluster, you can us in the virtual node mechanism to integrate some existing ECI into it. And all these kind of features, the conservatives, they have the same open APA. Regarding the different scenarios, ECI can be used definitely online service. Again, if you deploy application into a container like the ECI, it can immediately gain the benefits what the Kubernetes can also provide, like the HPA. And also based on some even to driven mechanism considering to use the ECI into your IoT or some video coding, decoding those kind of scenarios. Resiliency is to say for the CI/CD environment, you can always integrate the ECI with some Jenkins or Gitlab, those kind of 3rd party CI/CD tools to make your whole developed precise. Also considering the ECI and the computing unit, it can be used for the data processing scenario and also for your personal and the QA purpose test, you can use it to set up some testing environment together with the freedom or some other testing tools. So all in all ECI comparing to ECS it is a container based solution, sometimes we call it a serverless solution. It give you an application to be deployed into the container directly so that it can be integrated with some other Kubernetes clusters. One simple question I can give you here for ECI is, which of the following data volume type is not supported by Elastic Container Instance? If you have been using it for some time you will know that some of the terms in these options are made up actually, so emptyDir, NFS, confligFile, fixedVolume. So actually the option D is the right answer, there's no something called the fixedVolume. Now let's look into another cloud native solution for your application deployment, it's called a Function Compute. Alibaba Cloud Function Compute is a fully managed event driven computing service. With Function Compute, you can focus on writing and uploading code without the need to purchase and manage some construction resource such as UCS Function Compute prepares computing resources for you. So you can always run your service or your code in an elastic and reliable way. Alibaba Cloud Function Compute will do the elastic deployment ultimately to distribute and duplicate your code to finish the job as soon as possible. So with Function Compute you can quickly create any type of application and the services and only pay for the resources that actually consume when you draw your code. This chart is showing you the simple steps to make a Function Compute can work for you. The first step is to just create a service, from that service you need to create some functions because the service is composed of the different functions, then you can decide what you want to do to trigger your code. You relate, we define something called trigger, right? You can define to use the trigger or not. And finally, when some event with hate, the trigger will trigger the execution of your functions, and the function compute will do the log of your all Function and also it will generate some monitoring data for the whole service. This is the whole process about using the function compute in the Alibaba cloud, very direct, very simple. Now let's look into one question if you have a no. Dot Gs based application and you can plan to migrate to Alibaba cloud function compute which of the following steps is unnecessary. Again, let's recall the previous chart. Let's look into the options one x 1. The first one many we installed the note Js package in the function computer council. Create a simple application and upload the Karsten code really the found computer council complete program started out command. And excess parts in the compute started verify application. I would say the option A maybe the choice because considering the function compute. We provide a lot of different environment and programming language support, which means you do not need to manually install it by yourself. So the option A is red answer. Together with the function compute. Another option we want to introduce for your application deployment is called the serverless workflow. From the chart shows here you can see the major purpose of Solar's workflow is to be able to integrate the different function compute master of service. And to organize them into a workflow so that you can just define what kind of logic you want to go through for the data processing. Or your whole business logic and finally, after all these steps was executed, you can reach the desired results. Together with the civilized workflow and function compute you can also implement the following scenarios like the data processing. Ultimately the operation and management, machine learning media processing and some orders approval. So let's take the orders approval an example because our service workflow can support the transactional flow or transportation. Because in complex scenarios that involve the older management such as the E commerce website, hotel booking. All the flight reservation applications need to access multiple remote services and have high requirement for the optional mathematics of transactions. In other words, all steps must succeed or fail without intermediate status. If obligation with small traffic and centralized data storage, automatic consistency, isolation and the durability. Those properties you really need to be done by the original database but in a large traffic scenarios. Distributed micro service are usually used for the high availability and scalability to guarantee the reliable, precising of multi step transactions. The service provides. You really need to introduce cubes and persistent message and display the flow status to the whole architect. This brain additional develop an O and M cost. So considering using our civilized workflow, it can ensure the level processing of distributed transactions in complex flows. And therefore can help our developers to focus on their own business logic. So let me give you one example the simple question of service workflow. If you have a chance to use the service workflow, it allows you to orchestrate distribute tasks in sequence. Branch and a parallel mode and ensure that task reliable called according to work flow logic. Which of the following service integration mode is not supported by civilized workflow here is some of the options the request responsible. Synchronization mode is international mode and waiting for callback mode. So actually the option is C the in synchronized mode. We don't have this kind of more defined in the serverless workflow. Now, let's look into lots of product in this section. API Gateway, API gateway is an API hosting service, it provides a full range of lifecycle measurement of functions. To help build an API centralized system architect. The lifecycle measurement function includes the API design, development, testing, population, operation management. Monitoring all these features you can consider to define API lifecycle by releasing the API on the Alibaba cloud marketplace. You can also provide the capabilities, services and the data to a wide range of developer for purchase. And use our API gateway allow you to provide API for a variety of scenarios. For example, you can establish an ecosystem for capability sharing and economy development. Enterprise must explore new business model to solve various scenarios, specific problems of their customers. So with API Gateway standard API service are provided that allow other developers to integrate some or all API into their own application. This opens up new services, help enterprise established new business ecosystem and promote a cross section innovation. Another scenario you can consider using the API gateway is you can secure the implementation of multi terminal unification for single service. With multi terminal output just like the picture shows here and mobile and IOT devices become increasingly common EPI's. Are now required to support more types of terminal devices to expand the business scale, which also increased system complexity. Using API gateway, you can adopt any PS two multiple terminals by adjusting the API definition in API gateway without additional configuration needs. You only need to maintain a single service system that can provide output to multi terminos. The last scenario is you can use API gateway to do the easy system integration and standardization with API gateway. You can standardize your own inter system interface and apply pre standardized interface for this system integration. You can quickly integrate and mining resources, minimize the resource, waste and operation redundancies. We're focusing only on the channeling resource for the business development. Now let's look into one simple question for API gateway. Which of the following steps is not mandatory when creating API through the API gateway. If you have a chance to use the API gateway before you may quickly found out that actually in the API gateway. You do not need to attach a dominant name by yourself. So API gateway can manage and provide this domain service naturally. And other steps like the defined API information defined parameter and define the back end service. These are all the necessary steps. So the answer will be big for now. We reached the end of this section of this chapter. Talking about when you deploy application into Alibaba Club. Which kind of product and service you can choose from. Remember we have the CS and the most commonly used the virtual machine together with container registry and the CI. You can turn your application to a containerized application and put it in even lightweight, continually environment. And you really want to try our soldiers solutions or cloud native solutions. You can try our function computes and also civilized workflow to organize the function together. And API gateway is a centralized and unified gate to put the backhand service together. And provide unified endpoint to the client to migrate the application from the 3rd party of physical machines. You can using our server migration standard too. I think the data to the cloud and the generated image automatically in the cloud. Okay, this close this chapter to deploy application on cloud. Thank you for watching and looking forward to seeing you in the next chapter.
