With the launch of Krypton APP, the number of registered users has shown an explosive growth, and user identities and their corresponding use scenarios have also been expanding. In this process, the experience of APP users has become more and more important. How to ensure that the APP can meet the three high scenarios of the Internet, as well as the stability, fluency, and agility of rapid response needs while the user scale is growing rapidly has brought certain challenges to the research and development team of Krypton App.
- High requirements for business continuity
The core APP services such as remote car control, online map and 3C mall are very demanding on business continuity, and they all need to be online for 7 * 24 hours. In particular, in the face of peak season sales activities, new model releases, hot emergencies and other situations, the APP is facing high concurrent and large traffic pressure. There are some functional failures, pages cannot be opened, and interface delays are too high. In extreme cases, the APP is completely inaccessible, which has a serious impact on user experience.
- Version release pressure is high and frequency is fast
With the increasing demand for user scenarios, more and more functions are waiting to be released and launched, and the requirements for iteration frequency are getting higher and higher. However, due to the lack of full link grayscale release capability on the APP server, in order to ensure the stability of the business, customers can only choose to release each time in the low peak period of the business in the early morning. Students in development, operation and maintenance, and testing suffer terribly, It is urgent to realize the ability of lossless release at any time.
- Technical architecture urgently needs iteration
At the beginning of the company's establishment, in order to meet the business and realize the rapid launch of APP, the overall design of the technical architecture was slightly inadequate, which was reflected in many problems such as high coupling between some businesses, long system links, different technical implementation standards, and unreasonable cloud product selection. For example, through research, it was found that the request link of a core interface was too long, leading to high latency jitter rate, It affects the user experience.