您当前的位置是:  首页 > technology > Corporate communications > technology > cloud computing > Applications >
  Home >technology > Corporate communications > technology > cloud computing > Applications > Zhejiang Mobile's first production and application based on Alibaba Cloud technology was successfully launched

Zhejiang Mobile's first production and application based on Alibaba Cloud technology was successfully launched

2018-05-11 11:03:01 Author: Source:CTI ForumComment:0  Click:


  I. Project Background
In order to implement the company's "Thirteenth Five-Year Plan" strategy and establish an "IT framework with advanced architecture, efficient operation, and internal and external considerations", Zhejiang Mobile has recently been entrusted and guided by the Headquarters Information Technology Center to explore new cooperation models between traditional enterprises and Internet companies and track the development of the industry. The trend, to carry out new technologies, new product research and innovation, for the first time in the group to join Asia's largest cloud computing company - Ali cloud, on the basis of "regulatory management can be based on operation and maintenance", the introduction of third-party basic components to introduce pilot verification.
Second, implement the strategy
After many discussions with Alibaba Cloud Engineers, the Zhejiang company decided to adopt a phased implementation and a quick pilot to reduce intrusion on applications while taking into account the actual effects, considering light-weight system verification and introduction of key services. The pilot is specifically divided into multiple stages of execution, one of which is aimed at quickly landing verification technology components.
The general principle of the first phase is to quickly verify the application of the Ali-Cloud DRDS Distributed Relational Database Service component in the M-domain pilot application to experience Tmall's dual 11-core transaction business and various types of business challenges. Management "Application of migrating DRDS short-term fast" function verification, development to minimize the transformation to achieve DRDS "sub-library sub-table", "smooth expansion" and "differential operation and maintenance." After the completion of the first phase, an evaluation report of the reform is issued to provide reference for the implementation of the second phase.
Third, a stage summary
In the first phase, the “Uniform User Management” system was selected as a pilot. This application originally used the common front-end and back-end integration architecture for traditional small and medium-sized applications. The original database was PostgreSQL. With the continuous development of the business, the traditional infrastructure of the "Uniform User Management" system is constantly undergoing challenges. Among them, the single-point bottleneck problem of the database is particularly prominent. There is a single-bank capacity bottleneck, expansion is difficult, secondary development is difficult, and performance problems are difficult. Many problems such as optimization.
1. Before and after the transformation, the system deployment architecture is compared as follows:
Figure 1 - Original Unified User Management System Deployment Architecture
Figure 2 - System Deployment Architecture for Unified User Management Access to DRDS
2. Earnings after implementation in one phase:
The application itself only needs a small amount of interface adaptation to access DRDS. The benefits are a series of outstanding features brought by the distributed database:
1) Sub-library sub-table
Supports database sub-division tables. After a distributed database is created, split rules can be set according to service characteristics to achieve data splitting.
2) Transparent reading and writing separation
By using a read-only instance to achieve read/write separation, the read load capacity of the cluster can be increased at a low cost, the pressure of the main library can be released, and the service code can be transparent without modification; and at the same time, it has the capability of consistent reading.
3) Data storage is smoothly expanded
When there is a bottleneck in data storage capacity and access volume, online storage capacity expansion is supported, expansion is not required for application transformation, and the expansion schedule supports visual tracking.
3. Challenges in the implementation of a phase:
"Uniform user management" as the first application of access to the pilot, in the implementation of a phase in the process of how to solve the incompatibility of the database grammar, how to develop a split plan, how to solve the distributed transaction and other issues, and one by one to overcome.
1) From PostgreSql to DRDS
Application of the original database selection PostgreSQL, and DRDS currently only seamlessly docking Mysql. Therefore, the application must first complete the database switch and solve the SQL dialect or feature differences between databases.
The development team started with the code logic, completely replaced the incompatible data types, and continuously analyzed the efficiency of SQL execution and detailed optimization in the functional testing to fully prepare the application for subsequent access to the DRDS.
2) Sub-table splitting rules
There are several tens of millions of core large tables in use. When moving to DRDS, it should be handled in accordance with the three-step principle of "determining business entities - finding key fields - calculating the number of sub-database tables."
Take the work order operation attribute table as an example. All operations of the work table are performed around the work order operation, so the applyopid (work order ticket number) is selected as the split key. In the future, the estimated total amount of data for this table for 1-2 years is 60 million lines. According to the following formula, this table can be obtained according to the sub-libraries and the two sub-tables for each sub-library:
Single Library Physical Tables = CEILING(60,000,000 / (1 * 8) / 5,000,000) = 2
Figure 3 - Description of the Rules for Separate Library Tables
3) Distributed Transaction Practice - Global Transaction Service (GTS)
After splitting several core large tables of the application, the data originally stored in the single bank table is dispersed into multi-database tables, so the application will involve distributed transactions when writing related data. .
The traditional solution for distributed transaction management is based on the two-phase commit method of the XA protocol, which requires targeted development, intrusion of existing service logic, and poor performance.
After a comprehensive assessment, it decided to introduce the Alibaba Cloud Global Transaction Service GTS. GTS has the characteristics of simple access, seamless connection with DRDS, and no intrusion to business logic, effectively solving a series of transaction control problems caused by database split.
Figure 4 - Diagram of access to GTS deployment in the "Uniform User Management" system
IV. Construction process
The first phase was approved in early February of this year and officially began after the Spring Festival. Under the sincere cooperation of Zhejiang Mobile and Aliyun, only a month or so ago, the pilot application was successfully launched. Milestones for major projects during the period are as follows:
  1. In early February 2018, the project was completed before the Spring Festival and the project was officially launched after the Spring Festival.
  2. At the end of March 2018, the system successfully migrated the database to MySQL.
  3. At the end of April 2018, the system completed the production data cutover and officially entered DRDS.
Fifth, extend thinking
This cooperation is the first in-depth technical cooperation with the advanced Internet companies in the industry within the China Mobile Group. Based on the Group's “supervising, manageable, and maintainable” concept, it has passed the reform and practice of the pilot business in the first phase, and the The operation and maintenance mode, operation and maintenance tools, and integration schemes have been blended, accumulated, and precipitated valuable experience. They are also in project collaboration and architecture matching, and have initially verified the feasibility of combining advanced technologies and concepts of Zhejiang Mobile and Internet companies. Subsequent second and third phases laid a solid foundation for more in-depth pilot work on the core system of Zhejiang Mobile.
  
[Disclaimer] This article only represents the author's own opinion and has nothing to do with the CTI Forum. The CTI Forum maintains its neutrality in the presentation of statements and opinions, and does not provide any express or implied warranty for the accuracy, reliability or completeness of the contents contained therein. Readers are for reference only, and please bear full responsibility for yourself.
0

Topics