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

With the continuous deepening of the use of Internet technology, production efficiency has been greatly improved in product research and development, supply chain management, market operation and internal scenarios. With the deep popularity of mobile Internet technology at the social level, the popularity of mobile devices makes enterprises become the best carrier of digital transformation. This article is based on the speech of Alibaba senior technical expert Ling Ming on the mobile R & D platform EMAS of Hangzhou Station of Yunqi Conference in 2018.

Cdn.com/fec63c4bb62109044fd895f711e8720d9930812c.png ">

At the Cloud Conference last year, we officially launched the mobile R & D platform EMAS. Through a year of development, we have completed the export of the infrastructure of the entire Ali Group's mobile terminal for external commercialization. My sharing today will be divided into four parts. First, I will give an overall overview of the EMAS platform, then release the latest open product matrix around the mobile network scenario, and finally introduce the solutions of Super App and Intelligent Operations respectively.

With the continuous progress of the whole digitization process, Internet technology has begun to penetrate deeply from the traditional consumer market to the enterprise market. Whether industrial or commercial, it also takes digital transformation as the core driving force to support the development of the next enterprise. In 2017, seven of the top 10 market capitalization companies in the world are Internet companies, so the experience of Internet companies in digital operation in the entire consumer market should also be said to be an important reference for traditional enterprises to carry out digital transformation.

Today, we take a closer look at Alibaba's digital ecological model, in fact, it shows a very typical four-tier folding ecology, whether it is the initial e-commerce business or the emerging financial business. In the first connection layer, Mobile Taobao and Alipay are the most important connection points for enterprises to connect consumer terminals, including enterprises to build a new type of consumer-oriented terminal interaction model. The second layer, a large number of products and services provided to consumers. The third data layer, based on a large number of products and services, we precipitate the core data, including user portraits, commercial portraits, credit system, risk control system, how to use these data to further expand the boundary and value of the business. The bottom layer is the elastic expansion platform layer based on cloud computing and big data supporting the upper business.

Taking a further look at Alibaba's technical architecture model, we can find that Alibaba's technical architecture model and the four-tier folding digital generation model I mentioned just now go hand in hand. Including the first layer of the mobile center-mobile R & D platform EMAS, including the business center, including the data center. The business center carries general systems such as commodity centers, while the data center carries a general real-time and offline computing platform. At the bottom is the platform layer built by middleware. What role does the connection layer play in such a huge digital ecological map? The premise of digital operation is digital management, which helps to establish a directional interaction model between consumers and enterprises. In such a huge digital ecological map, the connection layer actually plays such a role, and is the core entrance and business carrier of enterprise user traffic, so this is the first step of digital transformation. The core goal of mobile R & D platform EMAS is to help enterprise customers complete the intelligence and data of the entire business connection layer, which can help enterprises establish the corresponding business model and corresponding technical support for the next stage of business growth.

This picture is a panoramic view of the entire mobile R & D platform EMAS products. EMAS is divided into five parts: the first part is the development kit, this layer precipitates customer components and terminal components, including UI picture components, routing components, network libraries, etc., as well as cross-platform development framework and H5 container. Based on the development kit, including enterprise developers to help complete the development. The second layer is the infrastructure layer. We have developed a large number of mobile infrastructure coupled with mobile APP and business, such as data analysis and a series of business-coupled infrastructure, which are opened through this layer. The third layer is the R & D support layer, which provides a continuous delivery work system around the entire life cycle of APP, helping enterprise R & D personnel to one-stop principle code hosting, code scanning, continuous construction, including mobile terminal testing, and then to online grayscale release, production release and online operation and maintenance, through the whole set of continuous delivery workflow system. To complete the hosting and control of the whole life cycle of mobile APP. The bottom layer is the engineering concept layer. Through the EMAS platform, we hope to open not only the infrastructure of a series of applications precipitated by Alibaba, but also a series of soft business methodologies precipitated by Alibaba, including our R & D specifications for two platforms, including how we define an APP as an APP with excellent user experience. Alibaba has a lot of experience to pass on, including the performance, quality and index baseline of APP release, including how to build the organizational structure of enterprise R & D teams in different stages and different processes. The top layer is the solution layer. Based on the product portfolio and business methodology just introduced, we hope to help enterprise business students solve the pain points in some hot scenarios, such as how to do intelligent operations in mobile scenarios, including how to do marketing in mobile scenarios, and so on. This is the product panorama of the entire EMAS.

