-
Notifications
You must be signed in to change notification settings - Fork 235
Great Wall Motor's Multi Cloud Active Active Architecture Practice and Exploration
Guide:
Great Wall Motor Company Limited (hereinafter referred to as "GWM") is a world-renowned SUV, passanger car and pickup manufacturer that owns four brands, which are HAVAL, WEY, ORA and GWM Pickup. It was listed on the Hong Kong Stock Exchange in 2003 and the Shanghai Stock Exchange in 2011. By the end of 2018, its assets had reached 111.8 billion yuan. With over 70 holding subsidiaries, GWM has more than 59,000 employees.
Great Wall Motors has an extremely high demand for service stability, requiring that even if a fault occurs with a certain cloud service provider, it can immediately switch to another cloud to continue providing reliable and stable services. AutoMQ, as a cloud-neutral product, can be deployed on cross-cloud k8s clusters to help Great Wall Motors synchronize business data in real-time. This way, when one cloud goes down, the service can be promptly switched to another cloud without affecting the business.
Today's case study is based on a presentation by Chen Tianyu, Director of R&D at Great Wall Motors, at an AutoMQ Meetup. We have summarized the key points from the presentation to help you understand this customer's case. The full video can be viewed at the end of this article.
Mr. Chen Tianyu, R&D Director at GWM, not only showcased the company's technological innovations in the field of new energy vehicles but also introduced their solutions to IT challenges. Specifically, in cloud computing and service-oriented architecture, they successfully addressed the complexities and challenges of digital transformation through a multi-cloud strategy and active-active architecture.
GWM proposed an "in-city active-active" solution to address the reliability and flexibility issues of cloud services:
The importance of multi-cloud active-active: This approach is not just to address cloud provider failures but to ensure that GWM can always provide stable and reliable services. By establishing access points among multiple cloud providers, they have achieved a cross-cloud architecture that improves system fault tolerance and stability.
Selection and management of multiple clouds: GWM no longer simply reassigns workloads to another cloud platform but actively leverages the characteristics and advantages of different cloud providers. Through global data traffic scheduling and service-oriented management, they ensure high availability and performance optimization of the system.
Separation of control plane and data plane: GWM has achieved the separation of the control plane and data plane, so even if the control plane of one cloud platform has issues, the data plane can continue to operate independently, avoiding comprehensive system failures.
Pain Points of Using MQ Systems in Cross-Cloud Scenarios: Traditional MQ products face significant challenges in data synchronization between cloud providers. Achieving effective cloud stability and cross-cloud reassignment requires additional data synchronization tools or custom-built solutions.
Key Features of AutoMQ's Cross-Cloud Solution: AutoMQ is a neutral MQ provider that supports deployment on cross-cloud Kubernetes clusters. It offers excellent cost-effectiveness and elasticity.
- What is automq: Overview
- Difference with Apache Kafka
- Difference with WarpStream
- Difference with Tiered Storage
- Compatibility with Apache Kafka
- Licensing
- Deploy Locally
- Cluster Deployment on Linux
- Cluster Deployment on Kubernetes
- Example: Produce & Consume Message
- Example: Simple Benchmark
- Example: Partition Reassignment in Seconds
- Example: Self Balancing when Cluster Nodes Change
- Example: Continuous Data Self Balancing
-
S3stream shared streaming storage
-
Technical advantage
- Deployment: Overview
- Runs on Cloud
- Runs on CEPH
- Runs on CubeFS
- Runs on MinIO
- Runs on HDFS
- Configuration
-
Data analysis
-
Object storage
-
Kafka ui
-
Observability
-
Data integration