Spring Cloud Services for VMware Tanzu

What Is Spring Cloud Services?

The rise in popularity of cloud-native architectures and the shift to implementing apps as series of focused microservices developed around bounded contexts has led to the discovery and rediscovery of patterns useful in designing distributed systems. Techniques such as service discovery, centralized configuration accessed through an app’s deployment environment, and graceful degradation of behavior through circuit breakers are common solutions for this style of architecture and can be built into tools for applying these techniques across apps.

Netflix, a pioneer in the microservices space, has built many such tools. Eureka is a service registry, which registers all of a microservice’s instances and supplies each microservice with instance information to use in discovering others. Hystrix, the Hystrix Dashboard, and Turbine provide fault tolerance using circuit breakers and enable monitoring of circuits across microservices and instances. These components have been battle-tested in a production environment facing some of the most demanding traffic requirements in the world, and are available as open-source software.

The Spring Cloud family of projects are based on Spring Boot and provide tools including Netflix’s Eureka and Hystrix as libraries easily consumable by Spring apps, following idiomatic Spring conventions. Spring Cloud Netflix makes the use of Eureka and Hystrix as simple as including starters dependencies in an app and adding an annotation to a configuration class. Spring Cloud Config includes a configuration server and client library that enable Spring apps to consume centralized configuration as series of property sources.

Spring Cloud Services for VMware Tanzu packages server-side components of Spring Cloud projects, including Spring Cloud Netflix and Spring Cloud Config, and makes them available as services in the VMware Tanzu Application Service for VMs (TAS) Marketplace. This frees you from having to implement and maintain your own managed services in order to use the included projects. You can create a Config Server, Service Registry, or Circuit Breaker Dashboard service instance on-demand, bind to it and consume its functionality, and return to focusing on the value added by your own microservices.


Spring Cloud Services currently provides the following services.

Service Type Current Version
Config Server 20
Service Registry 20
Circuit Breaker Dashboard 20

See below for the Spring Cloud Services releases that include each service version.

Service Version Tile Version
10 1.5.x
20 2.0.x–2.1.x

Product Snapshot

Element Details
Version 2.1.1
Release Date 27 November 2019
Software Component Version Spring Cloud Finchley.SR2
Compatible MySQL for VMware Tanzu Version 2.5.x and later
Compatible RabbitMQ for VMware Tanzu Version 1.6.0 and later
Compatible Ops Manager Version(s) 2.6.x and later
Compatible VMware Tanzu Application Service for VMs (TAS) Version(s) 2.6.x and later
Supported IaaS All supported by TAS


Spring Cloud Services for VMware Tanzu has the following requirements:

  • Java Cloud Foundry buildpack version 4.5 or later (if the default Java buildpack is not at version 4.5 or later, you must specify an alternate buildpack that is at version 4.5 or later when installing Spring Cloud Services; see Set Buildpack for Service Instances)
  • A MySQL service (VMware recommends MySQL for VMware Tanzu for use with Spring Cloud Services)
  • RabbitMQ for VMware Tanzu (for information about isolating the RabbitMQ cluster used for Spring Cloud Services, see Running SCS on a Dedicated RabbitMQ Cluster in the RabbitMQ for VMware Tanzu documentation)
    • If you wish to use the Circuit Breaker Dashboard service, you must enable the RabbitMQ for VMware Tanzu product’s p-rabbitmq pre-provisioned service (which uses multi-tenant VMs)
  • A single TAS SSL certificate (see the TAS documentation for information about configuring the SSL certificate) that includes the following domains, where SYS_DOMAIN.TLD is your TAS foundation’s system domain and APP_DOMAIN.TLD is your TAS foundation’s application domain:
    • *.login.SYS_DOMAIN.TLD
    • *.uaa.SYS_DOMAIN.TLD