Those things moved to the cloud

Cloud Times:
cloud era has arrived, after selecting a cloud, the first question is what kind of business the way choose to migrate the cloud? This affects the quality of business services companies after the migration cycle and migration, so be sure to follow certain methodologies and processes, rather than blindly migrate migration. It should also comply with the basic five processes: planning, design, migration, operation and optimization, you can fine-tune them according to your actual business situations in which this methodology.
All cloud vendors inside, AWS has the most complete migration methodology. For example: CAF (using cloud framework), LandingZone, Well-architected (good infrastructure) and three days migration training courses that will enable you to realize that the use of cloud will be what kind of mode, you use the process to solve the doubt. Personally I think that a methodology AWS primary user CAF learn more critical, which would allow you to have a better time for cloud experience.

Those things moved to the cloud

Learn from our past experience, we advise clients to have a small amount of applications on AWS later, again read Well-architected , more technical terms Well-architected, it is recommended that a preliminary understanding, the simple application of practical, late in practice, the process of continuous consolidation of knowledge point to grasp the essence of the part. Of course there are ways to shorten the learning time, that is to choose an experienced AWS Partner as well as a detailed explanation to accompany you to the cloud with their practice, they tell you what they are based on best practice business operating conditions of your business.

Those things moved to the cloud

Practice sharing:
According to our experienced migration of a large number of practical work, let us share in the migration process together, the two most critical stages, namely planning and design. They migrate throughout most basic part, just like the foundation of a building, how do the detail work of these two phases, we explore together, hoping to help you and your business.

1) Program:
advice before making plans, do a migration priority list, which must include several key fields, such as: operating system version / actual amount of data / application providers / business depends Services / complexity of technology / RTO / RPO, etc. these are decisions that you choose what kind of migration patterns (smooth / replacement / reconstruction), what kind of migration tools, because they will affect your migration cycle length and the effect (of course there are some companies, there are some special indicators, For example: compatibility (moved to the possibility of other cloud)). Please fill in this table complete, do the whole migration plan, rather than making plans without any basis in the case.

Those things moved to the cloud

According to the above indicators, perhaps you will feel the operating system version is not important, in fact, very important, we must first know AWS not to support this AMI, if AWS does not provide, Marketplace and community there? (If you're very focused on safety, it is recommended not to use the community AMI) You can also choose to make your own AMI (choose Vmware method of making), but our advice is to use AMI AWS offers, so does not manage the performance, stability, features and troubleshooting will be more reliable. For practice we had a case of the communications industry: the customer in front of the AWS, AMI has to be simple functional testing, performance testing and not for them to modify the kernel in On-premises CentOS of AMI. Found various failures during performance testing after the actual migration, this time after-sale technical AWS also can not be solved. Based on our experience we recommend that you try to use AMI AWS provides, if indeed there are very strict requirements for AMI, then please do all the necessary tests. Application providers, this is not migrate applications can play a decisive role, such as: License, version, and whether there are software providers? Businesses depend on service, this indicator describes the data exchange between business, tightly coupled relationship between business, the existence of the interactive service data or how much they are merely data providers other businesses between them, please note that "in fact sometimes other services rely only on the data in the database business, and does not depend on the business itself, " so there is no business relationship does not exist. RTO / RPO , this indicator will determine the cost of migration, to maintain uninterrupted service, the more expensive the cost of migration. According to our practice through experience, RTO / RPO more appropriate backup and disaster recovery scenarios, the migration scenario we believe that business can be interrupted for more critical because it is used for time synchronization and data service switching, the most important It is: "Please do not think that their business can never be interrupted" (migration costs caused by such waste, even not migrate). There are three factors related to the length of time of the decision to migrate are: data synchronization technology, network bandwidth and data volume size.
The above indicators, as well as the customer's own requirements indicators do related assessment and verification (the next phase of the "design" is at this stage "plan" the most important verification test) to determine the priority of business migration, business migration patterns, tools business migration, business migration time.

Those things moved to the cloud

2) Design:
Once you have more than well established migration priority list, this phase will be the architecture design and verification testing, as well as to ensure that migration patterns, migration tools and migration preference right, which explains the design and planning is the role of nexus, and They are not independent. Through business analysis and assessment phase of the program, you can already make the appropriate architecture design, and related verification test (in the cloud era, this is very important) to adjust the priority of migration and migration patterns . The more at this stage to verify this business, the less risk migration phase, the shorter the time. For example, after one of our high-tech manufacturing industries, before they assess the existing AWS with us in a cloud vendor's business structure in detail and analysis, the verification of their most crucial test in the use of an alternative migration patterns EC2 is a web-based K8S and VPC, so different from these fully tested, such as: License validity period of K8S, K8S of Autoscaling, K8S into different business groups and K8S network testing, as well as doing some business-critical migration test. Save two weeks due to the design phase fully tested when making a formal migration. If possible, we suggest using the production environment 1: 1 verification test environment, and after verification is complete, you can put the resources Stop, then and only pay part of the cost of resources such as: EBS, EIP, S3 and so on. For those resources that must be removed, you can choose to do first backup to prepare a formal migration, and can be used Cloudformation make templates, which can reduce the migration official preparations.

Those things moved to the cloud

Practice Summary:
Many companies prefer not verified or validated by a small amount, they begin to perform the migration, a variety of problems encountered in the implementation process, some of the problems that they can not continue, we must start from scratch. From our past experience is concerned, the proposal should first simple business cloud migration, smooth migration are the best, the best the first two stages make full verification test preparation. Some did not interrupt the service (DNS domain name actually need to switch or interrupt a few minutes) synchronized fashion design good data (mainly data synchronization database, you can use AWS DMS database designed for real-time synchronization or third-party software), here the data synchronization will be some delay, traffic may be considered to bear the delay range. We must remember and understand that there is a strict relationship between each stage.

Those things moved to the cloud

Migration, operation, optimization of these three stages is critical, and in the first two phases of the migration well prepared, the migration phase will be relatively easy, just pay attention to risk assessment and staff assignments, operate and optimize belong to the advanced stage , business migrated were gradually optimized in terms of stability, performance, security, availability, and cost. (This article for any errors, please correct me, thank you!)

Reference to learn Address:
https://d0.awsstatic.com/whitepapers/AWS_CAF_Security_Perspective.pdf
https://aws.amazon.com/cn/architecture/well-architected/

[About Booz cloud]
Those things moved to the cloud
as a professional cloud computing services-oriented enterprises, Booz cloud for customers to provide operational services on AWS: include architecture consulting services, migration services, cloud security integration services, hybrid cloud management service, big data services and DevOps service. Currently, Booz cloud vendor certification has been made in big data, DevOps, architecture, databases and operating systems, with branch offices in Shanghai, Nanjing, Hangzhou, Wuhan and other places. Innovative service model, lead the development of IT services, Booz cloud will continue to invest resources to carry out intelligent hybrid cloud management platform, the map database of research and development.

Guess you like

Origin blog.51cto.com/703356/2405125