Shulou(Shulou.com)06/02 Report--

Lecturer introduction

Hao Renjie, Amap wireless development expert. The evolution and practice of Amap's ArchSummit architecture in recent years were shared at the 2019 App Summit, which ended on July 13.

Background Overview

Gaud is a leading solution provider of digital map content, navigation and location services in China, with two main lines: mobile phone and car phone. In recent years, with the rapid development of Gaode business, the rapid expansion of personnel scale and the rapid expansion of code, how to improve the team's ability of efficient parallel operations, the end architecture has made a lot of attempts in terms of consistency and dynamics: from the initial double-ended native single architecture, to the sinking of the map engine, to the construction of the dynamic UI framework, it has achieved certain results, but in the face of the sustained and rapid development of the business. There are still many aspects that need to be improved.

In order to allow business development to proceed rhythmically, some bus plans are made on the project every year. The bus is each App version, the goods is the corresponding product function, the goods assembly is the function development, the bus plan is the annual release plan, the bus pulls away the assembled goods according to the specified time. However, due to the large difference between the two ends of the code, serious coupling, low reuse rate, unclear responsibilities, poor platform tools and other problems, the bus could not pull away the goods as planned, and the goods were assembled slowly and of poor quality, forcing the bus to wait. As a result, the entire version effect cycle is as long as 3 months, the collapse rate is as high as 8/10000, and the bus becomes a fake bus.

Executive plan

In order to turn a pseudo bus into a real bus, it is necessary to solve the problems of double-end difference, code coupling and backward platform tools to improve stability, parallelism and efficiency. In 2018, the goal will be achieved through double-end integration, componentization and R & D center construction.

Double-end fusion is realized by sinking C++, floating dynamic UI and double-end alignment. Sinking Craft enables cross-platform while improving performance; floating dynamic UI also achieves cross-platform and lowers the development threshold, making development simpler and more efficient, while laying the groundwork for future dynamic; double-end alignment is more likely to learn from the advantages of both ends to achieve integration, while retaining the differences between the two ends as an extension, so as to maintain consistency as far as possible, but also well compatible with the characteristics of the Android/iOS platform.

Componentization refers to mature container solutions such as handy Atlas, BeeHive and NetEase LDBusMediator, and integrates Gaud's own business characteristics and design thinking, and defines containers, modules, micro-applications, micro-services and page routing. Draw lessons from the Android component-based design idea, let the business focus on its own needs of services, without paying attention to other.

Through the layering and grouping of the architecture, the attribution and responsibility of the module are made clear.

The container provides the module with its internal structural framework, architecture layering and grouping to find its own location. The combination of the two realizes the componentization on the end, decouples the code, improves the reuse rate of functions, and lays the foundation for business parallel development.

According to the current bus process, combined with the component scheme, the R & D mid-Taiwan construction has developed a new detailed process of production, research, test and item, which reduces the risk, improves the efficiency and realizes the parallel research and development.

Practical income

Double-end fusion, solve the consistency problem, improve the stability of App; componentization, solve code coupling, improve the reuse rate; R & D middle platform construction, the process automation and standardization, while combined with components, to achieve the parallel development phase, to achieve a real bus. The publishing cycle has been cut in half.

Through targeted code quality governance and platform control, the collapse rate is reduced from 8/10000 to 8/100000.

Through the product-based integration after tool upgrade and componentization, the packaging time is reduced from 40 minutes + to 8mins.

Prospects for the future

In 2018, the Gaud client changed from a fake bus to a real bus through a series of architectural governance, but this is only a phased achievement of the evolution of the architecture in recent years. In the future, we should give full play to the advantages of dynamic UI to make the business really dynamic, from the bus era to the Feature Team era, so that the bus becomes a road, and each Feature Team is a car. After loading the goods at its own pace, we can drive freely on the repaired highway to achieve better flexibility, parallelism and efficiency.

Conclusion

Welcome to scan the Gaode technology official account to pay attention to more Gaode technology and details, and welcome you to join us to explore the evolution of Amap's App architecture!

Pay attention to Gaode technology and find more professional content in the field of travel technology.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.