Best practices for developing and deploying applications in SAE.
Isolate environments with namespaces: Create a namespace per environment to isolate development, testing, and production. Applications in the same namespace communicate over the internal network; applications in different namespaces are isolated.
Development scenario: Isolate development and testing environments using client-cloud connection: Isolate traffic between your local development environment and an online SAE testing environment for faster joint development and debugging.
Development scenario: Isolate environments using ApsaraMQ for RocketMQ: Use ApsaraMQ for RocketMQ for environment isolation with traffic shaping in asynchronous scenarios, without modifying business code.
Online scenario: Implement end-to-end canary release using a self-managed Spring Cloud Gateway or Zuul gateway: Implement end-to-end canary releases in SAE to control traffic across the entire request chain without modifying business code.
Deploy an Nginx service using SAE: Deploy an Nginx service in SAE to build a static website or set up a reverse proxy that forwards client requests to backend applications.