Spring Cloud Connectors provides a simple abstraction for JVM-based applications running on cloud platforms to discover bound services and deployment information at runtime, and provides support for registering discovered services as Spring beans. It is based on a plugin model so that the identical compiled application can be deployed locally or on any of multiple cloud platforms, and it supports custom service definitions through Java SPI.
Spring Cloud Connectors provides out-of-the-box support for discovering common services on Heroku and Cloud Foundry clouds as well as a properties-based configuration for development and testing.
+Spring Cloud Connectors provides out-of-the-box support for discovering common services on Heroku and Cloud Foundry clouds, as well as a properties-based connector that can supply configuration for development and testing.
The core concepts used in this project are:
+The core Connectors concepts are:
+Cloud Connector |
+A platform-specific interface that identifies the presence of the platform and discovers any services bound to the application deployment. |
+
Service Connector |
+An object that represents a runtime connection to a service (for example, a |
+
Service Information |
+Information about the underlying service (such as host, port, and credentials). |
+
Application Information |
+Information about the application and the particular running instance. |
+
The project contains three major submodules.
Cloud connector: An interface specific to a cloud platform that identifies the presence of the platform and discovers any services bound to the application deployment.
+core: The core library, which is both cloud-agnostic and Spring-agnostic. It provides a programmatic entry point for developers who prefer to access cloud services and application information manually. It also provides basic service definitions for several common services (databases, message queues) and an SPI-based extension mechanism for contributing cloud and service connectors.
Service connector: An object, such as a javax.sql.DataSource, that represents a runtime connection to a service.
spring-service-connector: A Spring library that exposes application information, cloud information, and discovered services as Spring beans of the appropriate type. For example, an SQL service will be exposed as a javax.sql.DataSource, with optional connection pooling.
Service information: Information about the underlying service such as host, port, and credentials.
-Application information: Information about the application and the particular running instance.
-The project contains three major submodules:
-core: The core library, cloud- and Spring-agnostic, that provides a programmatic entry point for developers who prefer to access cloud services and application information manually. It also provides basic service definitions for several common services (databases, message queues) and an SPI-based extension mechanism to contribute cloud and service connectors.
-spring-service-connector: A Spring Library that exposes application and cloud information and discovered services as Spring beans of the appropriate type. For example, SQL services will be exposed as javax.sql.DataSource s with optional connection pooling.
Cloud connectors:
+The cloud connectors:
heroku-connector: Connector for Heroku.
localconfig-connector: Properties-based connector for manually providing configuration information for development or testing. Allows the use of the same Spring Cloud configuration wiring in all stages of application deployment.
+localconfig-connector: Properties-based connector for manually providing configuration information during development or testing. Allows use of the same Spring Cloud configuration wiring in all stages of application deployment.
See below for examples of how to include the appropriate dependencies for your build system.
+See below for examples of how to include the appropriate dependencies using your build system.