This tutorial demonstrates how EventBridge routes meeting status events from Cloud Conferencing to a specified HTTP gateway using an event rule, helping you implement an event-driven architecture.
Prerequisites
- Activate EventBridge and grant permissions
- Activate Cloud Conferencing.
Background information
- Event-driven architecture: An event-driven architecture helps you decouple service modules, improving service stability and flexibility. All business data can be mapped to events, and these events are categorized into different event types by business domain. For more information, see event-driven architecture.
- Cloud Conferencing: Cloud Conferencing is an open, reliable, and intelligent Platform-as-a-Service (PaaS) from Alibaba Cloud. Built on years of video conferencing technology and application experience from Alibaba Group, a globally deployed network with extensive node coverage, and advanced AI technologies, it allows you to quickly build easy-to-use, multi-terminal collaboration applications.
Event type Description Scenario Meeting Status Meeting start or end events - A meeting starts when the first participant joins. The event includes the following data: time, MeetingUUID, MeetingName, and action.
- A meeting ends when the last participant leaves, whether actively or passively. The event includes the following data: time, MeetingUUID, MeetingName, and action.
Participant Status An event that indicates a change in a participant's status. - A participant joins a meeting. The event includes the following data: time, MeetingUUID, MeetingName, userID, groupId, and action.
- A participant leaves a meeting. The event includes the following data: time, MeetingUUID, MeetingName, userID, groupId, and action.
Participant Action An event that indicates an action performed by a participant in a meeting. - Mute or unmute. The event includes the following data: time, MeetingUUID, MeetingName, userID, groupId, and action.
- Turn the speaker on or off. The event includes the following data: time, MeetingUUID, MeetingName, userID, groupId, and action.
- Turn the camera on or off. The event includes the following data: time, MeetingUUID, MeetingName, userID, groupId, and action.
- Start or stop screen sharing. The event includes the following data: time, MeetingUUID, MeetingName, userID, groupId, and action.
Meeting Statistics Events for publishing meeting statistics An event containing the maximum concurrency is published once per day.
Note
Cloud Conferencing can be used as an event source only in the China (Hong Kong) and China (Hangzhou) regions.
Flow of Cloud Conferencing events
This topic describes how to integrate an Alibaba Cloud service, such as Cloud Conferencing, with EventBridge.
Step 1: Create an event rule
Cloud Conferencing events are published to the default event bus. EventBridge provides a built-in default event bus, so you do not need to create one. The following steps describe how to create an event rule for the default event bus:
Log on to the EventBridge console.
In the left-side navigation pane, click Event Buses.
In the top navigation bar, select a region.
- On the Event Buses page, click the bus named default.
In the left-side navigation pane, click Event Rules.
- In the left-side navigation pane, click Event Rules. On the Event Rules page, click Create Rule.
- Complete the Create Rule wizard.
- In the Configure Basic Info step, enter MyRule in the Name field, enter Route meeting status events from Cloud Conferencing to a specified HTTP gateway. in the Description field, and then click Next Step.
- In the Configure Event Pattern step, select Alibaba Cloud Service Event Source for Event Source Type, select acs.aliyuncvc Cloud Conferencing for Event Source, select Meeting Status for Event Type, and then click Next Step.
- In the Configure Targets step, configure an event target, and then click Create.
- Service Type: Select HTTP.
- URL: Enter http://example.com/eventBridge/processEvent.
- Body: Click Complete Event.
- Network Type: Click Internet.
Important The event targets that you want to configure for an event rule must reside in the same region as the event rule.
Step 2: Use an HTTP gateway to receive events
Use an HTTP gateway to receive events.
The following code provides an example on how to use an HTTP gateway to receive events:
import lombok.extern.slf4j.Slf4j;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.stereotype.Controller;
import org.springframework.web.bind.annotation.PostMapping;
import org.springframework.web.bind.annotation.RequestBody;
import org.springframework.web.bind.annotation.ResponseBody;
@Controller
@SpringBootApplication
@Slf4j
public class EventProcessingApplication {
public static void main(String[] args) {
SpringApplication.run(DemoApplication.class, args);
}
@PostMapping("/eventBridge/processEvent")
@ResponseBody
public String receiveMessage(@RequestBody String data) {
log.info("receiveEvent");
log.info(data);
return "received";
}
}