With the formal development of EMAS to the outside world, we have established corresponding connections with many enterprises. We also hope that EMAS can really help enterprises bring something different from traditional research and development, and bring real new value to enterprises, including new experiences.

How to help enterprises build a new foreground experience and help enterprises transform and upgrade their foreground business based on emerging mobile technologies such as AI, 3D and short video. It includes how to help enterprises increase the speed of business research and development based on our development framework, development suite and our infrastructure, and truly reduce and reduce the entire product cycle by more than 50%. Including the new model, facing a whole set of APP continuous delivery system polished in the past ten years, how can we help the enterprise reconstruct its traditional collaborative model among different functional teams such as product research and development, operation, operation and maintenance, testing, and so on? really help enterprises improve the efficiency of R & D operation by more than 500%. Including the new growth, based on the delivery model of our new products and the operation model of our new products, how can we help the enterprise to reconstruct its operation model in the consumer market? can really bring new momentum to the next stage of enterprise growth. This is something we hope EMAS can bring to enterprises differently.

After introducing EMAS, let's take a look at the new product matrix that we opened this quarter around the mobile network. Mobile business is a very important business form of online experience, the so-called online is a very strong dependence on the network, whether the infrastructure related to the mobile network is strong or not is closely related to the mobile experience. The bottom figure is Alibaba's mobile network infrastructure architecture diagram. Within the group, all APP network traffic is divided into two trunks, one trunk directly dissolving the CPA system, and the other backbone docking the mobile network access system to carry the dynamic network requests of the whole network. Based on best practices and business experience, we have today opened four critical infrastructure closely related to mobile APP, including mobile API gateway and message push. In fact, our message push has been open in public cloud scenarios for a period of time, and we have also completed the ability to specialize and privatize message push for external output. It also includes services for mobile configuration and control, as well as core engine channel services for unified access to the entire mobile network. Next, let's take a look at the applicable scenarios and product features of several new products.

The first is the mobile API gateway. With the continuous evolution of the micro-service process, the problem encountered by enterprises is how to control the back-end services. In the business scenario of an enterprise, there may be a large number of business scenarios, different R & D teams may develop back-end services, and sometimes suppliers may be invited to do corresponding development. Therefore, different back-end systems, the implementation of the entire infrastructure, including its communication protocols, are actually different. On the other hand, with the further evolution of the micro-service process, the back-end of the enterprise is split very fine. If you interact with the micro-service through the terminal device, the network interaction will be very heavy for the terminal device, which is very unreasonable. In addition, all business requests are actually the same work, including authentication, current restriction, encryption, acceleration and so on, so we need to monitor the full gateway traffic from the first layer of the API gateway. Such as authentication, current restriction and other work, all have to be carried through the API gateway, and then put the inherent traffic into the back-end micro service system. At the same time, one-click choreography and service governance around API are also completed through API gateways to save R & D costs. The dynamic traffic of our whole network is to the mobile API gateway, while the API gateway also supports the general RPC framework, and its back-end business system is docked. In terms of performance, we all have a special team of network experts to optimize the network optimization and connection in the mobile network scenario. Architecturally, the entire API gateway architecture also applies to the front-end access architecture under the "Singles Day" system of Alibaba Group, which means that we can support zero-point pulse traffic and first-level concurrent connections like "double Eleven" very smoothly. In terms of security, we also implement a custom encryption algorithm based on the 1.3framework, which is greatly improved compared with the traditional HTTP algorithm. We can help enterprises to achieve the separation of front-end architecture, to achieve the architecture system, at the same time, in terms of maintainability and stability, can also be greatly improved.

