This topic describes the best practices for developing and deploying applications in SAE.
Isolate development, testing, and production environments using namespaces: Create a namespace for each environment to separate your development, testing, and production environments. Applications within the same namespace can call each other over the internal network, while applications in different namespaces are isolated from each other.
Development scenario: Isolate development and testing environments using client-cloud connection: Describes how to isolate traffic between a local development environment and an online SAE testing environment. This improves development efficiency by enabling rapid joint development and debugging.
Development scenario: Isolate environments using ApsaraMQ for RocketMQ: Describes how to use Alibaba Cloud ApsaraMQ for RocketMQ to isolate environments. This method lets you implement traffic shaping in asynchronous scenarios without modifying your business code.
Online scenario: Implement end-to-end canary release using a self-managed Spring Cloud Gateway or Zuul gateway: Describes how to implement an end-to-end canary release in SAE. This method lets you control traffic across the entire request chain without modifying your business code.
Deploy an Nginx service using SAE: Describes how to deploy an Nginx service using SAE. You can use this deployment to build a static website or set up a reverse proxy that forwards client requests to backend applications.