I wrote about this in my previous article, "TheCloud Computing - Virtualization - OpenStackAs we talked about in the article, the essence of cloud computing is a sharing of IT resources through virtualization, a higher dimension of services. The essence of cloud computing is two words:enjoy together、service。
1. Recommendations for enterprises to go to the cloud
As an IT industry for more than 14 years of the old rod, personally led several companies in the medium and large-scale systems from the IDC server room migration to the cloud. Cloud this thing, is an inevitable trend, and I have always been supportive of the attitude, there are 2 reasons:
- The future of the enterprise must be focused on their own business, and then do a good job of sales and service, in order to continue to develop. IT infrastructure, this thing, must not become a point of obstruction to the development of the enterprise, this thing will be more and more by the cloud vendors to undertake.
- The AI era is coming, many developers will gradually become super individuals. Whether it's a micro-enterprise or an individual, it's important not to invest too much in the IT infrastructure thing, it's still about finding the right cloud vendor and then focusing on your own business.
For inexperienced organizations, rushing to the cloud may bring unexpected potholes, such as: budget overruns, performance degradation, service outages, and other problems. I've summarized some guidelines for avoiding potholes when enterprises go to the cloud, and I hope they will be helpful to you.
2、Enterprise cloud purpose
Enterprises go to the cloud for the simple purpose of handing over their specialties to cloud vendors and focusing on their business themselves. Rather than going to the cloud for the sake of going to the cloud, or just for a momentary price advantage. I've seen several businesses go to the cloud for unknown reasons.
Many organizations go to the cloud, often considering only some of the costs, which I think is putting the cart before the horse a bit. The purpose of going to the cloud is toTo focus yourself on your business, don't expend too much energy on IT infrastructure.
Of course, the cost has to be considered as well, and the cost is divided into 3 main pieces:
- Virtual machines or resources on the cloud. Overall, if you only look at the number of VMs consumed or the amount of resources on the cloud when the prices and policies of cloud vendors remain unchanged, the price of going to the cloud in the first three years is definitely more cost-effective than building your own IDC room, and the resources on the cloud in the later years may not be cheaper.
- Labor Costs. If the IT infrastructure goes to the cloud, the organization will save a lot of labor costs in architecture and operation and maintenance.
- Flexibility costs. As a business grows, it will keep exploring new business or doing marketing campaigns. That elastic servers on the cloud can save a lot of cost for the business.
3. Core Steps to the Cloud
Going to the cloud is a complex and long-term investment project that involves not only technology, but also cost management, security compliance, teamwork and other aspects. Therefore, enterprises must be well-prepared and well planned in the process of going to the cloud.
While the process of going to the cloud is long and relatively trivial, there are a few core steps that must be done to avoid many pitfalls in the process.
3.1 Resource planning
List all the types of resources needed, resource specifications, such as how many cloud servers what configuration, how many K8S clusters, what configuration of databases, what configuration to use for ES search, and so on.
Once the resource list is done, you need to compare the prices of various cloud vendors based on this list. The resource list format is as follows:
3.2. Hybrid or multi-cloud strategy
After listing the resources, it's a matter of synthesizing whether the overall migration to theA certain cloudUp. Still.IDC + a cloudof hybrid solutions, or to avoid being kidnapped by a particular cloud vendor and adopt acloudy (meteorology)Strategy.
3.3 Network planning
Network planning is a very important step, we must do a good job of planning in the early stages, face to the later stages of the network segment confusion, bad management.
Generally the environment on the cloud needs to be connected to the local office environment, and if a hybrid cloud is involved, it also needs to be connected to the IDC server room. It is also necessary to distinguish between production environment segments, operation and maintenance segments, development and testing segments, and so on.
3.4 Consider data migration
Plan all the preparations for data migration before going to the cloud.
- Data migration program: how to migrate from the original server room, to the cloud, generally cloud vendors will provide migration tools, if there is no migration tool how to migrate.
- Timing of data migration: choosing whether to migrate data with nightly downtime, or synchronized dual-write switching, etc.
- Time Consumption of Data Migration: When migrating data, it is important to consider the bandwidth required and the time consumed to avoid migrating too late, resulting in business interruption.
- Data Migration Integrity: Think about how to ensure data consistency during migration to avoid business damage.
3.5. Consideration of project modifications
Whether the project needs to be revamped or not needs to be decided based on the deployment scenario and data migration scenario.
It doesn't matter if it's a monolithic architecture or a microservices architecture. It needs to be a Docker + K8S deployment option, then the project needs to be Dockerized. If it's a VM deployment scenario, it may not need to be revamped.
If the data migration scenario is dual-write, then the project will need to be retrofitted in order to adapt to this scenario as well.
It's also possible that previous projects and data dependencies are confusing and not conducive to long-term maintenance, so take advantage of this cloud opportunity to sort them out as well.
3.6. Emergency Programs
In the process of going to the cloud, especially medium and large-scale projects, no one can guarantee that there will be no problems, so be sure to make a good contingency plan, such as a certain step fails to rush back, everything to not affect the business as the implementation guidelines.
Never take a chance and prefer to have an emergency plan ready to go that you can't use.
3.7. Strict CheckList
Before cutting on the cloud, be sure to set a good project leader, the project leader should develop a strict CheckList to ensure that the progress of the cloud in an orderly manner.
Going to the cloud requires a minimum of 2 core CheckLists:
- CheckList of the overall progress on the cloud, in the following format:
- On the night of the migration cut, the project leader must develop a strict execution action CheckList, for example: what time and what minute so-and-so does what specific thing, the more detailed the better, in the following format:
4. Completion
These are some of the core steps to the cloud, the table in the text can not be cut off in full, want to know more information about friends, welcome to add VX exchange!
The end of this article! Welcome to pay attention to, add micro letter (ylxiao) exchange, the whole network can be searched (programmer half a cigarette)
Link to original article:/s/HLpC-SUwjRKCkJ8EtM571g
Recently launchedKnowledge Planet《Developer AI Plus", an AI app development column designed to help developers with one more skill in these difficult and transformative times. And.1V1 technical consulting, clearing obstacles in the path of career development and technology. Early bird price of $9. Add a tweet (yclxiao) to inquire.
