Sync docs from master to gh-pages
This commit is contained in:
12
README.html
12
README.html
@@ -155,12 +155,12 @@ $(addBlockSwitches);
|
||||
<p>To extend this to Data Integration workloads, Spring Integration and Spring Boot were put together into a new project. Spring Cloud Stream was born.</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>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.
|
||||
<p>With Spring Cloud Stream, developers can:<br>
|
||||
* Build, test, iterate, and deploy data-centric applications in isolation.<br>
|
||||
* Apply modern microservices architecture patterns, including composition through messaging.<br>
|
||||
* 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.<br>
|
||||
* Port the business logic onto message brokers (such as RabbitMQ, Apache Kafka, Amazon Kinesis).<br>
|
||||
* 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.<br>
|
||||
* Rely on the framework’s automatic content-type support for common use-cases. Extending to different data conversion types is possible.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 80 KiB After Width: | Height: | Size: 51 KiB |
12
preface.html
12
preface.html
@@ -114,12 +114,12 @@ $(addBlockSwitches);
|
||||
<p>To extend this to Data Integration workloads, Spring Integration and Spring Boot were put together into a new project. Spring Cloud Stream was born.</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>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.
|
||||
<p>With Spring Cloud Stream, developers can:<br>
|
||||
* Build, test, iterate, and deploy data-centric applications in isolation.<br>
|
||||
* Apply modern microservices architecture patterns, including composition through messaging.<br>
|
||||
* 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.<br>
|
||||
* Port the business logic onto message brokers (such as RabbitMQ, Apache Kafka, Amazon Kinesis).<br>
|
||||
* 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.<br>
|
||||
* Rely on the framework’s automatic content-type support for common use-cases. Extending to different data conversion types is possible.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -303,12 +303,12 @@ $(addBlockSwitches);
|
||||
<p>To extend this to Data Integration workloads, Spring Integration and Spring Boot were put together into a new project. Spring Cloud Stream was born.</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>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.
|
||||
<p>With Spring Cloud Stream, developers can:<br>
|
||||
* Build, test, iterate, and deploy data-centric applications in isolation.<br>
|
||||
* Apply modern microservices architecture patterns, including composition through messaging.<br>
|
||||
* 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.<br>
|
||||
* Port the business logic onto message brokers (such as RabbitMQ, Apache Kafka, Amazon Kinesis).<br>
|
||||
* 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.<br>
|
||||
* Rely on the framework’s automatic content-type support for common use-cases. Extending to different data conversion types is possible.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user