The second part is the remote configuration service. The requirement scenario that the terminal R & D personnel of enterprises often encounter is that they need to change the parameters of the back end in real time to realize the real-time change of the behavior of the APP terminal and its external end. For example, at present, we need to dynamically deliver goods or pages based on the user's portrait and a series of user clicks, browsing and searching behaviors at the terminal at this point in time, such as some terminal switches and other scenarios. How to systematically organize and manage these configurations and ensure the timeliness and accuracy of these configurations? this is the focus of today's remote configuration service. Some students may say that this is not a very simple configuration to send and push the scene? If you use a sentence to describe all its work is indeed such a scene, but if you look at the details of the scene, you will find that there are a lot of details to be solved. For example, when configuring distribution, if you use push mode, you have to specifically configure a resource with a long link for remote configuration. In addition, with the continuous increase of the terminal volume, the computing cost of the server for a network-wide configuration is also very high, which will directly bring some challenges to the immediacy of the configuration. In addition, the remote configuration itself also needs to design a very helpful ACK algorithm, and at the same time, it also needs to design a very complex compensation mechanism, how to compensate if the first round configuration fails.

If we use the direct pull mode, it is also very clear how to set the interval for pulling at this time. If you set a long interval, it means that the immediacy of the entire configuration cannot be guaranteed. If the interval is set to be very short, the pressure on remote configuration to access the back-end service is very high, and more than 80% or 90% of the configuration queries may be invalid visits, resulting in a great waste of resources. Therefore, in the remote configuration scenario, we also choose the optimized push-pull model.

For the whole network model, we use the active pull mode, but the active pull mode is not the traditional mode, we will combine with the mobile API gateway. As you know, in the mobile scenario, the request for access to the API gateway is very high. Therefore, we will attach the configuration information to the API gateway to ensure the immediacy of the delivery.

For directed configuration distribution, we will still use push mode to promote the entire long link. In addition, we manage the configuration version data, index data and configuration content data in isolation. The version information will be managed on the server, and the real content information of the configuration will be managed on the CDN to further reduce the cost of configuration index calculation on the server and improve the immediacy of distribution. At the same time, through CDN, the bandwidth cost caused by configuration content pull can be further reduced. This is what the remote configuration service does.

The third part is the channel service. I just mentioned that whether the mobile API gateway, remote configuration or message push, the infrastructure that relies heavily on the network demands on the underlying network how to send data to the B end with high speed, stability and security. This is the link that the channel service is concerned about. Through the channel service, we hope to formally open the layer 4 access gateway service in Alibaba system for mobile scenarios, based on which enterprise R & D personnel can carry out upper-level research and development, and even carry out their own API gateway, message push and other scenarios. Such as traffic scheduling, load balancing, long link maintenance and other contents, are handed over to the channel service to complete. At the same time, the channel service will open up a unified client network SDK, which can further reduce the cost of network research and development for enterprise client R & D personnel. Some students may have some confusion about the location of mobile API gateways and channel services. Mobile API gateways are higher-level services that focus on one-click choreography and service governance of API, while channels are lower-level, pay attention to network details and do not have any business attributes.

After introducing our new products, let's take a look at our new open solutions. The concept of Super APP and Mini Program should be said to be the hottest topic in the mobile industry in recent years. Of course, this is also the definition of Super APP. There may be some deviations in the understanding of some students. I also said that only an APP with a mass of tens of millions or even hundreds of millions can be called Super APP, this understanding is a bit biased. Our definition of super APP now lies in the internal definition. The traditional mobile R & D model may evolve the demands of vertical scenarios into APP, including that APP may be implemented by different R & D teams and different suppliers, and the whole system and technical architecture are implemented in different ways. The result is the realization of the whole system, whether your traffic, your data, or your specifications are all fragmented and chimney-like, which is not conducive to the overall operation and maintenance, traffic operation and business linkage in the later stage. In fact, it is very appropriate for us to carry this type of scene through Mini Program, that is, today, a large number of business people are asking if they can help me build a framework similar to Taobao, Alipay and WeChat Mini Programs. So our definition of super APP today is actually that super APP is a Mini Program that can host Mini Program in different business scenarios. The goal of Super APP is to really help enterprises achieve unified traffic entry, unified operation strategy, unified business control and unified R & D norms, and really help enterprises achieve the aggregation of traffic and the reform of internal R & D efficiency.

