Function Compute and Simple Message Queue form an appropriate serverless, event-driven backend for bursty mobile workloads.
Function Compute is fully managed and automatically allocates elastic compute resources when functions are invoked. Alibaba Cloud bills Function Compute primarily according to actual configured resources and execution duration, allowing the startup to avoid maintaining continuously running application servers. This is particularly suitable for APIs and backend handlers experiencing unpredictable request spikes.
SMQ provides managed asynchronous messaging for decoupling backend components. It supports queue-based processing and publish-subscribe topics, making it suitable for notification events, background jobs, workflow messages, and traffic buffering. Alibaba Cloud explicitly identifies load leveling during sudden traffic spikes as an SMQ use case.
SMQ can also directly trigger Function Compute through queue or topic integrations, creating an event-driven design without dedicated message-consumer servers.
ECS requires persistent server resources and management, which conflicts with the requested serverless operating model. MaxCompute is a large-scale data warehouse and batch analytics platform rather than the application ' s transactional API or messaging layer.
Therefore, Function Compute supplies elastic execution while SMQ provides reliable asynchronous communication and notification-event handling.
Study Guide reference: Delivering Services and Content on Alibaba Cloud — Function Compute, serverless architectures, SMQ, event-driven integration, and elastic application services.
==================================================
