Use Spring Cloud to develop applications - Serverless App Engine

SAE seamlessly integrates with the native Spring Cloud microservice framework, allowing applications built with this framework to be migrated to SAE by simply adding dependencies and adjusting service registry configurations, with no code changes required. SAE offers enterprise-level features including application hosting, governance, monitoring, alerting, and diagnosis.

Benefits of Spring Cloud

Spring Cloud simplifies application development with a suite of standards and specifications, covering service discovery, load balancing, circuit breakers, configuration management, event-driven messaging, and message buses. It also facilitates the implementation of gateways, distributed tracing, security, and distributed job scheduling and coordination.

Commonly used Spring Cloud components include Spring Cloud Netflix, Spring Cloud Consul, and Spring Cloud Alibaba.

If your application is developed with Spring Cloud components like Spring Cloud Netflix or Spring Cloud Consul, you can deploy it on SAE to leverage application hosting capabilities and advanced monitoring features such as end-to-end tracing, without modifying any code.

To access additional service governance features in SAE for managing your Spring Cloud applications, you need to either replace your existing Spring Cloud components with those from Spring Cloud Alibaba or add Spring Cloud Alibaba components to your setup.

Compatibility description

SAE supports Spring Cloud versions Greenwich, Finchley, and Edgware. For detailed information on the compatibility between Spring Cloud, Spring Boot, Spring Cloud Alibaba, and their components, see version mappings.

The table below describes the features of Spring Cloud, open-source components, and their compatibility with SAE.

Spring Cloud features		Open source implementation	SAE compatibility
General-purpose features	Service registration and discovery	Netflix Eureka Consul Discovery	Compatible and substitute components available
	Load balancing	Netflix Ribbon	Compatible
	Service calls	Feign RestTemplate	Compatible
Configuration management		Config Server Consul Config	Compatible and substitute components available
Service gateway		Spring Cloud Gateway Netflix Zuul	Compatible
Tracing		Spring Cloud Sleuth	Compatible and substitute components available
Message-driven Spring Cloud Stream		RabbitMQ binder Kafka binder	Compatible and substitute components available
Message bus Spring Cloud Bus		RabbitMQ Kafka	Compatible and substitute components available
Security		Spring Cloud Security	Compatible
Distributed job scheduling		Spring Cloud Task	Compatible
Distributed coordination		Spring Cloud Cluster	Compatible

Version mappings

The table below shows the version mappings among Spring Cloud, Spring Boot, Spring Cloud Alibaba, and SAE's commercial components.

Spring Cloud	Spring Boot	Spring Cloud Alibaba
ANS	ACM	SchedulerX
Greenwich	2.1.x	2.1.1.RELEASE
Finchley	2.0.x	2.0.1.RELEASE
Edgware	1.5.x	1.5.1.RELEASE
Hoxton	2.2.x	2.2.x

Note

Spring Cloud Alibaba Nacos Discovery is an open-source component of ANS, and Spring Cloud Alibaba Nacos Config is an open-source component of ACM.

References

If you are new to developing native Spring Cloud applications and want to deploy them on SAE, you must first add the configuration management dependency locally before deploying the application to SAE. For more information, see Use Spring Cloud to develop microservice applications and deploy them on SAE.
If you have developed a local Spring Cloud application that uses components like Eureka, Consul, ZooKeeper, and Redis for service registration and discovery, and you want to deploy it to SAE, you need to update the service registration and discovery components to Spring Cloud Alibaba Nacos Discovery. There is no need to alter any business code for deploying your application on SAE to host your microservices. For more information, see Modify service registration and discovery of applications to Nacos.