<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alibaba Tech on Medium]]></title>
        <description><![CDATA[Stories by Alibaba Tech on Medium]]></description>
        <link>https://medium.com/@alibabatech?source=rss-69f6dde768a1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*doanyR6AmLHe1ZcnauMrXw.jpeg</url>
            <title>Stories by Alibaba Tech on Medium</title>
            <link>https://medium.com/@alibabatech?source=rss-69f6dde768a1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:12:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alibabatech/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Java Agent Exploration — appendToSystemClassLoaderSearch Problems]]></title>
            <link>https://alibabatech.medium.com/java-agent-exploration-appendtosystemclassloadersearch-problems-6d77d94c7166?source=rss-69f6dde768a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d77d94c7166</guid>
            <dc:creator><![CDATA[Alibaba Tech]]></dc:creator>
            <pubDate>Fri, 17 Mar 2023 08:59:43 GMT</pubDate>
            <atom:updated>2023-03-17T08:59:43.945Z</atom:updated>
            <content:encoded><![CDATA[<h3>Java Agent Exploration — appendToSystemClassLoaderSearch Problems</h3><p>This article describes the exploration of strange error reporting in Java Agent, including Java Agent error reporting, JVM principle, glibc thread safety, and pthread tls.</p><h3>Background</h3><p>Java agents are enabled in multiple Alibaba Cloud products for users. Thus, the overall Java Agent duration increases, and each agent stores each other in scenarios where multiple Java agents are used together, resulting in increased memory usage and resource consumption.</p><p><a href="https://www.alibabacloud.com/product/microservices-engine">Microservices Engine (MSE)</a> initiated a one-java-agent project that can collaborate with various Java agents. It supports more efficient and convenient bytecode injection.</p><p>Among them, each Java agent, as the plugin of the one-java-agent, is loaded through multi-thread startup in the premain phase, thus reducing the startup speed from O(n) to O(1) and the overall loading time of Java Agent.</p><h3>Questions</h3><p>However, the following errors were found during the one-java-agent premain phase of the new version of Agent verification:</p><pre>2022-06-15 06:22:47 [oneagent plugin arms-agent start] ERROR c.a.o.plugin.PluginManagerImpl -start plugin error, name: arms-agent<br>com.alibaba.oneagent.plugin.PluginException: start error, agent jar::/home/admin/.opt/ArmsAgent/plugins/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar<br>  at com.alibaba.oneagent.plugin.TraditionalPlugin.start(TraditionalPlugin.java:113)<br>  at com.alibaba.oneagent.plugin.PluginManagerImpl.startOnePlugin(PluginManagerImpl.java:294)<br>  at com.alibaba.oneagent.plugin.PluginManagerImpl.access$200(PluginManagerImpl.java:22)<br>  at com.alibaba.oneagent.plugin.PluginManagerImpl$2.run(PluginManagerImpl.java:325)<br>  at java.lang.Thread.run(Thread.java:750)<br>Caused by: java.lang.InternalError: null<br>  at sun.instrument.InstrumentationImpl.appendToClassLoaderSearch0(Native Method)<br>  at sun.instrument.InstrumentationImpl.appendToSystemClassLoaderSearch(InstrumentationImpl.java:200)<br>  at com.alibaba.oneagent.plugin.TraditionalPlugin.start(TraditionalPlugin.java:100)<br>  ... 4 common frames omitted<br>2022-06-16 09:51:09 [oneagent plugin ahas-java-agent start] ERROR c.a.o.plugin.PluginManagerImpl -start plugin error, name: ahas-java-agent<br>com.alibaba.oneagent.plugin.PluginException: start error, agent jar::/home/admin/.opt/ArmsAgent/plugins/ahas-java-agent/ahas-java-agent.jar<br>  at com.alibaba.oneagent.plugin.TraditionalPlugin.start(TraditionalPlugin.java:113)<br>  at com.alibaba.oneagent.plugin.PluginManagerImpl.startOnePlugin(PluginManagerImpl.java:294)<br>  at com.alibaba.oneagent.plugin.PluginManagerImpl.access$200(PluginManagerImpl.java:22)<br>  at com.alibaba.oneagent.plugin.PluginManagerImpl$2.run(PluginManagerImpl.java:325)<br>  at java.lang.Thread.run(Thread.java:855)<br>Caused by: java.lang.IllegalArgumentException: null<br>  at sun.instrument.InstrumentationImpl.appendToClassLoaderSearch0(Native Method)<br>  at sun.instrument.InstrumentationImpl.appendToSystemClassLoaderSearch(InstrumentationImpl.java:200)<br>  at com.alibaba.oneagent.plugin.TraditionalPlugin.start(TraditionalPlugin.java:100)<br>  ... 4 common frames omitted</pre><p>Those familiar with Java Agent may notice that this is an Instrumentation.appendToSystemClassLoaderSearch call that reported an error.</p><p>First of all, the appendToSystemClassLoaderSearch path does exist. Secondly, the real reason for this error is in the C++ part, which is difficult to troubleshoot.</p><p>Anyway, we still need to investigate why this mistake occurred.</p><p>First of all, let’s sort out the specific call process. The following analysis is based on this:</p><pre>- Instrumentation.appendToSystemClassLoaderSearch (java)<br>  - appendToClassLoaderSearch0 (JNI)<br>     `- appendToClassLoaderSearch<br>       |- AddToSystemClassLoaderSearch<br>       |  `-create_class_path_zip_entry<br>       |      `-stat<br>       `-convertUft8ToPlatformString<br>        `- iconv</pre><h3>Input the Logs and Confirm the Scene</h3><p>Since this problem has a 10% probability of occurring in the container environment and is easy to reproduce, the latest code of dragonwell8 is used to add logs to confirm the scene.</p><p>First, add the log at the actual entrance of JNI, which is the appendToClassLoaderSearch method entrance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*V-46uXS04f09cxVQ.png" /></figure><p>After adding the log, I found that the problem was even more confusing.</p><ul><li>When no error is reported, the appendToClassLoaderSearch entry will output.</li><li>When there is an error, the appendToClassLoaderSearch entry does not output. <em>Does that mean no commands are executed here?</em></li></ul><p>This is not the same as the error log. <em>Is the stacktrace information fooling us?</em></p><p>After a tough night, I consulted colleagues from the Dragonwell team the next day. Here was what they did:</p><ul><li>tty-&gt;print_cr(“internal error”)</li><li>If this is not available, use printf(“xxxn”);fflush(stdout)</li></ul><p>After that, our logs can be output.</p><p>This was the first difficulty we met. The printf needs to add fflush to ensure successful output.</p><h3>Code Analysis</h3><p>After that, logs are added continuously. Finally, we found that create_class_path_zip_entry returned NULL.</p><h4>What If I Can’t Find the Corresponding jar File?</h4><p>Continue the troubleshooting and find that the stat error is reported. Return No such file or directory. As we mentioned earlier, the path of jarFile exists. <em>Isn’t stat thread-safe?</em></p><p>After checking the document [1], we found that stat is thread-safe.</p><p>Looking back, I noticed that the path of stat was abnormal. Sometimes, the path was empty, and other times, the path was /home/admin/.opt/ArmsAgent/plugins/ahas-java-agent/ahas-java-agent.jarSHOT.jar. As seen at the end of the character, it was caused by two characters written into the same memory. Moreover, the length of the corresponding string has become an irregular number.</p><p>Then, the problem is clear to see. Let’s start looking for the generation of this string. This character is generated by the convertUft8ToPlatformString.</p><h4>Is There a Problem with the Character Encoding Conversion?</h4><p>Therefore, the logic of utf8ToPlatform is debugged. gdb is directly run on ECS to debug jvm and avoid frequent log addition and container restart.</p><p>The results show that under Linux, utf8ToPlatform is the direct memcpy, and the target address of memcpy is on the stack.</p><p>It seems the thread safety problem doesn’t exist.</p><p>After careful investigation, it was found it was related to the environment variables. The environment variable related to coding on ECS is LANG=en_US.UTF-8. The centos:7 does not have this environment variable by default on the container. As such, jvm reads ANSI_X3.4–1968.</p><p>This is the second difficulty. Environmental variables will affect the local encoding conversion.</p><p>With the preceding phenomena and codes, it is found that it is still necessary to go through iconv to switch from UTF-8 to ANSI_X3.4–1968 coding in the container environment.</p><p>It can also be inferred here that if LANG=en_US.UTF-8 is manually set in the container. This problem will not occur again. Additional verification confirms this.</p><p>Then, add the log. When finally confirm that it is iconv, the target string breaks down.</p><p><em>Does that mean the iconv is not thread-safe?</em></p><h4>Iconv Is Not Thread-Safe.</h4><p>We checked iconv’s documentation and found that it is not completely thread-safe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pLp7m8wQUmMqn89C.png" /></figure><p>Generally speaking, before iconv, you need to use iconv_open to open an iconv_t, and this iconv_t does not support the simultaneous use of multiple threads.</p><p>At this point, the problem has been clearly located since jvm has written iconv_t as a global variable. When multiple threads append, it is possible to call iconv at the same time, resulting in competition problems.</p><p>Here is the third difficulty. Iconv is not thread-safe.</p><h3>How Can We Fix It?</h3><h4>Fix the one-java-agent First</h4><p>It is easy to modify the Java code. You only need to add a lock.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RJXp8NHwfjf_-mCD.png" /></figure><p>However, there is a design problem here. The instrument objects have been scattered everywhere in the code. Now, it is suddenly necessary to add a lock. Almost all the places used need to be changed, and the cost of code transformation is high.</p><p>Finally, we solve it through the proxy class.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uxX1idSeulEwEXo0.png" /></figure><p>As such, other places only need to use InstrumentationWrapper, and such a problem will not be triggered.</p><h4>Whether to Repair jvm</h4><p>Then, we analyzed the code on the jvm side and found that the appendToClassLoaderSearch 0 method was not threaded-safe because iconv_t was not thread-safe. <em>Can it be solved gracefully?</em></p><p>If it is a Java program, it can be solved by directly using ThreadLoal to store iconv_t.</p><p>However, on the cpp side, although C++ 11 supports thread_local, jdk8 does not use C++ 11 (you can refer to JEP). Besides, C++ 11 only supports thread_local set and get. Lifecycle management (such as initialization and destruction of thread_local) is not supported yet. For example, it is impossible to automatically recycle iconv_t resources at the end of the thread.</p><p>Let’s fall back to pthread. Since pthread provides thread-specific data, you can do similar things.</p><ol><li>Pthread_key_create creates the thread-local storage area.</li><li>Pthread_setspecific is used to put values into thread-local storage.</li><li>Pthread_getspecific is used to retrieve values from the thread-local storage.</li><li>Most importantly, pthread_once meets the requirement that pthread_key_t can only be initialized once.</li><li>In addition, the second parameter of pthread_once is the callback at the end of the thread, which can be used to close iconv_t to avoid resource leakage.</li></ol><p>In short, pthread provides the full lifecycle management of thread_local. Therefore, the final code is listed below. The thread-local storage is initialized with make_key.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zN0gDXrQY4x_yMMP.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g87GWp3ZqLBw1zmH.png" /></figure><p>Therefore, after compiling the JDK, inputting mirroring and restarting pods several times in batches did not cause the problems mentioned at the beginning of the article.</p><h3>Summary</h3><p>There are many problems we have come across throughout this process, including Java, JNI/JVMTi, glibc, and pthread.</p><ul><li>Printf must be added with fflush to ensure successful output.</li><li>Environment variables affect local character encoding conversions.</li><li>Iconv is not thread-safe.</li><li>Use pthread thread-local storage to implement full lifecycle management of thread-local variables</li></ul><p>From this case, we restored the problem and proposed a solution according to the call stack and code. I hope this article help you learn more about Java/JVM.</p><h3>References</h3><p>[1] Document<br><a href="https://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_09.html">https://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_09.html</a></p><p>[2] Links that one-java-agent fixes:<br><a href="https://github.com/alibaba/one-java-agent/issues/31">https://github.com/alibaba/one-java-agent/issues/31</a></p><p>[3] Links that Dragonwell fixes:<br><a href="https://github.com/alibaba/dragonwell8/pull/346">https://github.com/alibaba/dragonwell8/pull/346</a></p><p>[4] The one-java-agent brings us a convenient and non-intrusive microservice governance method:<br><a href="https://www.alibabacloud.com/product/microservices-engine">https://www.alibabacloud.com/product/microservices-engine</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d77d94c7166" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[KubeVela Brings Software Delivery Control Plane Capabilities to CNCF Incubator]]></title>
            <link>https://alibabatech.medium.com/kubevela-brings-software-delivery-control-plane-capabilities-to-cncf-incubator-db4e51bd6cdf?source=rss-69f6dde768a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/db4e51bd6cdf</guid>
            <dc:creator><![CDATA[Alibaba Tech]]></dc:creator>
            <pubDate>Tue, 14 Mar 2023 10:49:28 GMT</pubDate>
            <atom:updated>2023-03-14T10:49:28.879Z</atom:updated>
            <content:encoded><![CDATA[<p>The CNCF Technical Oversight Committee (TOC) has voted to accept KubeVela as a CNCF incubating project.</p><p><a href="https://kubevela.io/">KubeVela</a> is an application delivery engine built with the Kubernetes control plane that makes deploying and operating applications across hybrid and multi-cloud environments easier, faster, and more reliable. KubeVela can orchestrate, deploy, and operate application components and cloud resources with a workflow-based application delivery model. The application delivery abstraction of KubeVela is powered by the <a href="https://oam.dev/">Open Application Model</a> (OAM).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8H2Opz1PNqpwZozj.png" /></figure><p>The KubeVela project evolved from <a href="https://github.com/crossplane/oam-kubernetes-runtime">oam-kubernetes-runtime</a> and developed with <a href="https://github.com/kubevela/community/blob/main/OWNERS.md#bootstrap-contributors">bootstrap contributions</a> from more than eight different organizations, including Alibaba Cloud, Microsoft, Upbound and more. It was publicly announced as an open source project in November 2020, released as v1.0 in April 2021, and accepted as a CNCF sandbox project in June 2021. The project has more than <a href="https://kubevela.devstats.cncf.io/d/22/prs-authors-table?orgId=1">260 contributors</a> and committers across multiple continents from organizations like Didi, JD.com, JiHu GitLab, SHEIN, and more.</p><p>“KubeVela pioneered a path for delivering applications across multi-cloud/multi-cluster environments with unified yet extensible abstractions,” said Lei Zhang, CNCF TOC sponsor. “This innovation unlocked the next-generation software delivery experience and filled the ‘last mile’ gap in existing practices which focus on the ‘deploy’ stage rather than ‘orchestrating’. We are excited to welcome more app-centric tools/platforms in the CNCF community and look forward to watching the adoption of KubeVela grow to a new level in the fast-growing application delivery ecosystem.”</p><p>KubeVela is used in production today by multiple companies across all major public clouds and on-premises deployments. Most users are adopting KubeVela as their internal “PaaS”, as part of their CI/CD pipeline, or as an extensible DevOps kernel for building their own IDP. Public <a href="https://github.com/kubevela/community/blob/main/ADOPTERS.md">adopters</a> include Alibaba, which uses KubeVela as the core to deliver and manage applications across hybrid environments; Bytedance, which uses KubeVela and Crossplane to provide advanced Gaming PaaS abilities; China Merchants Bank, which uses KubeVela to build a hybrid cloud application platform to unify the whole process from build, ship and run; and many more.</p><p>“We’ve found capabilities such as gateway, security, and observability are being standardized with the emergence of corresponding open source tools and cloud services,” said Fang SITU, leader of aPaaS and Serverless team at Alibaba Cloud. “These capabilities can be integrated so that developers can self-serve, easily configure, automatically trigger, and get faster feedback, thereby greatly improving the application development efficiency. KubeVela is very suitable for the integration and customization of this kind of application delivery process, and it is the best practice of Platform Engineering.”</p><p>“KubeVela enables China Merchants Bank to quickly establish a large-scale unified OAM cloud native application management platform, reducing the complexity of cloud for FinTech and accelerating the standardized development and delivery of modern applications,” said Jiahang Xu, Senior Architect at China Merchants Bank and KubeVela maintainer. “KubeVela provides an application model and programmable CRD, workflow orchestration application delivery, observability, and configuration capabilities. KubeVela empowers cloud native applications along with the CNCF ecosystem.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d4Yd263zJHbnw_1y.png" /></figure><h3>Main Components:</h3><ul><li><a href="https://github.com/kubevela/kubevela">Vela Core</a> is the main component of KubeVela, also known as the KubeVela Control Plane. It provides operators and webhooks for rendering, orchestrating and delivering OAM applications.</li><li>The <a href="https://github.com/kubevela/workflow">Vela Workflow</a> engine translates CUE-based steps and executes them. It’s a common library that can work as a standalone engine or run inside a KubeVela application.</li><li>KubeVela CLI provides various commands that help you to operate applications, such as managing definitions, viewing resources, restarting workflow, and rolling versions.</li><li><a href="https://github.com/kubevela/velaux">VelaUX</a> is the Web UI for KubeVela. It incorporates business logic into fundamental APIs and provides out-of-box user experiences for non-k8s-expert users.</li><li>The <a href="https://github.com/kubevela/terraform-controller">Terraform Controller</a> in KubeVela allows users to use Terraform to manage cloud resources through Kubernetes Custom Resources.</li><li>The <a href="https://github.com/oam-dev/cluster-gateway">Cluster Gateway</a> provides a unified multi-cluster access interface.</li><li>KubeVela also has a growing <a href="https://github.com/kubevela/catalog">catalog</a> with more than 50 community add-ons for integrations, including ArgoCD, FluxCD, Backstage, OpenKruise, Dapr, Crossplane, Terraform, OpenYurt and more.</li></ul><h3>Notable Milestones:</h3><blockquote><em>4.7k GitHub Stars<br>3.5k pull requests<br>1.6k issues<br>290 contributors<br>150 Releases</em></blockquote><p>Since joining the CNCF Sandbox, KubeVela has released seven minor versions to v1.7 and added five new components, including standalone workflow, VelaUX, ClusterGateway, VelaD, and Vela Prism. The number of contributors has tripled from 90+ to 290+, GitHub stars have doubled from 1900+ to 4700+, and contributing organizations have tripled from 20+ to 70+.</p><p>“KubeVela improved the developer experience when it comes to complex multi-cloud environments with their modern open source software delivery control plane,” said Chris Aniszczyk, CNCF CTO. “We look forward to supporting the community in its growth and maturity towards a graduated project.”</p><p>Looking forward, the community plans to improve the user experience for cloud resource provisioning and consumption with delivery workflow, enhance the security for the whole CI/CD delivery process in hybrid/multi-cluster scenarios, support the KubeVela Dynamic API that allows users to make integration with third-party APIs easily, and more. Visit the <a href="https://kubevela.io/docs/roadmap/">roadmap</a> to learn more.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FM3H6gDs9RRM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DM3H6gDs9RRM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FM3H6gDs9RRM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/539eccf3541966bc6f4252550917f4e0/href">https://medium.com/media/539eccf3541966bc6f4252550917f4e0/href</a></iframe><p>This is the story behind KubeVela.</p><p>“We’re humbled and grateful for the trust and support from users and contributors,” said Jianbo Sun, Staff Engineer at Alibaba Cloud and KubeVela maintainer. “KubeVela’s highly extensible design is very suitable for the diverse user scenarios of the community, bringing us a powerful engine to the ecosystem for application delivery. Thanks to the support and endorsement from CNCF, I believe that reaching incubation status is an important milestone for the project. The KubeVela maintainers look forward to collaborating with CNCF in our goals to make deploying and operating applications across today’s hybrid environments easier, faster and more reliable.”</p><p>“Thanks to Kubevela, the way we deploy and manage applications in Kubernetes has now become more accessible,” Daniel Higuero, CTO at Napptive and KubeVela maintainer. “The use of Application and Workflow as top-level entities greatly simplifies common processes on top of Kubernetes. The strength of the approach lies in its ability to simplify basic use cases while enabling complex ones with multi-tenant and multi-cluster support. This is combined with an inherently extensible system which supports community add-ons, allowing it to integrate with other tools and add custom definitions to tailor the experience to your use case.”</p><p>“The CNCF community has incubated a large number of cloud native operation and atomic management capabilities,” said QingGuo Zeng, Technical Expert at Alibaba Cloud and KubeVela maintainer. “We hope to integrate various capabilities through a unified, application-centric concept and help more and more platform developers easily implement standardized applications in enterprises. KubeVela is growing into a powerful helper for enterprises to practice Platform Engineering.”</p><p>“KubeVela aims to provide convenience and advancements of the rich cloud native infrastructures to various industries,” said Da Yin, Senior Engineer at Alibaba Cloud and KubeVela maintainer. “To meet the modern application delivery demands, KubeVela is always exploring extensible and flexible architecture and adding pioneering ideas, including multi-cluster delivery, programmable workflow, and automated observability. KubeVela also continuously cares for the security and stability of the control plane, which builds up production confidence for community adopters. We expect the openness of KubeVela could make it a frontier explorer in the cloud native era.”</p><p>As a CNCF-hosted project, KubeVela is part of a neutral foundation aligned with its technical interests and the larger Linux Foundation, which provides governance, marketing support, and community outreach. The project joins 35 other <a href="https://www.cncf.io/projects/">incubating technologies</a>, including Backstage, Cilium, Istio, Knative, OpenTelemetry, and more. For more information on maturity requirements for each level, please visit the <a href="https://github.com/cncf/toc/blob/main/process/graduation_criteria.md">CNCF Graduation Criteria</a>.</p><p><em>This article was orginally posted on </em><a href="https://www.cncf.io/blog/2023/02/27/kubevela-brings-software-delivery-control-plane-capabilities-to-cncf-incubator/"><em>CNCF</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db4e51bd6cdf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Does an Open-Source Workflow Engine Support an Enterprise-Level Serverless Architecture]]></title>
            <link>https://alibabatech.medium.com/how-does-an-open-source-workflow-engine-support-an-enterprise-level-serverless-architecture-731afdd38657?source=rss-69f6dde768a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/731afdd38657</guid>
            <dc:creator><![CDATA[Alibaba Tech]]></dc:creator>
            <pubDate>Fri, 10 Mar 2023 08:38:17 GMT</pubDate>
            <atom:updated>2023-03-10T08:38:17.496Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.alibabacloud.com/product/severless-application-engine">Serverless Application Engine (SAE)</a> is a Kubernetes-based cloud product that combines the Serverless architecture and the microservice model. As an iterative cloud product, it has encountered many challenges in the process of rapid development. How can we solve these challenges in the booming cloud-native era and perform reliable and fast upgrades for architecture? The SAE team and the KubeVela community worked closely to address these challenges and came up with a replicable open-source solution, KubeVela Workflow.</p><p>This article describes how to use KubeVela Workflow to upgrade the architecture of SAE and interprets multiple practice scenarios.</p><h3>Challenges in the Serverless Era</h3><p>SAE is an application hosting platform for business application architecture and microservices. It is a Kubernetes-based cloud product that combines the Serverless architecture and the microservice model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wlU3C4NHRqPYS3DS.png" /></figure><p>As shown in the preceding architecture diagram, SAE users can host multiple types of applications on SAE. At the underlying layer of SAE, the Java business layer processes the relevant business logic and interacts with Kubernetes resources. At the bottom, it relies on highly available, O&amp;M-free, and pay-as-you-go elastic resource pools.</p><p>In this architecture, SAE mainly relies on its Java business layer to provide users with capabilities. This architecture helps users easily deploy applications. Still, at the same time, it brings some challenges as well.</p><p>With the continuous development of Serverless, SAE has encountered three major challenges:</p><ol><li>Engineers in SAE have some complex and non-standardized operations. How can we automate these complex operations to reduce development consumption?</li><li>With the development of business, the application-delivering capability of SAE is favored by a large number of users. The growth of users also brings efficiency challenges. How can we optimize the existing delivery capability and improve efficiency in high concurrency?</li><li>As Serverless architecture continues to be implemented in enterprises, numerous of cloud vendors are making their product systems serverless. In such a wave, how can SAE quickly connect with internal Serverless capabilities and reduce development costs while launching new features?</li></ol><p>The preceding three challenges show that SAE needs some kind of orchestration engine to upgrade the delivery process, integrate with internal capabilities, and automate operations.</p><p>So, what does this orchestration engine need to meet to solve these challenges?</p><ol><li>High Scalability: The steps in the process need to be highly scalable for this orchestration engine. Only in this way can the originally non-standardized and complex operations be standardized with the steps. In the meanwhile, the steps can combine with the process control capability of the orchestration engine, thus reducing the consumption of development resources.</li><li>Lightweight and Efficient: This orchestration engine must be efficient and production-ready, so as to meet the high concurrency requirements of SAE in large-scale user scenarios.</li><li>Strong Integration and Process Control Capabilities: This orchestration engine needs to be able to quickly integrate with the atomic functions in the company. If the glue code that connects upstream and downstream capabilities can be transformed into the process in the orchestration engine, development costs can be reduced.</li></ol><p>Based on these challenges and considerations, the SAE team and the KubeVela community have conducted in-depth cooperation and launched the <a href="https://github.com/kubevela/workflow">KubeVela Workflow</a> project as an orchestration engine.</p><h3>Why Use Kubevela Workflow?</h3><p>Thanks to the booming ecological of cloud-native, there are already many mature workflow projects in the community (such as Tekton, Argo, etc.). There are also some orchestration engines within Alibaba Cloud. So, <em>why reinvent the wheel instead of using existing technology?</em></p><p>This is because KubeVela Workflow has a fundamental difference in design. The steps in the workflow are designed for the cloud-native IaC system and support abstract encapsulation and reuse, which means that you can use atomic capabilities like a function call in every step, instead of just creating pods or containers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZXD0aCvVYrZlBZar.png" /></figure><p>In KubeVela Workflow, each step has a step type, and each step type corresponds to the resource callend WorkflowStepDefinition. You can use the <a href="https://github.com/cue-lang/cue">CUE language</a> (an IaC language, which is a superset of JSON) to write this step definition or directly use the step type defined in the community.</p><p>You can simply regard a WorkflowStepDefinition as a function declaration. Each time a new step type is defined, a new function is defined. The function requires some input parameters, and the step definition is the same. In the step definition, you can define the input parameters required for this step type in the parameter field. When the workflow is running, the workflow controller executes the CUE code in the corresponding step definition using the actual parameter values input by the user, just as it executes your custom function.</p><p>With such a layer of abstraction of the steps, it adds huge possibilities to the steps:</p><ul><li>If you want to customize the step type (just like writing a new function), you can import the official code packages in the step definition, thus introducing other atomic capabilities into the step, including HTTP requests, CRUD resources in multiple clusters, conditional waiting, etc. With such a programmable step type, you can easily integrate with any system. For example, in the SAE scenario, the step definition is integrate with other internal atomic capabilities (such as MSE, ACR, ALB, SLS, etc.). Then, the workflow orchestration capability is used to control the process.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PvpcrldsBhzh5Ruf.png" /></figure><ul><li>If you only want to use defined steps, just like calling a packaged third-party function, the only thing you need to care about is your input parameters and the step type you want. For example, in a typical image-building scenario, first, specify the step type as build-push-image and then specify your input parameters: the code source and branch of the built image, the name of the built image, and the secret key of the image repository to push.</li></ul><pre>apiVersion: core.oam.dev/v1alpha1<br>kind: WorkflowRun<br>metadata:<br>  name: build-push-image<br>  namespace: default<br>spec:<br>  workflowSpec:<br>   steps:<br>    - name: build-push<br>      type: build-push-image<br>      properties:<br>        context:<br>          git: github.com/FogDong/simple-web-demo<br>          branch: main<br>        image: fogdong/simple-web-demo:v1<br>        credentials:<br>          image:<br>            name: image-secret</pre><p>In such an architecture, the abstraction of the step brings infinite possibilities to the workflow. When you need to add a step to the workflow, you no longer need to compile-build-package the business code and then use the pod to execute the code. You only need to modify the configuration code in the step definition (together with the workflow engine’s orchestration and control capability) to integrate with new features.</p><p>This is also the main reason why SAE chooses Kubevela Workflow. Based on scalability, we can fully leverage the power of ecology and accelerate product upgrades.</p><h3>Cases</h3><p>Next, let’s go deeper into the user cases in SAE.</p><h3>Case 1: Automated Operations</h3><p>The first scenario is an automated operations scenario for SREs in SAE.</p><p>In SAE, we write and update some base images for users. We need to preload these images to multiple clusters in different regions to provide a better experience for users who use these base images.</p><p>The original operation process is very complicated. It involves building images and pushing them across multiple regions using ACR, as well as creating image cache templates and managing those image caches. Regions here include Shanghai, US West, Shenzhen, and Singapore. These operations are non-standardized and time-consuming. This is because when an SRE needs to push these images from the local to foreign clusters, it is likely to fail due to network problems. Therefore, he needs to disperse his energy on these operations that could otherwise be automated.</p><p>This is also the scenario that KubeVela Workflow is suitable for: each step in these operations can be converted into a step in the workflow programmatically, so that these steps can be orchestrated and reused. In addition, KubeVela Workflow provides a visual dashboard. SREs only need to configure a pipeline template once, and can automate the process by triggering execution or by entering specific runtime parameters each time the execution is triggered.</p><p>The simplified steps is like below:</p><ol><li>Use the HTTP request step type to build an image by requesting the service of ACR and pass the image ID to the next step through inputs/outputs. In this step definition, you need to wait until the ACR service is done before ending the execution of the current step.</li><li>If the first step fails, execute the error handle step.</li><li>If the first step is successfully built, use the HTTP request step to build image cache, at the same time, the service logs are used as the source of the current step. Here you can view the logs of the steps directly in the Dashboard to troubleshoot problems.</li><li>Use a step group with deploy step type to preload images for clusters in the China (Shanghai) region and the US (West) region. The multi-cluster management and control capabilities of KubeVela Workflow are used to distribute the ImagePullJob workload to multiple clusters to preload images.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PW43G1uhIhlBQocZ.png" /></figure><p>In the preceding process, if you do not use KubeVela Workflow, you may need to write a bunch of business code to connect multiple services and clusters. Let’s take the last step of distributing the ImagePullJob workload to multiple clusters as an example: Not only do you need to manage the configuration of multiple clusters, but also need to watch the status of the workload (CRD) until the status of the workload becomes Ready before proceeding to the next step. This process actually corresponds to a simple Kubernetes Operator&#39;s reconcile logic: first create or update a resource, if the status of the resource is as expected, then end the reconcile, if not, continue to wait.</p><p>Do we need to implement an Operator for every new resource management in our operations? Is there any convenient way to free us from the complicated Operator development?</p><p>It is precisely because of the programmability of steps in KubeVela Workflow that it can completely cover these operations and resource management in SAE scenarios, which can help engineers reduce manpower consumption. Similar to the above logic, the step definition corresponding to KubeVela Workflow is very simple. No matter what kind of resources (or a HTTP interface request), it can be covered by a similar step template like:</p><pre>template: {<br>  // First, read resources from the specified cluster<br>    read: op.#Read &amp; {<br>      value: {<br>        apiVersion: parameter.apiVersion<br>        kind: parameter.kind<br>        metadata: {<br>          name: parameter.name<br>          namespace: parameter.namespace<br>        }<br>      }<br>      cluster: parameter.cluster<br>    }<br>    // Second, wait until the resource is Ready. Otherwise, the step keeps waiting<br>    wait: op.#ConditionalWait &amp; {<br>      continue: read.value.status != _|_ &amp;&amp; read.value.status.phase == &quot;Ready&quot;<br>    }<br>    // Third(optional), if the resource is Ready, then...<br>    // Custom Logic...<br>    <br>    // Users must input the defined parameter when using the step type<br>    parameter: {<br>      apiVersion: string<br>      kind: string<br>      name: string<br>      namespace: *context.namespace | string<br>      cluster: *&quot;&quot; | string<br>     }<br>}</pre><p>Corresponding to the current case is:</p><ul><li>First: Read the status of ImagePullJob in a specified cluster, such as the cluster in the China (Shanghai) region.</li><li>Second: If the ImagePullJob is ready and the image has been preloaded, continue to execute.</li><li>Third(Optional): After the ImagePullJob is ready, clean up the ImagePullJob in the cluster.</li></ul><p>Like this, no matter how many Region clusters or new type resources are added in the subsequent O&amp;M scenarios, you can let KubeVela Workflow manage the cluster’s KubeConfig, and use the defined step types with different cluster names or resource types to achieve a simplified Kubernetes Operator Reconcile process to reduce development costs.</p><h3>Case 2: Optimize the Existing Delivery Process</h3><p>In addition to automating internal O&amp;M operations, upgrading the original SAE product architecture to improve delivery efficiency for users is also an important reason of choosing KubeVela Workflow.</p><h4>Original Architecture</h4><p>In the delivery scenario of SAE, a delivery process corresponds to a series of tasks, such as: initializing the environment, building images, releasing in batches, etc. This series of tasks corresponds to the SAE Tasks in the figure below.</p><p>These tasks are sequentially thrown to Java Executor for business logic in the original architecture of SAE, such as creating resources in Kubernetes, and synchronizing the status of current tasks with the MySQL database, etc.</p><p>After the current task is completed, JAVA Executor will get the next task from SAE’s original orchestration engine, and at the same time, the orchestration engine will continuously put new tasks into the initial task list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HnV3qQmVSQJ44wcq.png" /></figure><p>The biggest problem in this old architecture is the polling call. JAVA Executor will get it from the SAE task list every second to check whether there are new tasks; at the same time, after JAVA Executor creates Kubernetes resources, it will attempts to get the status of resources from the cluster every second.</p><p>The original architecture of SAE is not the controller model in the Kubernetes ecosystem, but the polling model. If the orchestration engine layer is upgraded to the controller model for event watching, it can better integrate with the entire Kubernetes ecosystem and improve efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OWJY66MVlMCBKr1L.png" /></figure><p>However, the logic coupling of business is deep in the original architecture. If the traditional container-based cloud-native workflow is used, SAE needs to package the original business logic into images and maintain and update a large number of images, which is not a sustainable path. We hope the upgraded workflow engine can be easily integrated with the task orchestration, business execution layer, and Kubernetes cluster.</p><h4>New Architecture</h4><p>With the high scalability of KubeVela Workflow, SAE engineers do not need to repackage the original capabilities into images or make large-scale modifications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U7TpV0FDwssal3EP.png" /></figure><p>The new process is shown in the preceding figure. After a delivery paln is created on the SAE product side, the business side writes the model to the database, converts the model, and generates a KubeVele workflow, which corresponds to YAML on the right side.</p><p>At the same time, SAE’s original Java Executor provides the original business capabilities as microservice APIs. When KubeVela Workflow is executed, each step is IaC-based, and the underlying implementation is in the CUE language. Some of these steps will call the business microservice API of SAE, while others will directly interact with the underlying Kubernetes resources. Data can be transferred between steps. If there is an error in the call, you can use the conditional judgment of the step to handle the error.</p><p>Such optimization is scalable and fully reuses the Kubernetes ecosystem. It extends workflow processes and atomic capabilities and is oriented to the final state. This combination of scalability and process control can cover the original business functions and reduce the amount of development. At the same time, the state update latency is reduced from the minute level to the millisecond level, which is agile and native. It has the YAML-level description capability but also improves the development efficiency from 1d to 1h.</p><h3>Case 3: Launch New Features Quickly</h3><p>In addition to automated O&amp;M and upgrading the original architecture, <em>what else can KubeVela Workflow provide?</em></p><p>The reusability of steps and the ease of integration with other ecosystems bring more surprises to SAE in addition to upgrades: from writing business code to orchestrating different steps, so as to launch new product features quickly!</p><p>SAE has accumulated a large amount of JAVA foundation and supports a wealth of functions, such as: supporting single-batch release, multi-batch release, and canary release for JAVA microservices. However, with the increase of customers, some customers have put forward new requirements, and they hope to have the ability to publish multilingual north-south traffic in canary release.</p><p>There are also many mature open-source products for canary release, such as Kruise Rollout. After investigation, SAE engineers found that Kruise Rollout can be used to complete the ability of canary release, and it can cooperate with the internal ingress controller(ALB) of Alibaba Cloud to split different traffic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QOPWO3aaAKLhXTUb.png" /></figure><p>Such a solution is shown in the architecture diagram above. SAE distributes a KubeVela Workflow, and the steps in the Workflow will integrate with Alibaba Cloud ALB, open-source Kruise Rollout, and SAE’s business components at the same time. Batch management is completed in the steps, thus completing the rapid launch of features.</p><p>In fact, after using KubeVela Workflow, it is no longer necessary to write new business codes for this feature. It is only necessary to write a step type for updating canaray batches.</p><p>Due to the programmability of step types, we can easily use different patch policies in the definition to update the release batches of Rollout objects in the different clusters. Moreover, in the workflow, the step type of each step is reusable. This means when you develop a new step type, you are laying the foundation for the next time a new feature is launched. This reuse allows you to launch features quickly and reduce development costs.</p><h3>Summary</h3><p>After SAE upgraded the KubeVela architecture, it improved delivery efficiency and reduced development costs. Based on the advantages of its underlying reliance on Serverless infrastructure, it can give full play to the advantages of the product in application hosting.</p><p>In addition, the architecture upgrade solution of KubeVela Workflow in SAE is an open-source solution that can be replicated. The community provides more than 50 built-in step types (including image building, image pushing, image scanning, and multi-cluster deployment, using Terraform to manage infrastructure, condition wait, message notification, etc) to help you open up CI/CD easily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dNm-JLF7MYTEvKWl.png" /></figure><p>You can refer to the following documents for more usage scenarios:</p><ul><li>Build images, push images, and deploy resources: <a href="https://github.com/kubevela/workflow#try-kubevela-workflow">https://github.com/kubevela/workflow#try-kubevela-workflow</a></li><li>Orchestrate multiple KubeVela Applications: <a href="https://github.com/kubevela/workflow/blob/main/examples/multiple-apps.md">https://github.com/kubevela/workflow/blob/main/examples/multiple-apps.md</a></li><li>Initialize the Environment with One Click, use Terraform to pull up clusters, manage clusters, and distribute resources to new clusters: <a href="https://github`.com/kubevela/workflow/blob/main/examples/initialize-env.md">https://github`.com/kubevela/workflow/blob/main/examples/initialize-env.md</a></li><li>Call the specified service and send a notification of the returned result through data passing: <a href="https://github.com/kubevela/workflow/blob/main/examples/request-and-notify.md">https://github.com/kubevela/workflow/blob/main/examples/request-and-notify.md</a></li><li>Use different context parameters to control the deployment of resources: <a href="https://github.com/kubevela/workflow/blob/main/examples/run-with-template.md">https://github.com/kubevela/workflow/blob/main/examples/run-with-template.md</a></li></ul><h3>The End</h3><p>You can learn more about KubeVela and the OAM project through the following materials:</p><ul><li>Project Code Library: <a href="https://github.com/kubevela/kubevela">https://github.com/kubevela/kubevela</a> Welcome to Star/Watch/Fork!</li><li>Workflow Code Library: <a href="https://github.com/kubevela/workflow">https://github.com/kubevela/workflow</a> Welcome to Star/Watch/Fork!</li><li>Official Project Homepage and Documents: kubevela.io</li><li>Slack: CNCF #kubevela Channel</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=731afdd38657" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The ZEEKR App System’s Cloud-Native Architecture Transformation Practice]]></title>
            <link>https://alibabatech.medium.com/the-zeekr-app-systems-cloud-native-architecture-transformation-practice-cfcaf9a0841c?source=rss-69f6dde768a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/cfcaf9a0841c</guid>
            <dc:creator><![CDATA[Alibaba Tech]]></dc:creator>
            <pubDate>Fri, 03 Mar 2023 06:42:21 GMT</pubDate>
            <atom:updated>2023-03-03T09:46:58.895Z</atom:updated>
            <content:encoded><![CDATA[<h3>Preface</h3><p>New energy vehicles have become the key pillar for the re-emergence of China’s automobile market. With the rapid development of the new energy vehicle market, there are different brands of car manufacturers. ZEEKR is a new brand of high-end electric cars under the Geely Holding Group. In April 2021, ZEEKR released the first high-end intelligent electric car model, ZEEKR 001, which was well-received by the market. As of December 2022, the cumulative delivery volume of the 001 models has exceeded 70,000 units. It ranked first for three consecutive months in the deluxe pure electric models of ZEEKR, with a value of more than 300,000 RMB.</p><p>In addition to providing customers with excellent products, ZEEKR establishes connections with users through the ZEEKR app. The ZEEKR app has launched an online community, subscription travel, online shopping, ZEEKR Life, and other innovative modules to achieve the full lifecycle management of ZEEKR products and the full scene coverage of the user journey. Different scenarios are integrated into the app, including users that want to know about relevant models, users interested in purchasing and using cars, and users that want to share feelings and get quick solutions to after-sales problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Uh5P4bnf5ovtoA44.png" /></figure><p><em>“I didn’t know much about ZEEKR before. The ZEEKR app is very helpful to me. I think it is good. At the same time, I learned about the car I want to buy through the software. I have known ZEEKR for a year. I cannot only learn about ZEEKR cars but also use points in the app to change products. I hope ZEEKR can launch more practical products.”</em></p><p>It comes from an Apple App Store user review. The ZEEKR app can help car owners control cars intelligently anytime and anywhere and provide the ultimate travel experience that allows owners to purchase goods and join community activities. Users can obtain vehicle information at their fingertips and enjoy their travel with convenience.</p><h3>The Practice of Cloud-Native Architecture Exploration</h3><h3>Cloud-Native Technology Development</h3><p>With the rapid development of ZEEKR’s digital business, the IT technology behind it is constantly updated and iterated. ZEEKR attaches great importance to customer experience and <strong>regards system stability, iterative efficiency of business functions, and rapid problem positioning and resolution as the cornerstones of building core competitiveness.</strong> Liu Hao (Vice President of ZEEKR) said, <em>“In order to respond to user needs quickly (such as shortening the manufacturing cycle of a car and upgrading the car operating system conveniently and smoothly), companies need to innovate from products to user experience to business models. However, the experience in the development of consumer Internet and traditional industries is not enough to meet the high requirements of industrial Internet for cost, efficiency, and quality. Cloud-native is a deterministic technological development trend, which can effectively promote industrial development and drive enterprises to actively innovate. ZEEKR will continue to invest and empower cloud-native capabilities in a wider range of business areas (such as research, production, supply, marketing, and three electrics) within the company.”</em></p><p><strong>These businesses are compatible with the core capabilities brought by the cloud-native architecture. </strong>In the process of transforming the ZEEKR system to the cloud, around the cloud-native technology system, we promote the technological upgrading and transformation of each business line of ZEEKR and speed up the development process of digital intelligence. ZEEKR has followed two principles in the technical selection:</p><p><strong>The first principle is to embrace open-source mainstream technical standards.</strong> It can ensure the maturity of technical solutions, make it easier to obtain technical resources and best practices from the developer community, and help enterprises recruit technical talents. In addition, such a strategy avoids being tied to closed technology systems and specific cloud vendors. The localization of software technology and independence and control are also points to consider.</p><p><strong>The second principle is to make full use of the cloud.</strong> Non-functional requirements (such as stability guarantee, underlying technology implementation, technical component maintenance, and auto-scaling) are handed over to cloud vendors as much as possible so the technical team can devote more energy to business innovation.</p><p>These two principles are not contradictory. On the contrary, they can be well-integrated. This is an architecture selection standard that all enterprise users that use cloud computing can learn from utilizing. For example, Kubernetes is a typical technical standard that meets open-source standards. The Kubernetes products provided by Alibaba Cloud can simplify users’ construction costs and better integrate with cloud computing resources. At the same time, users can still use cloud products based on the standard protocols and APIs of open-source Kubernetes, which is the best embodiment of the integration of the two selection principles.</p><h3>Business Containerization</h3><p>Under the cloud-native trend, Kubernetes has undoubtedly become the infrastructure of the new generation of cloud IT architecture for enterprises. Since 2021, ZEEKR has started a microservice and containerization transformation plan to migrate the base of IT systems from virtual machines to Kubernetes.</p><p>In terms of the selection of the Kubernetes platform, based on the two principles of technology selection, ZEEKR chose Alibaba Cloud ACK. Based on the reliable and stable IaaS platform of Alibaba Cloud, ACK packages more than 30 cloud products to form a new interface for automated O&amp;M and cloud platform interaction. This improves the elasticity and automated O&amp;M capabilities of enterprise business systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/0*vKx6Vr8RXhIEh0jx.png" /></figure><p>Based on ease of use and integration capabilities of ACK, the containerization transformation of the ZEEKR IT system is smoother than expected. For each business system, the migration from virtual machines to Kubernetes is only a change in the underlying bearer without too much transformation cost. In the process of containerization transformation, when the ZEEKR Technical Team encounters difficult problems, it can obtain best practice guidance from Alibaba Cloud for the first time, including cluster planning, platform operation and maintenance, application adaptation, security protection, observability, and other aspects. This improves the speed of containerization transformation.</p><p>Systems (such as the ZEEKR app and SCRM) have been 100% based on Kubernetes. <strong>Compared with the traditional VM-based deployment methods, containerization helps ZEEKR improve resource utilization by 20% and O&amp;M efficiency by 50%.</strong> In September 2022, it passed the maturity assessment of the cloud-native technology architecture of CAICT. At the same time, the ZEEKR Technical Team also mastered the ability to manage ultra-large-scale Kubernetes clusters in the process of containerization transformation and promoted the application of more cloud-native new technologies.</p><h3>Unified Microservice Model</h3><p>The unification of the microservice model take places at the same time as the containerization transformation. Before this, ZEEKR’s various business units coexisted with multiple technology stacks, and the communication complexity between each other was high. The handover of projects often required huge energy, which hindered the progress of digital transformation. Therefore, microservices model unification was imperative.</p><p>It took ZEEKR over two years to complete this arduous task. Although it required a lot of energy, the benefits are immediate and persistent. Whether it is an internal team or a tripartite ISV, there is a unified technical framework standard. After each team shares the technology stack, the research and development efficiency is doubled.</p><p>It is related to the IT strategy for many years. High openness, high maturity, and high popularity are indispensable when selecting a microservices model. Considering that ZEEKR uses Java as its main development language, Spring Cloud Alibaba has become the best choice for the microservice framework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*B3lLOQaaZxbpbqeP.png" /></figure><p>Spring Cloud Alibaba is dedicated to providing an all-in-one solution for microservice development. It contains the necessary components for developing distributed application microservices so developers can easily use these components to develop distributed application services through the Spring Cloud programming model. Some of these components are integrated into the code in the form of SDK, and some run independently in the form of middleware. The latter can choose managed cloud products to reduce the workload of developers. For example, Alibaba Cloud Microservice Engine (MSE) has improved the out-of-the-box registration configuration center Nacos and cloud-native gateway.</p><h3>Stability and Efficiency Issues Become More Prominent</h3><p>It can be expected that with the launch of the ZEEKR app, the number of registered car owners has grown explosively, and the use scenarios have been expanding. In this process, the user experience of the app has become more important. How to ensure the stability and agility of the app while the user scale is growing at a high speed and how to ensure the microservice development efficiency of the app have brought challenges to the research team.</p><h4>Poor Business Continuity without Capacity Planning</h4><p>Remote car controlling, online map, 3C mall, and other core app services have strict requirements for business continuity. It needs to be online 24/7. The app is facing the pressure of high concurrency and large traffic, especially in the face of peak season sales activities, the release of new models, sudden hot events, and other situations. There are often exceptions (such as functional failure, page failure, excessive delay, and even complete inaccessibility of the app), which have a serious impact on user experience.</p><h4>Slow Feature Version Iteration</h4><p>With the increasing demand for user scenarios, more features are waiting to be released online, and the requirement for iteration frequency is getting higher. However, due to the lack of end-to-end canary release capability on the app server, in order to ensure business stability, developers can only choose to release a new version at midnight (during the off-peak hours), which is a challenge, and the lossless release feature is required.</p><h4>Technical Architecture Lacks Overall Design</h4><p>At the beginning of the company’s establishment, in order to realize the rapid launch of the app, the overall design of the technical architecture was not considered enough, which was reflected in many problems (such as high coupling between services, long system links, different technical implementation standards, and an unreasonable selection of cloud products). For example, through research, it was found that the requested link of a core interface was too long, resulting in a high delay jitter rate and affecting user experience.</p><p>The R&amp;D Team realized they will face more challenges with the development of the business. In the rapid development of the business, it is necessary to ensure the stability of the existing business, quickly iterate new features, and ensure that the efficiency of development will not be reduced with the growth of the business. After all, there is a problem that the pace of team recruitment cannot keep up with the development of the business. In summary, the key for the team to solve the rapid app iterative evolution is to solve the problems of stability and efficiency.</p><ul><li>Stability: After the number of users increases, the stability of the system becomes more important. In terms of users encountering abnormal errors at a specific time, a specific function point continuously reporting errors, and the system being completely unavailable for a period, these will affect the reputation of the product among users. Finally, this completely unavailable scenario may even become a hot topic on social media networks.</li><li>Efficiency: As the number of users increases, the corresponding requirements increase, and the business scenarios become more complex. At this time, the internal test cannot cover all scenarios. You need to increase the investment in testing. Although there are more functional requirements, the speed of iteration is required to be faster because there are already many competitors in the market. One of the keys to competition is speed. The business, the pace of development, testing, and release should be faster.</li></ul><p>To address these issues, the R&amp;D Team optimizes and tunes microservice systems from traffic ingress to microservices and then from a global perspective based on the business architecture. It conducts in-depth microservice exploration around cost, stability, and efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Iyo6vMpBS1Yhitrf.png" /></figure><h3>Business Link Ingress Upgrade</h3><p>The gateway architecture in the ZEEKR architecture is inconsistent, and various gateways have played a specific role. We can see from the figure that there are many gateways (such as traffic gateway, API gateway, and microservice gateway). They have the functions of security (WAF), API management, traffic distribution, etc. If a request link passes through multiple gateways, this brings certain challenges to both cost and stability.</p><p>At this time, MSE cloud-native gateways appeared in the vision of the R&amp;D Team. Cloud-native gateways combine traffic gateways (Kubernetes Ingress and Nginx) and microservice gateways (Spring Cloud Gateway and Zuul gateways) to reduce 50% of resource costs, shorten request time, and reduce O&amp;M complexity.</p><p>As a north-south public network gateway, it is common to use WAF to protect against abnormal traffic. As the Internet environment becomes more complex, users’ demands for protection continue to increase. The common practice is to connect the traffic to the WAF security gateway, filter the traffic, forward the traffic to the traffic gateway, and reach the microservice gateway. Then, after upgrading the cloud-native gateway, we need to consider if the security capability of the ingress traffic is still available.</p><p>The cloud-native gateway is directly connected to Alibaba Cloud WAF through the built-in WAF module. This way, the user’s request link can complete the WAF protection capability at the same time only through the cloud-native gateway, reducing the O&amp;M complexity of the gateway, as shown in the following figure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DCbYjzeCf1YCPTeZ.png" /></figure><p>As the ingress of link traffic, the gateway has security capabilities and undertakes the management of ingress traffic/capacity and high availability.</p><h3>Exploration of the High Availability of Microservices</h3><h4>Use Lossless Online and Offline to Improve the Stability of Microservice</h4><p>The customer app uses a microservices model. The request failure rate increases and POD restarts continuously in scenarios (such as business release and auto-scaling). To solve this problem, combined with MSE product capabilities, through adaptive waiting and active notification during application offline, readiness probe during application online, and service preheating, microservices are released without loss, effectively avoiding traffic loss during the release process and reducing the risk of service access failure. In addition, the MSE traffic prevention and control capabilities are introduced to improve the overall stability of the service by using corresponding technical measures for core business scenarios (such as port throttling and degradation, MQ peak and valley cutting, and database slow SQL throttling).</p><h4>Use Horizontal Splitting to Improve Business Auto Scaling Capabilities</h4><p>With the rapid development of business, the problem of insufficient capacity under the original architecture of the ZEEKR app is becoming more prominent. Horizontal expansion cannot be carried out quickly in the face of new car releases, sales activities, and sudden hot spots. A large number of core business databases are placed on the same database instance, which is prone to <em>all losses</em>. The Alibaba Cloud Service Team recommends using PolarDB-X products to separate business databases one by one and split large business tables to solve the problem of large single tables. This improves the elastic scaling capability at the database level. In addition, to address the pain points of insufficient microservice elasticity, container elasticity solutions (such as multi-zone node auto-scaling, HPA, and CronHPA) are provided to improve the ability of core services to cope with traffic emergencies.</p><h4>Traffic Protection and Fault Tolerance</h4><p>Let’s imagine some downstream service providers encounter performance bottlenecks during peak business hours that affect business. The ZEEKR App Team encountered such a problem. In the process of an architecture migration, it encountered unexpected slow calls, which slowed down the system and led to a jitter in overall stability. <em>How can they avoid such problems?</em> You need to configure a circuit breaker rule for some non-critical service consumers. When the proportion of slow calls or the proportion of error calls within a period reaches a certain condition, the circuit breaker is automatically triggered, and the Mock result is directly returned for a subsequent period. This can ensure that the calling end is not dragged down by unstable services, give unstable downstream services some <em>breathing time</em>, and ensure the normal operation of the entire business link.</p><p>There are a lot of unexpected things, so <em>how can we make the system highly available and make the system work on the optimal solution under uncertain conditions?</em> The ZEEKR App Team tried to do microservice stability management on the large level of the app to avoid the overall downtime of the app. Then, they tried to sort out the core services and interfaces, find out the upstream and downstream, decouple and transform the strong dependencies, and confirm what reasonable parameters are configured for the core services based on the monitoring and observability data. After that, they tried to perform throttling and degradation configurations, drills, and optimization on the service many times, summarize the practical rules of the scenario, and formulate appropriate technical specifications.</p><h4>Development and Testing Efficiency Improvement: Online Service Testing</h4><p>After ZEEKR began to deploy, release, and test on the cloud, they encountered the following problems:</p><ol><li><em>After the application is deployed, is the application healthy? When there is a problem online, how can they quickly initiate a request and reproduce it?</em></li><li><em>How can they quickly verify whether the historical functions are normal before the service is launched?</em></li><li><em>Before the large version is launched, what is the impact of the modified content on the performance, and will the service pressure be too great after the volume is increased?</em></li></ol><p>The R&amp;D environment, test environment, staging environment, and production environment are deployed in different VPCs to achieve security isolation. If you build a test tool, you need to solve the problem of network interconnection between the test tool and different environments. The IT staff of the enterprise only wants a simple test tool, but it is far from over to solve the complex cloud network topology after cloud migration. In order to use the test tool in the office network, it is necessary to ensure that the test tool can be accessed by the office network. At this time, it is facing the test of network security.</p><p>Cloud service testing and stress testing are designed to solve this problem. <strong>With the elastic computing capability of FC, it can solve the problem of the network connection on the cloud and the problem of resource utilization to the greatest extent.</strong> With the content provided by the service contract, the service test function can automatically fill in the test parameters, and users only need to modify the values to initiate the test. You can connect service tests in series as prompted to achieve the purpose of automated regression and stress testing.</p><h3>End-to-End Governance</h3><h4>End-to-End Canary Release, Enabling Release at Any Time during the Day</h4><p>As the sales of ZEEKR cars become more popular, its registered users and daily active users grow rapidly, and more business scenarios and new functions need to be supported, with an average upgrade frequency of one small version in two or three days and one large version in half a month. In order to not affect the business peak during the day, each release can only be carried out during the off-peak hours of the business in the early morning. Let’s imagine that if the R&amp;D/O&amp;M personnel concentrate on the release at night, the work efficiency of participating in the release will be affected the next day. If fewer people are selected to participate in the release at night, hemostasis measures will probably be too late to be implemented when problems occur, and fault responsibilities will not be easily divided.</p><p>The Alibaba Cloud Service Team helps the ZEEKR Team develop and implement an end-to-end grayscale release solution. The Alibaba Cloud Service Team releases and cuts streams after the verification is completed vy deploying a canary version, and performing canary verification based on the traffic ratio or customer characteristics. This meets the requirements of customers for releasing small versions at any time during the day.<strong> Based on the scenarios that customers need to release multi microservices on the core business link and the MSE cloud-native gateway and traffic grayscale tagging to implement multi-service end-to-end grayscale scenarios, </strong>you can implement grayscale scenarios (such as CDN, gateway, MQ, configuration, and database). As such, you can implement multi-service daytime releases without the need to change any service code. At the same time, you can verify the multi-service through gradual traffic amplification. If a problem occurs, the traffic can be cut back in time, which reduces the stability risk that may be caused by the release during the day. At the same time, the transformation of the Apsara DevOps pipeline can help customers achieve the core business automation release and improve deployment efficiency.</p><h4>Development Environment Isolation</h4><p>The iteration of microservices has a lot of dependencies. Business developers cannot complete the development locally. They must use a complete set of environments to perform development and joint debugging. There are dozens of applications in the ZEEKR app system. If each development environment maintains a microservice environment provided by a complete set of app systems, it will consume a lot of manpower and resource costs.</p><p>The ideal logical isolation of the development environment should be like this. Based on the git-branch design concept, a stable baseline environment is retained. Development students of each branch can quickly pull up the feature environment to be developed through logical environment isolation. We only need to maintain a complete set of baseline environments. When adding a feature development environment, we only need to deploy the changed applications involved in this feature separately, instead of deploying a complete set of microservice applications and their supporting facilities in each feature environment. The baseline environment contains all microservice applications and other facilities (such as service registries, domain names, SLB, and gateways), while the feature environment contains only the applications that need to be modified in this feature. As such, the cost of maintaining n sets of feature environments becomes an addition instead of the original multiplication, from n×m to n+m. This is equivalent to adding a feature environment at zero cost, so we can safely scale out multiple feature environments. <strong>The ZEEKR Team uses the end-to-end grayscale solution in microservice governance to implement traffic <em>swimlanes</em>. This way, the team can quickly build an isolated development environment, improve R&amp;D efficiency, and reduce costs.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*DTelEDlme-1K3pdgMirNLg.png" /></figure><h4>End-to-End Stress Testing and Tuning</h4><p>In order to find out the actual concurrent capacity that an app can carry, it is necessary to perform multiple rounds of end-to-end stress testing and tuning for core service interfaces. System capacity evaluation, optimization, and protection are summarized as stress testing, observability, throttling, and scale out. The construction of a highly available system must come from practice. The ZEEKR Team conducted a performance survey of the app service capability through stress testing to evaluate whether the performance is acceptable. If the performance is unacceptable, you need to scale out and optimize. If the performance is as expected, you must configure the corresponding throttling rules to prevent service failure if the traffic exceeds the expected traffic.</p><p>During the entire stress testing drill, you need to press, watch, limit, and scale the data while continuously receiving feedback and adjusting the data and establish a system that ensures high availability of the business system. The end-to-end stress test lets everyone know the performance and capacity of the app system and enhances the confidence of the whole production system to upgrade to the cloud-native architecture.</p><h3>Outlook</h3><p>The ZEEKR app has explored the upgrading of cloud-native architecture, improved the stability and agility of the C-side business system, and provided solid technical support for higher sales targets. This is just the beginning of exploration. With the deepening of the cloud-native architecture, the usability of the business will continue to increase, thereby offering a better travel experience and more fun to the car end user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfcaf9a0841c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HealthBlocks’ blockchain-based platform helps medical practitioners reduce their administrative…]]></title>
            <link>https://alibabatech.medium.com/healthblocks-blockchain-based-platform-helps-medical-practitioners-reduce-their-administrative-4c738098834f?source=rss-69f6dde768a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c738098834f</guid>
            <dc:creator><![CDATA[Alibaba Tech]]></dc:creator>
            <pubDate>Fri, 20 Jan 2023 11:48:13 GMT</pubDate>
            <atom:updated>2023-01-20T11:48:13.898Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>HealthBlocks’ blockchain-based platform helps medical practitioners reduce their administrative workload</strong></h3><p><strong><em>The Philippine startup has developed a digital clinic management system to manage patient records, schedule appointments, and track inventory.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q9XVFhIDICERNJZISOE5LQ.png" /></figure><p>Medical data is key to the diagnosis of medical conditions to improve clinical decision-making and enhance patient outcomes. But the collection and management of medical data, including record keeping, can be a tedious process for healthcare professionals.</p><p>For example, <a href="https://www.healthit.gov/faq/what-electronic-health-record-ehr">electronic health records (EHRs)</a> are health information often used by doctors to keep track of their patients’ conditions. On average, medical professionals would need to spend around <a href="https://www.forbes.com/sites/brucelee/2020/01/13/electronic-health-records-here-is-how-much-time-doctors-are-spending-with-them/?sh=570466305172">16 minutes to use or update an EHR</a> for a single patient. Also, in a 2018 survey of 20,000 physicians, 70% of respondents said they spent ten hours or more on <a href="https://www.ama-assn.org/practice-management/sustainability/do-you-spend-more-time-administrative-tasks-your-peers">paperwork and administrative tasks</a> each week.</p><p>To address this problem, Philippine-based startup HealthBlocks has come up with HealthBlocks 360, a digital platform that aims to relieve healthcare practitioners of their administrative burden.</p><p>Notably, HealthBlocks 360 tackles the issue of poor <a href="https://www.ama-assn.org/practice-management/digital/spending-too-much-time-typing-ehr-you-can-change">electronic health records (EHRs)</a> usability, which is a leading driver of burnout for doctors. With an easy-to-use interface, the platform allows its users to customize and improve the medical office workflow.</p><p>HealthBlocks 360 can also plan and schedule patient appointments and track clinic inventory and finances, allowing its users to cut down time spent on internal administrative processes.</p><p>The cloud-based, real-time clinic management system can be accessed from a wide range of devices, including smartphones. Built on blockchain technology, HealthBlocks 360 also ensures that all personal health information is processed and stored securely.</p><p>Led by Grace Anne Agustin-Mendoza (CEO) and James Tristan Mendoza (director), HealthBlocks is a venture-backed subsidiary of MaroonStudios, a software company from Quezon City, Manila. The startup was founded in 2018 after being named a top five winner of the ASEAN’s Next Great Idea competition, which was organized by the Malaysian Global Innovation &amp; Creativity Centre (MaGIC), Uber, and Digi in 2017. HealthBlocks was also runner-up at the UAE Blockchain Virtual GovHack, which was held in the same year in Dubai.</p><p>By reducing the administrative burden of healthcare practitioners, HealthBlocks aspires to help health professionals focus on providing clinical care.</p><p><a href="https://healthblocks.ph/">HealthBlocks</a> applied to take part in the <a href="https://www.alibabacloud.com/startup/global-startup-accelerator?spm=a2c65.11461447.0.0.1917579cHd2Lbj">Project AsiaForward Alibaba Cloud Global Startup Accelerator</a> Philippines Demo Day, held online on February 8, 2022.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c738098834f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Advance’s on-demand salary platform provides financial assistance to workers]]></title>
            <link>https://alibabatech.medium.com/advances-on-demand-salary-platform-provides-financial-assistance-to-workers-91035999af64?source=rss-69f6dde768a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/91035999af64</guid>
            <dc:creator><![CDATA[Alibaba Tech]]></dc:creator>
            <pubDate>Sat, 31 Dec 2022 12:12:19 GMT</pubDate>
            <atom:updated>2022-12-31T12:12:19.154Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>The Philippine fintech startup offers early wage advances to cash-strapped employees.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AXs-W2eRMr0mMDRnFBfzcA.png" /></figure><p>Financial inclusion allows individuals and businesses to have <a href="https://www.worldbank.org/en/topic/financialinclusion/overview">access to useful and affordable financial products and services</a> that meet their needs — transactions, payments, savings, credit, and insurance — delivered in a responsible and sustainable way.</p><p>An example of financial inclusion is having credit access, which can provide a lifeline to people and businesses to stay afloat, especially during the COVID-19 pandemic. Boosting access to credit can also help households address the <a href="https://www.oecd-ilibrary.org/sites/eb28eb26-en/index.html?itemId=/content/component/eb28eb26-en">volatility of their personal finances</a> and is essential for firms to fund their investments.</p><p>In the Philippines, <a href="https://mb.com.ph/2022/05/19/number-of-unbanked-filipinos-decreases-as-digital-finance-supports-daily-needs">half of the country’s adult population is unbanked</a>. This means many Filipinos do not have access to financial services, including credit services. To tackle this issue, Philippine startup Advance has developed an on-demand salary platform to provide financial aid to cash-strapped workers. Touted as the first salary on-demand provider in the Philippines, the fintech startup partners with employers to offer salary advances to their employees.</p><p>Employees who wish to receive a wage advance just need to fill out an online application, which can be approved in a matter of days. Upon approval, the payroll advance is disbursed directly through Advance’s digital platform.</p><p>Founded in 2018 by Jaime de los Angeles (CEO) and Addi Guevara (CFO), Advance has a management team that includes Stef Lim (COO) and Enzo Doromal (CTO). The Manila-based company raised an undisclosed sum in a seed funding round in 2020 led by Next Billion Ventures, Wavemaker Partners, Dymon Asia Ventures, and Accion Venture Lab.</p><p>By enhancing the financial well-being of employees, the company hopes that its business solution can drive organizational growth, improve productivity, and boost workplace engagement.</p><p><a href="https://advance.ph/">Advance</a> applied to take part in the <a href="https://www.alibabacloud.com/startup/global-startup-accelerator">Project AsiaForward Alibaba Cloud Global Startup Accelerator</a>, held online on February 8, 2022.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91035999af64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Malaysia-based Entrusol is combating obesity with healthy, Halal-certified snacks]]></title>
            <link>https://alibabatech.medium.com/malaysia-based-entrusol-is-combating-obesity-with-healthy-halal-certified-snacks-99bf19791e06?source=rss-69f6dde768a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/99bf19791e06</guid>
            <dc:creator><![CDATA[Alibaba Tech]]></dc:creator>
            <pubDate>Mon, 14 Nov 2022 10:27:23 GMT</pubDate>
            <atom:updated>2022-11-14T10:27:23.971Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>With a variety of nutritious and tasty snacks, the startup is aiming to provide healthier options to snack lovers in Southeast Asia.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x8ZVyrjxFhKMmGNyYBaoQA.png" /></figure><p>The COVID-19 pandemic has had a profound impact on many people’s lives, including their dietary habits. Long periods of isolation and incessant updates about the spread of the disease can be stressful, resulting in<a href="https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0262332"> stronger cravings for comfort foods</a> with high fat and sugar content.</p><p>Pandemic-fueled weight gain is a major cause for concern in many parts of the world, especially in Malaysia, where obesity is becoming more common. At least<a href="https://iptk.moh.gov.my/images/technical_report/2020/4_Infographic_Booklet_NHMS_2019_-_English.pdf"> half of all Malaysian adults are overweight or obese</a>, according to a study conducted by Malaysia’s Ministry of Health in 2020.</p><p>To help tackle the growing obesity challenge, Malaysia-based startup Entrusol has come up with healthier snacking options. The company produces healthy snacks that are tasty and nutritious such as nuts, granola, cereal drinks, and more. These snacks are Halal-certified and can be consumed by Muslims, who form the majority of the population in Malaysia.</p><p>Entrusol operates an e-commerce website that allows consumers to make online purchases of snacks that can be delivered right to their doorstep. The snack company also offers a snack subscription service.</p><p>Moving forward, the company plans to increase its market reach through online channels, as well as pop-up stores in areas such as the Klang Valley. Entrusol also has plans to retail its products in brick-and-mortar stores, and expand overseas where there is demand for Halal-certified healthy snacks, such as in Singapore, Thailand, and Brunei.</p><p>Founded in 2019 by Nash Mohamad (CEO), Elly Fazira Jamil (COO), and Ejue Liza (chief business development officer), Entrusol hopes its line of snacks can help people stave off their hunger pangs without compromising their health.</p><p><a href="https://entrusol.com/">Entrusol</a> applied to take part in the <a href="https://www.alibabacloud.com/startup/global-startup-accelerator?spm=a2c65.11461447.0.0.7dad7f75vwyPHC">Project AsiaForward Alibaba Cloud Global Startup Accelerator</a> Singapore Demo Day, held on June 1, 2022, at the Singapore EXPO.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99bf19791e06" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MatarStars’ smart freight management platform optimizes business operations for the logistics…]]></title>
            <link>https://alibabatech.medium.com/matarstars-smart-freight-management-platform-optimizes-business-operations-for-the-logistics-3e580b1ab5ba?source=rss-69f6dde768a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e580b1ab5ba</guid>
            <dc:creator><![CDATA[Alibaba Tech]]></dc:creator>
            <pubDate>Mon, 14 Nov 2022 07:13:15 GMT</pubDate>
            <atom:updated>2022-11-14T07:13:15.066Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>MatarStars’ smart freight management platform optimizes business operations for the logistics industry</strong></h3><p><strong><em>The Vietnamese startup has developed an AI-powered solution to help businesses better manage their logistics processes.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kl9QU668yoSS5lF32Btnuw.png" /></figure><p>Vietnam is one of Southeast Asia’s fastest-growing economies. Over the past few decades, the country has achieved high economic growth. In 2021, the country’s GDP hit <a href="https://blogs.worldbank.org/eastasiapacific/next-stage-vietnams-development-journey">USD 363 billion</a>, a jump from USD 21 billion in 1994.</p><p>A key sector that is thriving is the logistics industry, which is expected to record a<a href="https://en.vietnamplus.vn/demand-for-logistics-real-estate-increases-sharply-savills-vietnam/235611.vnp"> compound annual growth rate (CAGR) of 7%</a> between 2021 and 2026. This is largely due to Vietnam’s strategic location, <a href="https://www.trade.gov/country-commercial-guides/vietnam-trade-agreements">free trade agreements</a>, as well as the rapid growth of e-commerce in the region.</p><p>Despite this, Vietnam’s logistics industry faces major challenges such as operational inefficiencies in the trucking segment, which handles<a href="https://documents.worldbank.org/en/publication/documents-reports/documentdetail/165301554201962827/strengthening-vietnam-s-trucking-sector-towards-lower-logistics-costs-and-greenhouse-gas-emissions"> 77% of the total freight volume</a> transported in the country.</p><p>For example, route planning for local trucking operations is typically made intuitively. As a result, the lack of knowledge of local routes or human error can lead to inefficient transportation routes, during which trucks chalk up <a href="https://convoy.com/blog/empty-miles-in-trucking/">empty miles</a>. This leads to fuel wastage and increased carbon emissions. Often, logistics companies in Vietnam struggle to hire well-trained drivers with the relevant experience to operate freight vehicles safely and efficiently.</p><p>Vietnamese company MatarStars, also known locally as Song Nhật Tinh, has developed a smart freight management system to tackle these challenges while unlocking productivity gains in the logistics sector. The platform offers companies access to two solutions to optimize their freight operations.</p><p>The first is a transport management system that can plan freight transportation routes, reduce empty miles traveled, view freight costs, and analyze vehicle usage patterns. The other is an AI-driven fleet management system. The AI technology allows users to track deliveries in real time, and leverages data to identify areas for freight optimization. Users can also use the network to identify unsafe driving behavior.</p><p>MatarStars is led by Duc Vu Minh (CEO), Vu Tung (COO), and Nam Hoai (CTO). The team has vast experience and knowledge, with prior stints in companies such as FPT Software and VPBank. Backed by VSV Capital, MatarStars aims to improve the operational performance of companies in the logistics industry in Vietnam and across the region.</p><p><a href="https://matarstars.co/en">MatarStars (Song Nhật Tinh</a>) was a finalist at the <a href="https://www.alibabacloud.com/startup/global-startup-accelerator">Project AsiaForward Alibaba Cloud Global Startup Accelerator</a> Singapore Demo Day, held on May 25, 2022 in Ho Chi Minh City.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e580b1ab5ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linh AI’s digital platform helps businesses speed up AI adoption]]></title>
            <link>https://alibabatech.medium.com/linh-ais-digital-platform-helps-businesses-speed-up-ai-adoption-6d7b09dcb5d5?source=rss-69f6dde768a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d7b09dcb5d5</guid>
            <dc:creator><![CDATA[Alibaba Tech]]></dc:creator>
            <pubDate>Tue, 11 Oct 2022 06:39:37 GMT</pubDate>
            <atom:updated>2022-10-11T06:39:37.606Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>The startup provides companies with a scalable infrastructure for AI development.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f4A7xEN2wj82Y5eWFXaFfA.png" /></figure><p>Artificial intelligence (AI) is transforming the world. AI adds value to businesses in diverse ways, and helps companies automate tasks, improve operational efficiency, reduce costs, and provide data analysis. AI can also be adopted in a myriad of industries, such as healthcare, manufacturing, and transportation.</p><p>Despite the benefits that AI provides, its adoption can be challenging for companies. One is the need for <a href="https://www.zdnet.com/article/ai-has-a-big-data-problem-heres-how-to-fix-it/">reliable, high-quality data</a>. Building and deploying AI requires large volumes of data, which can be a time-consuming process.</p><p>At the same time, to train AI algorithms, developers have to carry out data annotation, a laborious process that can be costly, in which data is labeled and categorized.</p><p>Data quality is key to building a successful AI system. High-quality data is needed to ensure AI algorithms are reliable and produce accurate results. Flawed and insufficient data can negatively impact the effectiveness of AI, <a href="https://ai100.stanford.edu/2021-report/standing-questions-and-responses/sq10-what-are-most-pressing-dangers-ai#determinism">exhibiting bias</a> or <a href="https://venturebeat.com/ai/when-ai-hurts-people-who-is-held-responsible/">endangering people</a>.</p><p>To aid AI developers, Linh AI has built Graviton, a scalable infrastructure for AI development that can process a broad range of data formats.</p><p>Graviton’s annotation capabilities allow its users to identify and annotate data points such as keypoints, polylines, and cuboids, which are more detailed than traditional bounding box annotations. Annotations made on the platform can also include metadata such as attributes, text, and object and image groupings to enrich datasets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VN1jpTW8HwQT6p7knfJfTQ.gif" /></figure><p>The platform’s annotation tool, which can be semi-automated using a proprietary AI model, can speed up the annotation process by up to six-fold.</p><p>Users have the option to directly manage their datasets through the platform to provide insights on data composition. In addition, it allows developers to review annotations at scale, allowing them to detect errors and improve the accuracy of annotations.</p><p>Graviton is compliant with global regulations on data protection and privacy, such as the Personal Data Protection Regulations (PDPR) in Singapore, and the General Data Protection Regulation (GDPR) in Europe.</p><p>Graviton is developed by Singapore-based Linh AI, a startup founded in 2021 by Giang Nguyen (CEO), Nhan Nguyen (CTO), and Louis Phung (COO).</p><p>Linh AI is supported by NTUitive — the innovation and entrepreneurial arm of Nanyang Technological University (NTU) — as well as NTU’s SCSE Innovation Lab, and the NVIDIA Inception program.</p><p><a href="https://linh.ai/">Linh AI</a> applied to take part in the <a href="https://www.alibabacloud.com/startup/global-startup-accelerator?spm=a2c65.11461447.0.0.1917579cHd2Lbj">Project AsiaForward Alibaba Cloud Global Startup Accelerator</a> Singapore Demo Day, held on June 1, 2022 at the Singapore EXPO.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d7b09dcb5d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hiraya Water is a smart water management tool for water utility companies]]></title>
            <link>https://alibabatech.medium.com/hiraya-water-is-a-smart-water-management-tool-for-water-utility-companies-f25c7b63303d?source=rss-69f6dde768a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f25c7b63303d</guid>
            <dc:creator><![CDATA[Alibaba Tech]]></dc:creator>
            <pubDate>Tue, 11 Oct 2022 06:36:05 GMT</pubDate>
            <atom:updated>2022-10-11T06:36:05.593Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>The Philippine startup’s resource-efficient solution combines hardware and AI to reduce water wastage and regulate energy consumption.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*diOzK5BA8AQZQkIdWhpAkQ.png" /></figure><p>Water is an important resource in industries such as agriculture, construction, and manufacturing. In rural and less developed areas, water resource management can be complicated and challenging, especially for utility companies, largely due to a lack of infrastructure and expertise.</p><p>Hence, when water distribution systems are not managed efficiently, it can result in a myriad of problems for water utility companies as well as consumers.</p><p>For example, poorly managed water systems can lead to <a href="https://www.adb.org/sites/default/files/publication/27473/reducing-nonrevenue-water.pdf">water leakage and wastage</a>. Leakages are also considered a form of <a href="https://blogs.worldbank.org/water/what-non-revenue-water-how-can-we-reduce-it-better-water-service">non-revenue water (NRW)</a>, which can lead to high operational expenditure for utility companies.</p><p>Hiraya Water is a Philippines-based company that has developed a solution to address these issues. The company’s flagship product is a “real-time adjusting pump system” (R-TAP), which can help regulate pressure applied inside a water distribution network.</p><p>R-TAP leverages the use of sensors to collect data from various components of a water distribution system, such as pumps, tanks, and valves. The information is then analyzed with a proprietary algorithm to manage the water distribution network more efficiently.</p><p>For instance, R-TAP’s AI can help optimize the operations of water pumps to prevent high supply pressure within a water system. Water utility companies that integrate R-TAP into their systems can also reap cost savings on maintenance and energy consumption.</p><p>In addition, R-TAP has an advanced metering infrastructure (AMI), which allows its users to optimize their data operations through an online dashboard where users can manage customer information, meter readings, as well as billing and payments. Users will also be able to monitor the water network distribution in real-time and detect problems such as water theft, leaks, and malfunctioning meters.</p><p>Led by Stephen Larcia (CEO), Hiraya Water was founded in 2014 after Larcia and his team placed among the top ten winning teams at IdeaSpace Foundation’s National Technology Startup Competition, held in the Philippines that year.</p><p>R-TAP’s development is backed by grants from the Department of Science and Technology (DOST) in the Philippines, and Development Innovation Ventures — the open innovation program of the United States Agency for International Development (USAID).</p><p><a href="https://www.hirayawater.com/">Hiraya Water</a> applied to take part in the <a href="https://www.alibabacloud.com/startup/global-startup-accelerator?spm=a2c65.11461447.0.0.1917579cHd2Lbj">Project AsiaForward Alibaba Cloud Global Startup Accelerator</a> Philippines Demo Day, held online on February 8, 2022.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f25c7b63303d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>