diff --git a/.DS_Store b/.DS_Store new file mode 100644 index 000000000..b1bc858e9 Binary files /dev/null and b/.DS_Store differ diff --git a/docs/.DS_Store b/docs/.DS_Store new file mode 100644 index 000000000..9a874b576 Binary files /dev/null and b/docs/.DS_Store differ diff --git a/docs/src/.DS_Store b/docs/src/.DS_Store new file mode 100644 index 000000000..7b0d36729 Binary files /dev/null and b/docs/src/.DS_Store differ diff --git a/multi/multi__binder_implementations.html b/multi/multi__binder_implementations.html new file mode 100644 index 000000000..e9d5f4145 --- /dev/null +++ b/multi/multi__binder_implementations.html @@ -0,0 +1,3 @@ + + + 16. Binder Implementations
16. Binder Implementations
Prev Part I. Preface 

16. Binder Implementations

The following is the list of available binder implementations

Prev Up 
15. Samples Home 
\ No newline at end of file diff --git a/multi/multi__quick_start.html b/multi/multi__quick_start.html index adc8bb481..28c43ba2d 100644 --- a/multi/multi__quick_start.html +++ b/multi/multi__quick_start.html @@ -8,7 +8,7 @@ When the “Cloud Stream̶ We recommend using the one you have already installed or feel more comfortable with installing and running. Also, as you can see from the Initilaizer screen, there are a few other options you can choose. For example, you can choose Gradle as your build tool instead of Maven (the default).

  • In the Artifact field, type 'logging-consumer'.

    The value of the Artifact field becomes the application name. -If you chose RabbitMQ for the middleware, your Spring Initializr should now be as follows:

    stream initializr

  • Click the Generate Project button.

    Doing so downloads the zipped version of the generated project to your hard drive.

  • Unzip the file into the folder you want to use as your project directory.
    • [Tip]Tip

    We encourage you to explore the many possibilities available in the Spring Initializr. +If you chose RabbitMQ for the middleware, your Spring Initializr should now be as follows:

    stream initializr

  • Click the Generate Project button.

    Doing so downloads the zipped version of the generated project to your hard drive.

  • Unzip the file into the folder you want to use as your project directory.
    • [Tip]Tip

    We encourage you to explore the many possibilities available in the Spring Initializr. It lets you create many different kinds of Spring applications.

    2.2 Importing the Project into Your IDE

    Now you can import the project into your IDE. Keep in mind that, depending on the IDE, you may need to follow a specific import procedure. For example, depending on how the project was generated (Maven or Gradle), you may need to follow specific import procedure (for example, in Eclipse or STS, you need to use File → Import → Maven → Existing Maven Project).

    Once imported, the project must have no errors of any kind. Also, src/main/java should contain com.example.loggingconsumer.LoggingConsumerApplication.

    Technically, at this point, you can run the application’s main class. diff --git a/multi/multi__samples.html b/multi/multi__samples.html index 5fbd677de..628cc9540 100644 --- a/multi/multi__samples.html +++ b/multi/multi__samples.html @@ -1,3 +1,3 @@ - 15. Samples

    15. Samples
    Prev Part I. Preface 

    15. Samples

    For Spring Cloud Stream samples, see the spring-cloud-stream-samples repository on GitHub.

    15.1 Deploying Stream Applications on CloudFoundry

    On CloudFoundry, services are usually exposed through a special environment variable called VCAP_SERVICES.

    When configuring your binder connections, you can use the values from an environment variable as explained on the dataflow Cloud Foundry Server docs.

    Prev Up 
    14. Metrics Emitter Home 
    \ No newline at end of file + 15. Samples
    15. Samples
    Prev Part I. Preface Next

    15. Samples

    For Spring Cloud Stream samples, see the spring-cloud-stream-samples repository on GitHub.

    15.1 Deploying Stream Applications on CloudFoundry

    On CloudFoundry, services are usually exposed through a special environment variable called VCAP_SERVICES.

    When configuring your binder connections, you can use the values from an environment variable as explained on the dataflow Cloud Foundry Server docs.

    Prev Up Next
    14. Metrics Emitter Home 16. Binder Implementations
    \ No newline at end of file diff --git a/multi/multi_spring-cloud-stream.html b/multi/multi_spring-cloud-stream.html index e373737be..39803068e 100644 --- a/multi/multi_spring-cloud-stream.html +++ b/multi/multi_spring-cloud-stream.html @@ -1,3 +1,3 @@ - Spring Cloud Stream Reference Guide
    Spring Cloud Stream Reference Guide
       Next

    Spring Cloud Stream Reference Guide

    Authors

    Sabby Anandan, Marius Bogoevici, Eric Bottard, Mark Fisher, Ilayaperumal Gopinathan, Gunnar Hillert, Mark Pollack, Patrick Peralta, Glenn Renfro, Thomas Risberg, Dave Syer, David Turanski, Janne Valkealahti, Benjamin Klein, Vinicius Carvalho, Gary Russell, Oleg Zhurakousky, Jay Bryant

    Table of Contents

    I. Preface
    1. A Brief History of Spring’s Data Integration Journey
    2. Quick Start
    2.1. Creating a Sample Application by Using Spring Initializr
    2.2. Importing the Project into Your IDE
    2.3. Adding a Message Handler, Building, and Running
    3. What’s New in 2.0?
    3.1. New Features and Components
    3.2. Notable Enhancements
    3.2.1. Both Actuator and Web Dependencies Are Now Optional
    3.2.2. Content-type Negotiation Improvements
    3.3. Notable Deprecations
    3.3.1. Java Serialization (Java Native and Kryo)
    3.3.2. Deprecated Classes and Methods
    4. Introducing Spring Cloud Stream
    5. Main Concepts
    5.1. Application Model
    5.1.1. Fat JAR
    5.2. The Binder Abstraction
    5.3. Persistent Publish-Subscribe Support
    5.4. Consumer Groups
    5.5. Consumer Types
    5.5.1. Durability
    5.6. Partitioning Support
    6. Programming Model
    6.1. Destination Binders
    6.2. Destination Bindings
    6.3. Producing and Consuming Messages
    6.3.1. Spring Integration Support
    6.3.2. Using @StreamListener Annotation
    6.3.3. Using @StreamListener for Content-based routing
    6.3.4. Spring Cloud Function support
    Functional Composition
    6.3.5. Using Polled Consumers
    Overview
    Handling Errors
    6.4. Error Handling
    6.4.1. Application Error Handling
    6.4.2. System Error Handling
    Drop Failed Messages
    DLQ - Dead Letter Queue
    Re-queue Failed Messages
    6.4.3. Retry Template
    6.5. Reactive Programming Support
    6.5.1. Reactor-based Handlers
    6.5.2. Reactive Sources
    7. Binders
    7.1. Producers and Consumers
    7.2. Binder SPI
    7.3. Binder Detection
    7.3.1. Classpath Detection
    7.4. Multiple Binders on the Classpath
    7.5. Connecting to Multiple Systems
    7.6. Binding visualization and control
    7.7. Binder Configuration Properties
    8. Configuration Options
    8.1. Binding Service Properties
    8.2. Binding Properties
    8.2.1. Common Binding Properties
    8.2.2. Consumer Properties
    8.2.3. Producer Properties
    8.3. Using Dynamically Bound Destinations
    9. Content Type Negotiation
    9.1. Mechanics
    9.1.1. Content Type versus Argument Type
    9.1.2. Message Converters
    9.2. Provided MessageConverters
    9.3. User-defined Message Converters
    10. Schema Evolution Support
    10.1. Schema Registry Client
    10.1.1. Schema Registry Client Properties
    10.2. Avro Schema Registry Client Message Converters
    10.2.1. Avro Schema Registry Message Converter Properties
    10.3. Apache Avro Message Converters
    10.4. Converters with Schema Support
    10.5. Schema Registry Server
    10.5.1. Schema Registry Server API
    Registering a New Schema
    Retrieving an Existing Schema by Subject, Format, and Version
    Retrieving an Existing Schema by Subject and Format
    Retrieving an Existing Schema by ID
    Deleting a Schema by Subject, Format, and Version
    Deleting a Schema by ID
    Deleting a Schema by Subject
    10.5.2. Using Confluent’s Schema Registry
    10.6. Schema Registration and Resolution
    10.6.1. Schema Registration Process (Serialization)
    10.6.2. Schema Resolution Process (Deserialization)
    11. Inter-Application Communication
    11.1. Connecting Multiple Application Instances
    11.2. Instance Index and Instance Count
    11.3. Partitioning
    11.3.1. Configuring Output Bindings for Partitioning
    11.3.2. Configuring Input Bindings for Partitioning
    12. Testing
    12.1. Disabling the Test Binder Autoconfiguration
    13. Health Indicator
    14. Metrics Emitter
    15. Samples
    15.1. Deploying Stream Applications on CloudFoundry
       Next
       Part I. Preface
    \ No newline at end of file + Spring Cloud Stream Reference Guide
    Spring Cloud Stream Reference Guide
       Next

    Spring Cloud Stream Reference Guide

    Authors

    Sabby Anandan, Marius Bogoevici, Eric Bottard, Mark Fisher, Ilayaperumal Gopinathan, Gunnar Hillert, Mark Pollack, Patrick Peralta, Glenn Renfro, Thomas Risberg, Dave Syer, David Turanski, Janne Valkealahti, Benjamin Klein, Vinicius Carvalho, Gary Russell, Oleg Zhurakousky, Jay Bryant

    Table of Contents

    I. Preface
    1. A Brief History of Spring’s Data Integration Journey
    2. Quick Start
    2.1. Creating a Sample Application by Using Spring Initializr
    2.2. Importing the Project into Your IDE
    2.3. Adding a Message Handler, Building, and Running
    3. What’s New in 2.0?
    3.1. New Features and Components
    3.2. Notable Enhancements
    3.2.1. Both Actuator and Web Dependencies Are Now Optional
    3.2.2. Content-type Negotiation Improvements
    3.3. Notable Deprecations
    3.3.1. Java Serialization (Java Native and Kryo)
    3.3.2. Deprecated Classes and Methods
    4. Introducing Spring Cloud Stream
    5. Main Concepts
    5.1. Application Model
    5.1.1. Fat JAR
    5.2. The Binder Abstraction
    5.3. Persistent Publish-Subscribe Support
    5.4. Consumer Groups
    5.5. Consumer Types
    5.5.1. Durability
    5.6. Partitioning Support
    6. Programming Model
    6.1. Destination Binders
    6.2. Destination Bindings
    6.3. Producing and Consuming Messages
    6.3.1. Spring Integration Support
    6.3.2. Using @StreamListener Annotation
    6.3.3. Using @StreamListener for Content-based routing
    6.3.4. Spring Cloud Function support
    Functional Composition
    6.3.5. Using Polled Consumers
    Overview
    Handling Errors
    6.4. Error Handling
    6.4.1. Application Error Handling
    6.4.2. System Error Handling
    Drop Failed Messages
    DLQ - Dead Letter Queue
    Re-queue Failed Messages
    6.4.3. Retry Template
    6.5. Reactive Programming Support
    6.5.1. Reactor-based Handlers
    6.5.2. Reactive Sources
    7. Binders
    7.1. Producers and Consumers
    7.2. Binder SPI
    7.3. Binder Detection
    7.3.1. Classpath Detection
    7.4. Multiple Binders on the Classpath
    7.5. Connecting to Multiple Systems
    7.6. Binding visualization and control
    7.7. Binder Configuration Properties
    8. Configuration Options
    8.1. Binding Service Properties
    8.2. Binding Properties
    8.2.1. Common Binding Properties
    8.2.2. Consumer Properties
    8.2.3. Producer Properties
    8.3. Using Dynamically Bound Destinations
    9. Content Type Negotiation
    9.1. Mechanics
    9.1.1. Content Type versus Argument Type
    9.1.2. Message Converters
    9.2. Provided MessageConverters
    9.3. User-defined Message Converters
    10. Schema Evolution Support
    10.1. Schema Registry Client
    10.1.1. Schema Registry Client Properties
    10.2. Avro Schema Registry Client Message Converters
    10.2.1. Avro Schema Registry Message Converter Properties
    10.3. Apache Avro Message Converters
    10.4. Converters with Schema Support
    10.5. Schema Registry Server
    10.5.1. Schema Registry Server API
    Registering a New Schema
    Retrieving an Existing Schema by Subject, Format, and Version
    Retrieving an Existing Schema by Subject and Format
    Retrieving an Existing Schema by ID
    Deleting a Schema by Subject, Format, and Version
    Deleting a Schema by ID
    Deleting a Schema by Subject
    10.5.2. Using Confluent’s Schema Registry
    10.6. Schema Registration and Resolution
    10.6.1. Schema Registration Process (Serialization)
    10.6.2. Schema Resolution Process (Deserialization)
    11. Inter-Application Communication
    11.1. Connecting Multiple Application Instances
    11.2. Instance Index and Instance Count
    11.3. Partitioning
    11.3.1. Configuring Output Bindings for Partitioning
    11.3.2. Configuring Input Bindings for Partitioning
    12. Testing
    12.1. Disabling the Test Binder Autoconfiguration
    13. Health Indicator
    14. Metrics Emitter
    15. Samples
    15.1. Deploying Stream Applications on CloudFoundry
    16. Binder Implementations
       Next
       Part I. Preface
    \ No newline at end of file diff --git a/single/spring-cloud-stream.html b/single/spring-cloud-stream.html index 87da5012f..e0b1cc0c1 100644 --- a/single/spring-cloud-stream.html +++ b/single/spring-cloud-stream.html @@ -1,6 +1,6 @@ - Spring Cloud Stream Reference Guide

    Spring Cloud Stream Reference Guide

    Authors

    Sabby Anandan, Marius Bogoevici, Eric Bottard, Mark Fisher, Ilayaperumal Gopinathan, Gunnar Hillert, Mark Pollack, Patrick Peralta, Glenn Renfro, Thomas Risberg, Dave Syer, David Turanski, Janne Valkealahti, Benjamin Klein, Vinicius Carvalho, Gary Russell, Oleg Zhurakousky, Jay Bryant

    Table of Contents

    I. Preface
    1. A Brief History of Spring’s Data Integration Journey
    2. Quick Start
    2.1. Creating a Sample Application by Using Spring Initializr
    2.2. Importing the Project into Your IDE
    2.3. Adding a Message Handler, Building, and Running
    3. What’s New in 2.0?
    3.1. New Features and Components
    3.2. Notable Enhancements
    3.2.1. Both Actuator and Web Dependencies Are Now Optional
    3.2.2. Content-type Negotiation Improvements
    3.3. Notable Deprecations
    3.3.1. Java Serialization (Java Native and Kryo)
    3.3.2. Deprecated Classes and Methods
    4. Introducing Spring Cloud Stream
    5. Main Concepts
    5.1. Application Model
    5.1.1. Fat JAR
    5.2. The Binder Abstraction
    5.3. Persistent Publish-Subscribe Support
    5.4. Consumer Groups
    5.5. Consumer Types
    5.5.1. Durability
    5.6. Partitioning Support
    6. Programming Model
    6.1. Destination Binders
    6.2. Destination Bindings
    6.3. Producing and Consuming Messages
    6.3.1. Spring Integration Support
    6.3.2. Using @StreamListener Annotation
    6.3.3. Using @StreamListener for Content-based routing
    6.3.4. Spring Cloud Function support
    Functional Composition
    6.3.5. Using Polled Consumers
    Overview
    Handling Errors
    6.4. Error Handling
    6.4.1. Application Error Handling
    6.4.2. System Error Handling
    Drop Failed Messages
    DLQ - Dead Letter Queue
    Re-queue Failed Messages
    6.4.3. Retry Template
    6.5. Reactive Programming Support
    6.5.1. Reactor-based Handlers
    6.5.2. Reactive Sources
    7. Binders
    7.1. Producers and Consumers
    7.2. Binder SPI
    7.3. Binder Detection
    7.3.1. Classpath Detection
    7.4. Multiple Binders on the Classpath
    7.5. Connecting to Multiple Systems
    7.6. Binding visualization and control
    7.7. Binder Configuration Properties
    8. Configuration Options
    8.1. Binding Service Properties
    8.2. Binding Properties
    8.2.1. Common Binding Properties
    8.2.2. Consumer Properties
    8.2.3. Producer Properties
    8.3. Using Dynamically Bound Destinations
    9. Content Type Negotiation
    9.1. Mechanics
    9.1.1. Content Type versus Argument Type
    9.1.2. Message Converters
    9.2. Provided MessageConverters
    9.3. User-defined Message Converters
    10. Schema Evolution Support
    10.1. Schema Registry Client
    10.1.1. Schema Registry Client Properties
    10.2. Avro Schema Registry Client Message Converters
    10.2.1. Avro Schema Registry Message Converter Properties
    10.3. Apache Avro Message Converters
    10.4. Converters with Schema Support
    10.5. Schema Registry Server
    10.5.1. Schema Registry Server API
    Registering a New Schema
    Retrieving an Existing Schema by Subject, Format, and Version
    Retrieving an Existing Schema by Subject and Format
    Retrieving an Existing Schema by ID
    Deleting a Schema by Subject, Format, and Version
    Deleting a Schema by ID
    Deleting a Schema by Subject
    10.5.2. Using Confluent’s Schema Registry
    10.6. Schema Registration and Resolution
    10.6.1. Schema Registration Process (Serialization)
    10.6.2. Schema Resolution Process (Deserialization)
    11. Inter-Application Communication
    11.1. Connecting Multiple Application Instances
    11.2. Instance Index and Instance Count
    11.3. Partitioning
    11.3.1. Configuring Output Bindings for Partitioning
    11.3.2. Configuring Input Bindings for Partitioning
    12. Testing
    12.1. Disabling the Test Binder Autoconfiguration
    13. Health Indicator
    14. Metrics Emitter
    15. Samples
    15.1. Deploying Stream Applications on CloudFoundry

    Part I. Preface

    1. A Brief History of Spring’s Data Integration Journey

    Spring’s journey on Data Integration started with Spring Integration. With its programming model, it provided a consistent developer experience to build applications that can embrace Enterprise Integration Patterns to connect with external systems such as, databases, message brokers, and among others.

    Fast forward to the cloud-era, where microservices have become prominent in the enterprise setting. Spring Boot transformed the way how developers built Applications. With Spring’s programming model and the runtime responsibilities handled by Spring Boot, it became seamless to develop stand-alone, production-grade Spring-based microservices.

    To extend this to Data Integration workloads, Spring Integration and Spring Boot were put together into a new project. Spring Cloud Stream was born.

    With Spring Cloud Stream, developers can: + Spring Cloud Stream Reference Guide

    Spring Cloud Stream Reference Guide

    Authors

    Sabby Anandan, Marius Bogoevici, Eric Bottard, Mark Fisher, Ilayaperumal Gopinathan, Gunnar Hillert, Mark Pollack, Patrick Peralta, Glenn Renfro, Thomas Risberg, Dave Syer, David Turanski, Janne Valkealahti, Benjamin Klein, Vinicius Carvalho, Gary Russell, Oleg Zhurakousky, Jay Bryant

    Table of Contents

    I. Preface
    1. A Brief History of Spring’s Data Integration Journey
    2. Quick Start
    2.1. Creating a Sample Application by Using Spring Initializr
    2.2. Importing the Project into Your IDE
    2.3. Adding a Message Handler, Building, and Running
    3. What’s New in 2.0?
    3.1. New Features and Components
    3.2. Notable Enhancements
    3.2.1. Both Actuator and Web Dependencies Are Now Optional
    3.2.2. Content-type Negotiation Improvements
    3.3. Notable Deprecations
    3.3.1. Java Serialization (Java Native and Kryo)
    3.3.2. Deprecated Classes and Methods
    4. Introducing Spring Cloud Stream
    5. Main Concepts
    5.1. Application Model
    5.1.1. Fat JAR
    5.2. The Binder Abstraction
    5.3. Persistent Publish-Subscribe Support
    5.4. Consumer Groups
    5.5. Consumer Types
    5.5.1. Durability
    5.6. Partitioning Support
    6. Programming Model
    6.1. Destination Binders
    6.2. Destination Bindings
    6.3. Producing and Consuming Messages
    6.3.1. Spring Integration Support
    6.3.2. Using @StreamListener Annotation
    6.3.3. Using @StreamListener for Content-based routing
    6.3.4. Spring Cloud Function support
    Functional Composition
    6.3.5. Using Polled Consumers
    Overview
    Handling Errors
    6.4. Error Handling
    6.4.1. Application Error Handling
    6.4.2. System Error Handling
    Drop Failed Messages
    DLQ - Dead Letter Queue
    Re-queue Failed Messages
    6.4.3. Retry Template
    6.5. Reactive Programming Support
    6.5.1. Reactor-based Handlers
    6.5.2. Reactive Sources
    7. Binders
    7.1. Producers and Consumers
    7.2. Binder SPI
    7.3. Binder Detection
    7.3.1. Classpath Detection
    7.4. Multiple Binders on the Classpath
    7.5. Connecting to Multiple Systems
    7.6. Binding visualization and control
    7.7. Binder Configuration Properties
    8. Configuration Options
    8.1. Binding Service Properties
    8.2. Binding Properties
    8.2.1. Common Binding Properties
    8.2.2. Consumer Properties
    8.2.3. Producer Properties
    8.3. Using Dynamically Bound Destinations
    9. Content Type Negotiation
    9.1. Mechanics
    9.1.1. Content Type versus Argument Type
    9.1.2. Message Converters
    9.2. Provided MessageConverters
    9.3. User-defined Message Converters
    10. Schema Evolution Support
    10.1. Schema Registry Client
    10.1.1. Schema Registry Client Properties
    10.2. Avro Schema Registry Client Message Converters
    10.2.1. Avro Schema Registry Message Converter Properties
    10.3. Apache Avro Message Converters
    10.4. Converters with Schema Support
    10.5. Schema Registry Server
    10.5.1. Schema Registry Server API
    Registering a New Schema
    Retrieving an Existing Schema by Subject, Format, and Version
    Retrieving an Existing Schema by Subject and Format
    Retrieving an Existing Schema by ID
    Deleting a Schema by Subject, Format, and Version
    Deleting a Schema by ID
    Deleting a Schema by Subject
    10.5.2. Using Confluent’s Schema Registry
    10.6. Schema Registration and Resolution
    10.6.1. Schema Registration Process (Serialization)
    10.6.2. Schema Resolution Process (Deserialization)
    11. Inter-Application Communication
    11.1. Connecting Multiple Application Instances
    11.2. Instance Index and Instance Count
    11.3. Partitioning
    11.3.1. Configuring Output Bindings for Partitioning
    11.3.2. Configuring Input Bindings for Partitioning
    12. Testing
    12.1. Disabling the Test Binder Autoconfiguration
    13. Health Indicator
    14. Metrics Emitter
    15. Samples
    15.1. Deploying Stream Applications on CloudFoundry
    16. Binder Implementations

    Part I. Preface

    1. A Brief History of Spring’s Data Integration Journey

    Spring’s journey on Data Integration started with Spring Integration. With its programming model, it provided a consistent developer experience to build applications that can embrace Enterprise Integration Patterns to connect with external systems such as, databases, message brokers, and among others.

    Fast forward to the cloud-era, where microservices have become prominent in the enterprise setting. Spring Boot transformed the way how developers built Applications. With Spring’s programming model and the runtime responsibilities handled by Spring Boot, it became seamless to develop stand-alone, production-grade Spring-based microservices.

    To extend this to Data Integration workloads, Spring Integration and Spring Boot were put together into a new project. Spring Cloud Stream was born.

    With Spring Cloud Stream, developers can: * Build, test, iterate, and deploy data-centric applications in isolation. * Apply modern microservices architecture patterns, including composition through messaging. * Decouple application responsibilities with event-centric thinking. An event can represent something that has happened in time, to which the downstream consumer applications can react without knowing where it originated or the producer’s identity. @@ -14,7 +14,7 @@ When the “Cloud Stream̶ We recommend using the one you have already installed or feel more comfortable with installing and running. Also, as you can see from the Initilaizer screen, there are a few other options you can choose. For example, you can choose Gradle as your build tool instead of Maven (the default).

  • In the Artifact field, type 'logging-consumer'.

    The value of the Artifact field becomes the application name. -If you chose RabbitMQ for the middleware, your Spring Initializr should now be as follows:

    stream initializr

  • Click the Generate Project button.

    Doing so downloads the zipped version of the generated project to your hard drive.

  • Unzip the file into the folder you want to use as your project directory.
    • [Tip]Tip

    We encourage you to explore the many possibilities available in the Spring Initializr. +If you chose RabbitMQ for the middleware, your Spring Initializr should now be as follows:

    stream initializr

  • Click the Generate Project button.

    Doing so downloads the zipped version of the generated project to your hard drive.

  • Unzip the file into the folder you want to use as your project directory.
    • [Tip]Tip

    We encourage you to explore the many possibilities available in the Spring Initializr. It lets you create many different kinds of Spring applications.

    2.2 Importing the Project into Your IDE

    Now you can import the project into your IDE. Keep in mind that, depending on the IDE, you may need to follow a specific import procedure. For example, depending on how the project was generated (Maven or Gradle), you may need to follow specific import procedure (for example, in Eclipse or STS, you need to use File → Import → Maven → Existing Maven Project).

    Once imported, the project must have no errors of any kind. Also, src/main/java should contain com.example.loggingconsumer.LoggingConsumerApplication.

    Technically, at this point, you can run the application’s main class. @@ -1048,4 +1048,4 @@ For example, specifying spring.integration.* captur } ] }

    [Note]Note

    Given that the format of the Metric message has slightly changed after migrating to Micrometer, the published message will also have -a STREAM_CLOUD_STREAM_VERSION header set to 2.x to help distinguish between Metric messages from the older versions of the Spring Cloud Stream.

    15. Samples

    For Spring Cloud Stream samples, see the spring-cloud-stream-samples repository on GitHub.

    15.1 Deploying Stream Applications on CloudFoundry

    On CloudFoundry, services are usually exposed through a special environment variable called VCAP_SERVICES.

    When configuring your binder connections, you can use the values from an environment variable as explained on the dataflow Cloud Foundry Server docs.

    \ No newline at end of file +a STREAM_CLOUD_STREAM_VERSION header set to 2.x to help distinguish between Metric messages from the older versions of the Spring Cloud Stream.

    15. Samples

    For Spring Cloud Stream samples, see the spring-cloud-stream-samples repository on GitHub.

    15.1 Deploying Stream Applications on CloudFoundry

    On CloudFoundry, services are usually exposed through a special environment variable called VCAP_SERVICES.

    When configuring your binder connections, you can use the values from an environment variable as explained on the dataflow Cloud Foundry Server docs.

    16. Binder Implementations

    The following is the list of available binder implementations

    \ No newline at end of file diff --git a/spring-cloud-stream.xml b/spring-cloud-stream.xml index 131f13f59..cd617733f 100644 --- a/spring-cloud-stream.xml +++ b/spring-cloud-stream.xml @@ -4,7 +4,7 @@ Spring Cloud Stream Reference Guide -2018-10-26 +2018-10-30 @@ -175,7 +175,7 @@ If you chose RabbitMQ for the middleware, your Spring Initializr should now be a - + stream initializr @@ -2869,5 +2869,29 @@ a STREAM_CLOUD_STREAM_VERSION header set to 2.xWhen configuring your binder connections, you can use the values from an environment variable as explained on the dataflow Cloud Foundry Server docs. + +Binder Implementations +The following is the list of available binder implementations + + +[RabbitMQ](https://cloud.spring.io/spring-cloud-stream-binder-rabbit/) + + +[Apache Kafka](https://cloud.spring.io/spring-cloud-stream-binder-kafka/) + + +[Amazon Kinesis](https://github.com/spring-cloud/spring-cloud-stream-binder-aws-kinesis) + + +[Google PubSub (partner maintained)](https://github.com/spring-cloud/spring-cloud-gcp/tree/master/spring-cloud-gcp-pubsub-stream-binder) + + +[Solace PubSub+ (partner maintained)](https://github.com/SolaceProducts/spring-cloud-stream-binder-solace) + + +[Azure Event Hubs (partner maintained)](https://github.com/Microsoft/spring-cloud-azure/tree/master/spring-cloud-azure-eventhub-stream-binder) + + + \ No newline at end of file