Quick 3‑Minute Guide to the Full Spring Cloud Alibaba Suite

Background

Since the first release of Spring Cloud Alibaba, Chinese developers have paid close attention to it. Spring Cloud Alibaba is an open‑source microservice framework built on Spring Cloud that integrates Alibaba’s proven distributed‑system technologies like Dubbo and Nacos, offering a more complete enterprise‑grade solution.

Key Components

Nacos – dynamic service discovery, configuration and service management platform; can replace Eureka and Config Server.

Dubbo – high‑performance, lightweight Java RPC framework for remote service calls.

Sentinel – traffic‑control and circuit‑breaker component for distributed services.

RocketMQ – low‑latency, highly reliable distributed message queue.

Seata – open‑source distributed transaction solution ensuring atomicity across microservices.

Additional Alibaba Cloud components such as OSS, SchedulerX and SMS require integration with Alibaba Cloud services.

Version Management

Spring Cloud Alibaba components are not included in the Spring Cloud BOM, so they must be imported via spring-cloud-alibaba-dependencies. Example Maven configuration:

<properties>
  <spring-cloud.version>Hoxton.SR3</spring-cloud.version>
  <spring-cloud-alibaba.version>2.2.1.RELEASE</spring-cloud-alibaba.version>
</properties>

<dependencies>
  <!-- Nacos service discovery -->
  <dependency>
    <groupId>com.alibaba.cloud</groupId>
    <artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId>
  </dependency>
  <!-- OpenFeign service call -->
  <dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-openfeign</artifactId>
  </dependency>
  <!-- Load balancer -->
  <dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-loadbalancer</artifactId>
  </dependency>
</dependencies>

<dependencyManagement>
  <dependencies>
    <!-- Import Spring Cloud BOM -->
    <dependency>
      <groupId>org.springframework.cloud</groupId>
      <artifactId>spring-cloud-dependencies</artifactId>
      <version>${spring-cloud.version}</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
    <!-- Import Spring Cloud Alibaba BOM -->
    <dependency>
      <groupId>com.alibaba.cloud</groupId>
      <artifactId>spring-cloud-alibaba-dependencies</artifactId>
      <version>${spring-cloud-alibaba.version}</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

Pay special attention to the version‑compatibility matrix between Spring Cloud and Spring Cloud Alibaba; mismatched versions often cause runtime exceptions. The article includes a compatibility diagram (image).

Component Version Mapping

The article provides a table (image) that maps each Spring Cloud Alibaba release to the corresponding versions of its internal components. When version conflicts arise, developers can refer to this table to adjust dependencies appropriately.

Summary

Spring Cloud has evolved through two major technology generations:

First generation – Eureka, Ribbon, Feign, Hystrix, implemented by Spring Cloud Netflix.

Second generation – Nacos, Sentinel, Seata, implemented by Spring Cloud Alibaba.

Spring Cloud Alibaba inherits many microservice design ideas from Spring Cloud Netflix, adds performance improvements, and is becoming the mainstream framework after Netflix’s projects entered maintenance mode. Mastering Spring Cloud Alibaba therefore offers significant benefits for building microservice applications.

References

https://sca.aliyun.com/docs/2.2.x/overview/version-explain/

https://spring.didispace.com/spring-cloud/spring-cloud-alibaba-version.html

https://juejin.cn/post/6926390930790580237