Unlock Seamless Message Integration with Alibaba Cloud EventBridge

Introduction

The article introduces Alibaba Cloud EventBridge as a cloud‑native event bus that solves current messaging integration challenges, focusing on routing, processing, and ecosystem expansion needs.

Current Messaging Landscape

Message queues are widely used for decoupling and traffic shaping, but evolving business requirements now demand advanced capabilities such as message routing across regions, data filtering, and transformation.

Key Capability Requirements

Message Routing – Need to aggregate data from multiple applications and synchronize across regions for disaster recovery.

Message Processing – Different downstream systems (RocketMQ, RabbitMQ, Kafka) require filtered and transformed payloads rather than raw messages.

Ecosystem Extension – Integration with logs (SLS), serverless functions (FC), and other cloud services to unlock additional value.

EventBridge Overview

EventBridge is a serverless event bus that supports Alibaba Cloud services, custom applications, and SaaS apps via the CloudEvents 1.0 protocol. Its core capabilities are:

Unified Event Service – Consolidates events from most Alibaba Cloud products into a single management console.

Data Pipeline – Enables bidirectional data flow, such as routing messages between queues or importing logs into queues.

Open Integration – Provides multi‑language SDKs and full compatibility with the CloudEvents 1.0 schema, allowing easy migration and integration with other EDA engines.

Message Integration Solutions

Message Flow Solution

EventBridge supports a wide range of message products (RocketMQ, RabbitMQ, Kafka, MNS, MQTT). Users can create routing tasks directly from the message product console or the EventBridge console, including cross‑region and cross‑account routing.

For cross‑region routing (e.g., Beijing to Shanghai), users select source and target instances and launch the task with a single click.

For cross‑account scenarios, EventBridge event buses synchronize data between different Alibaba Cloud accounts.

Message Processing Solution

EventBridge offers rich filtering and transformation rules, supporting exact match, prefix/suffix, exclusion, numeric, array, and complex composite matching.

Transformation types include full event, partial event, constant, template, and Function Compute converters, allowing extraction and re‑formatting of payload fields.

Ecosystem Extension Solution

EventBridge expands the message ecosystem by ingesting events from services such as MNS, Kafka, DTS, and custom events, and exporting to compute services (FC, SAE), databases (RDS), notification platforms (DingTalk, WeChat), HTTP targets, and third‑party SaaS applications.

Practical Scenarios

Cross‑Region Message Routing

In a multi‑region deployment (Hangzhou, Beijing, Qingdao), EventBridge can create routing tasks from each region to a central region, enabling a global data dashboard while avoiding routing loops by configuring appropriate filters.

Step‑by‑Step: Create a Beijing‑to‑Shanghai RocketMQ Routing Task

In the RocketMQ console, select Message Outbound and click Create Task .

Choose RocketMQ as the outbound type.

Select Beijing as the source region and fill in the instance details.

Set Shanghai as the target region and provide the target instance information.

Configure optional message filtering and transformation, then confirm.

Wait 1–2 minutes; the task will appear in the running state.

Offline Data Processing

For analytics, messages from RocketMQ can be routed to Log Service (SLS) with custom formatting. Users configure a task, map source fields (e.g., name, state) to a template, and the transformed logs are written to SLS.

Select SLS as the outbound type.

Specify the source RocketMQ instance and target SLS project/logstore.

Define the log content format using variables and templates.

Confirm and wait 1–2 minutes for the task to become active.

Conclusion

EventBridge provides a comprehensive, low‑cost solution for message integration, covering routing, processing, and ecosystem support. Users are encouraged to follow the official documentation for the latest features.