spring-cloud-stream-samples

Files

Spring Operator 0f8c257ed7 URL Cleanup

This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).

# Fixed URLs

## Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

* [ ] http://www.apache.org/licenses/ with 1 occurrences migrated to:
  https://www.apache.org/licenses/ ([https](https://www.apache.org/licenses/) result 200).
* [ ] http://www.apache.org/licenses/LICENSE-2.0 with 91 occurrences migrated to:
  https://www.apache.org/licenses/LICENSE-2.0 ([https](https://www.apache.org/licenses/LICENSE-2.0) result 200).

2019-04-24 12:53:07 -04:00

src

URL Cleanup

2019-04-24 12:53:07 -04:00

.mvn

Refactoring samples

2018-03-09 10:47:22 -05:00

docker-compose.yml

multibinder rabbit docker container name update

2018-04-25 17:31:49 -04:00

mvnw

Refactoring samples

2018-03-09 10:47:22 -05:00

mvnw.cmd

Refactoring samples

2018-03-09 10:47:22 -05:00

pom.xml

URL Cleanup

2019-04-24 12:51:53 -04:00

README.adoc

Refactoring samples

2018-03-09 10:47:22 -05:00

README.adoc

== Spring Cloud Stream Multibinder Application with Different Systems

This example shows how to run a Spring Cloud Stream application with two different binder types (Kafka and RabbitMQ)

## Running the application

The following instructions assume that you are running Kafka and RabbitMQ as a Docker images.

Go to the application root:

* `docker-compose up -d`

This brings up both Kafka and RabbitMQ clusters in docker containers.
Local ports mapped are 9092 and 5672 for Kafka and RabbitMQ respectively.

* `./mvnw clean package`

The sample comes with a convenient test producer and consumer to see the processor in action.
After running the program, watch your console, every second some data is sent to Kafka and it is received through RabbitMQ.

```
java -jar target/multibinder-0.0.1-SNAPSHOT.jar
```

You can also send data directly to Kafka topic:

`docker exec -it kafka-multibinder /opt/kafka/bin/kafka-console-producer.sh --broker-list 127.0.0.1:9092 --topic dataIn`

Enter some text and verify it comes through the console output (test consumer)

You can also go the RabbitMQ UI: `http:localhost:15672`

Once you are done testing: `docker-compose down`