What kind of technical challenges will we encounter to implement such a super APP solution? There are mainly two dimensions: soft and hard. To have such a super APP, we need to have a set of R & D tools and R & D specifications to help us restrict the connection of applet sub-applications in different scenarios to our super APP system. Just mentioned the hard part, we mentioned the need for a set of R & D specifications to help us at this stage of the traditional component-based APP to an applied APP architecture model transition. We have also developed a unified development suite here, including unified UI diagrams and scaffolding, which can constrain different R & D teams and suppliers to develop Mini Program applications in a unified scenario. The second is to provide multi-stack solvents to improve APP rendering performance and build an elegant and scalable Mini Program. The third part is around the underlying executive engine of APP, we provide the corresponding high-performance technical components, including network library, picture library, cache, routing framework and so on, which is also the core engine of the whole APP operation, and is closely related to the user experience of the entire APP terminal.

What I just mentioned is the technical hard core. In the engineering soft core, we also need a set of R & D specifications to define the entire APP Mini Program R & D operation and maintenance paradigm, including a unified DSL, to help enterprises complete the entire code quality audit and business control, including a unified communication protocol, to define the communication standards at the bridge layer, to complete the control and expansion of the entire API, including a unified release baseline. How to quantify the release standards around the user experience of APP and the performance, quality and baseline of the release, including unified environmental control, how to ensure that Mini Program is isolated from each other at runtime, including how to ensure the stability and security of APP at runtime. Including Mini Program's continuous delivery system, how to establish a unified Mini Program production line to ensure that different R & D teams and different suppliers produce small subprograms on your R & D pipeline, it is around the user experience or around quality, around performance, can be on a unified baseline, there will not be too much deviation. Through the two dimensions of technical hard core and engineering soft core, we can help enterprises to realize their own super APP.

The last part of the solution is the smart operations solution. Students who are familiar with EMAS should be aware that we have gradually opened mobile data analysis services in public and proprietary cloud scenarios, which can help enterprise personnel temporarily complete an one-stop data management platform for data burying, storage, reporting, calculation and display. How to further mine the business value behind these data based on such a data engineering platform? This should be said to be the core subject of the whole digital operation.

Taobao is also the first business scene in the industry to practice digital operation and precision marketing. Based on our very powerful data engineering platform, we can complete real-time massive terminal equipment data collection and cloud computing, and at the same time based on the input of industry knowledge templates, we can complete the corresponding data cleaning, data processing and modeling, which is the data training process we completed when offline. When APP is running, based on the powerful data engineering platform just mentioned, we can support the feedback recorded by a large number of devices in real time, and at the same time, based on the data model we calculated offline, we can build a set of corresponding accurate marketing and personalized recommendation system. Based on these systems, we can carry out accurate operations in some business scenarios, including thousands of people. We can predict users' purchase expectations based on user history browsing information, real-time browsing, clicking and search behavior on the current APP, and then deliver the corresponding products to users. Including in some non-tributary scenarios, we can view the click and purchase time of the user to display the items. Including targeted shipping and marketing, we can make corresponding matching based on user tags, and recommend targeted products for different people after they are triggered at a specific point in time. It includes that we can establish a model relationship between commodity pricing and sales volume for intelligent selection and intelligent pricing system. Through a set of precision marketing solutions, we can help business personnel to complete the operation cycle of a single flow in a closed loop, from the customer access to the touch of the flow to the realization of the traffic. greatly improve the efficiency of enterprise flow realization. In today's forum, our senior technical experts will also share Alibaba's best practices of intelligent operation and precision marketing in the digital age.

Author: mqc.yunos.com

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.