Bumping versions
This commit is contained in:
25
README.adoc
25
README.adoc
@@ -23,13 +23,12 @@ Fast forward to the cloud-era, where microservices have become prominent in the
|
||||
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.
|
||||
* Port the business logic onto message brokers (such as RabbitMQ, Apache Kafka, Amazon Kinesis).
|
||||
* Interoperate between channel-based and non-channel-based application binding scenarios to support stateless and stateful computations by using Project Reactor's Flux and Kafka Streams APIs.
|
||||
* Rely on the framework's automatic content-type support for common use-cases. Extending to different data conversion types is possible.
|
||||
* 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.
|
||||
* Port the business logic onto message brokers (such as RabbitMQ, Apache Kafka, Amazon Kinesis).
|
||||
* Interoperate between channel-based and non-channel-based application binding scenarios to support stateless and stateful computations by using Project Reactor's Flux and Kafka Streams APIs.
|
||||
* Rely on the framework's automatic content-type support for common use-cases. Extending to different data conversion types is possible.
|
||||
|
||||
== Quick Start
|
||||
|
||||
@@ -63,8 +62,14 @@ For example, you can choose Gradle as your build tool instead of Maven (the defa
|
||||
+
|
||||
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:
|
||||
+
|
||||
image::{github-raw}/docs/src/main/asciidoc/images/spring-initializr.png[Spring Initializr]
|
||||
|
||||
[%hardbreaks]
|
||||
[%hardbreaks]
|
||||
[%hardbreaks]
|
||||
image::{github-raw}/docs/src/main/asciidoc/images/spring-initializr.png[align="center"]
|
||||
|
||||
[%hardbreaks]
|
||||
[%hardbreaks]
|
||||
|
||||
. Click the *Generate Project* button.
|
||||
+
|
||||
@@ -406,4 +411,4 @@ added after the original pull request but before a merge.
|
||||
if you are fixing an existing issue please add `Fixes gh-XXXX` at the end of the commit
|
||||
message (where XXXX is the issue number).
|
||||
|
||||
// ======================================================================================
|
||||
// ======================================================================================
|
||||
2
pom.xml
2
pom.xml
@@ -8,7 +8,7 @@
|
||||
<parent>
|
||||
<groupId>org.springframework.cloud</groupId>
|
||||
<artifactId>spring-cloud-build</artifactId>
|
||||
<version>2.1.0.BUILD-SNAPSHOT</version>
|
||||
<version>2.1.0.RC3</version>
|
||||
<relativePath/>
|
||||
</parent>
|
||||
<scm>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<parent>
|
||||
<groupId>org.springframework.cloud</groupId>
|
||||
<artifactId>spring-cloud-build</artifactId>
|
||||
<version>2.1.0.BUILD-SNAPSHOT</version>
|
||||
<version>2.1.0.RC3</version>
|
||||
<relativePath />
|
||||
</parent>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user