By adopting AutoMQ, which directly relies on the underlying cloud storage CubeFS, the need for upper-layer replication is eliminated. The architecture is expected to save two-thirds of storage costs when fully implemented. AutoMQ's stateless computing layer perfectly meets the requirements for containerization transformation, significantly enhancing system flexibility.

Asia's Quora, Zhihu (NYSE: ZH), has significantly reduced operational complexity and saved a lot of costs by using AutoMQ instead of Kafka. Through this strategic implementation, Zhihu has not only streamlined its data operations but also embraced technical innovations that AutoMQ offers over traditional Apache Kafka, ensuring enhanced performance, scalability, and efficiency.

When Geely Auto Group was originally using Apache Kafka, the constraints of its architecture made it difficult to scale the cluster storage. Therefore, the only way to avoid expanding the cluster storage was to reduce the data retention time, which had a certain impact on the business. AutoMQ completely solved the pain point of Kafka's elastic scaling.

Within one month, Palmpay seamlessly migrated its business, including metrics tracking and real-time computing, to AutoMQ, processing and distributing billions of messages and events daily. The new solution reduced costs by over 50% compared to the original setup, with no negative impacts.

With the rapid growth of the business, the architecture of Apache Kafka, which guarantees data persistence through multiple ISR copies, exposed issues related to cost and elasticity. After seamlessly replacing it with Apache Kafka-compatible AutoMQ, overall costs dropped by more than 50%, and it can automatically scale horizontally without manual intervention.

CaoCao Mobility is a leading shared mobility platform in China. The mobility business is strongly influenced by weather and time. Apache Kafka's heavy dependence on local storage makes cluster scaling operations complex and risky, making it difficult to support the mobility business. After switching to AutoMQ, they completely solved the scaling challenges of Kafka.

By leveraging a cloud-native architecture and tiered storage, RedKafka accommodates vast amounts of real-time data. However, the challenge lies in flexible scaling and cost optimization. AutoMQ, with its new architecture based on EBS shared storage and object storage, provides significant improvements in elasticity for scaling. Its storage-computing separation aligns well with current operational requirements based on Kubernetes.

Poizon previously relied on Kafka to build its observability platform, requiring a team to spend several days each quarter on scaling operations. Since adopting AutoMQ, data storage has been moved to object storage, making the compute layer stateless and fully compatible with Kafka. This has enabled automatic elastic scaling without manual intervention, significantly reducing cloud resource costs by up to 85%.

360 extensively adopted Apache Kafka internally. However, its storage-computing integrated architecture required data migration during scaling, increasing the operational burden. In contrast, AutoMQ uses a storage-computing separation architecture, storing data in object storage and eliminating the need for data migration during cluster scaling.

TokenPocket, a world-leading crypto wallet, faced the challenge of replaying Kafka messages from years ago. The original Apache Kafka-based solution proved to be costly. By switching to AutoMQ and migrating data storage to object storage, they significantly reduced overall costs.

Great Wall Motor is building a multi-cloud, multi-active architecture across multiple public clouds. The challenge lies in achieving real-time, cross-cloud disaster recovery with message middleware. By choosing AutoMQ, they benefit from its inherent multi-cloud support and Kubernetes compatibility, enabling them to achieve multi-active deployment and traffic orchestration for their multi-cloud applications.