You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/stream-core-plugin-comparison.md
+26-5Lines changed: 26 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,24 +19,24 @@ See the License for the specific language governing permissions and
19
19
limitations under the License.
20
20
-->
21
21
22
-
# Stream Core vs Stream Plugin
22
+
# RabbitMQ Core vs Stream Plugin
23
23
24
24
## Overview {#overview}
25
25
26
-
This section covers the differences between [stream core](./streams) and the [stream plugin](./stream).
26
+
This section covers the differences between [RabbitMQ core](./streams) and the [stream plugin](./stream).
27
27
Stream core designates stream features in the broker with only default plugins activated and through protocols like AMQP 0.9.1, AMQP 1.0, MQTT, and STOMP.
28
28
29
29
30
30
### Feature Matrix
31
31
32
-
|Feature |Stream Core | Stream Plugin |
32
+
|Feature |RabbitMQ Core | Stream Plugin |
33
33
|-| ------------------------ | ------------- |
34
34
|Activation| Built-in |[Must be activated](./stream#enabling-plugin)|
35
35
|Protocol| AMQP 0.9.1 and AMQP 1.0 |[RabbitMQ Stream](https://github.com/rabbitmq/rabbitmq-server/blob/v3.12.x/deps/rabbitmq_stream/docs/PROTOCOL.adoc)|
|Offset tracking| Use external store | Built-in server-side support ([Java example](https://rabbitmq.github.io/rabbitmq-stream-java-client/snapshot/htmlsingle/#consumer-offset-tracking)) or external store |
@@ -50,9 +50,30 @@ Streams store messages using the AMQP 1.0 message format.
50
50
51
51
* RabbitMQ Stream client libraries are expected to support the AMQP 1.0 message format
52
52
* The broker handles the [conversion](./conversions) between AMQP 1.0 and AMQP 0.9.1 for AMQP 0.9.1 clients
53
-
* AMQP 0.9.1and stream clients can write to and read from the same stream, but [Sub-Entry Batching](https://rabbitmq.github.io/rabbitmq-stream-java-client/snapshot/htmlsingle/#sub-entry-batching-and-compression) is not supported.
53
+
* AMQP 0.9.1,AMQP 1.0 and stream clients can write to and read from the same stream. [Sub-Entry Batching](https://rabbitmq.github.io/rabbitmq-stream-java-client/snapshot/htmlsingle/#sub-entry-batching-and-compression) is supported without compression.
54
54
* RabbitMQ Stream supports the following section of the AMQP 1.0 message format:
Copy file name to clipboardExpand all lines: docs/streams.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ To answer these questions, streams were not introduced to replace queues but to
50
50
51
51
The following information details streams usage, and the administration and maintenance operations for streams.
52
52
53
-
You should also review the [stream plugin](./stream) information to learn more about the usage of streams with the binary RabbitMQ Stream protocol and the [stream core and stream plugin comparison page](./stream-core-plugin-comparison) for the feature matrix.
53
+
You should also review the [stream plugin](./stream) information to learn more about the usage of streams with the binary RabbitMQ Stream protocol and the [RabbitMQ core and stream plugin comparison page](./stream-core-plugin-comparison) for the feature matrix.
|Offset tracking| Use external store | Built-in server-side support ([Java example](https://rabbitmq.github.io/rabbitmq-stream-java-client/snapshot/htmlsingle/#consumer-offset-tracking)) or external store |
@@ -49,10 +49,30 @@ Stream core designates stream features in the broker with only default plugins a
49
49
Streams store messages using the AMQP 1.0 message format.
50
50
51
51
* RabbitMQ Stream client libraries are expected to support the AMQP 1.0 message format
52
-
* The broker handles the conversion between AMQP 1.0 and AMQP 0.9.1 for AMQP 0.9.1 clients
53
-
* AMQP 0.9.1and stream clients can write to and read from the same stream, but [Sub-Entry Batching](https://rabbitmq.github.io/rabbitmq-stream-java-client/snapshot/htmlsingle/#sub-entry-batching-and-compression) is not supported.
52
+
* The broker handles the [conversion](./conversions) between AMQP 1.0 and AMQP 0.9.1 for AMQP 0.9.1 clients
53
+
* AMQP 0.9.1,AMQP 1.0 and stream clients can write to and read from the same stream. [Sub-Entry Batching](https://rabbitmq.github.io/rabbitmq-stream-java-client/snapshot/htmlsingle/#sub-entry-batching-and-compression) is supported without compression.
54
54
* RabbitMQ Stream supports the following section of the AMQP 1.0 message format:
Copy file name to clipboardExpand all lines: versioned_docs/version-3.13/streams.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ To answer these questions, streams were not introduced to replace queues but to
50
50
51
51
The following information details streams usage, and the administration and maintenance operations for streams.
52
52
53
-
You should also review the [stream plugin](./stream) information to learn more about the usage of streams with the binary RabbitMQ Stream protocol and the [stream core and stream plugin comparison page](./stream-core-plugin-comparison) for the feature matrix.
53
+
You should also review the [stream plugin](./stream) information to learn more about the usage of streams with the binary RabbitMQ Stream protocol and the [RabbitMQ core and stream plugin comparison page](./stream-core-plugin-comparison) for the feature matrix.
Copy file name to clipboardExpand all lines: versioned_docs/version-4.0/stream-core-plugin-comparison.md
+26-5Lines changed: 26 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,24 +19,24 @@ See the License for the specific language governing permissions and
19
19
limitations under the License.
20
20
-->
21
21
22
-
# Stream Core vs Stream Plugin
22
+
# RabbitMQ Core vs Stream Plugin
23
23
24
24
## Overview {#overview}
25
25
26
-
This section covers the differences between [stream core](./streams) and the [stream plugin](./stream).
26
+
This section covers the differences between [RabbitMQ core](./streams) and the [stream plugin](./stream).
27
27
Stream core designates stream features in the broker with only default plugins activated and through protocols like AMQP 0.9.1, AMQP 1.0, MQTT, and STOMP.
28
28
29
29
30
30
### Feature Matrix
31
31
32
-
|Feature |Stream Core | Stream Plugin |
32
+
|Feature |RabbitMQ Core | Stream Plugin |
33
33
|-| ------------------------ | ------------- |
34
34
|Activation| Built-in |[Must be activated](./stream#enabling-plugin)|
35
35
|Protocol| AMQP 0.9.1 and AMQP 1.0 |[RabbitMQ Stream](https://github.com/rabbitmq/rabbitmq-server/blob/v3.12.x/deps/rabbitmq_stream/docs/PROTOCOL.adoc)|
|Offset tracking| Use external store | Built-in server-side support ([Java example](https://rabbitmq.github.io/rabbitmq-stream-java-client/snapshot/htmlsingle/#consumer-offset-tracking)) or external store |
@@ -50,9 +50,30 @@ Streams store messages using the AMQP 1.0 message format.
50
50
51
51
* RabbitMQ Stream client libraries are expected to support the AMQP 1.0 message format
52
52
* The broker handles the [conversion](./conversions) between AMQP 1.0 and AMQP 0.9.1 for AMQP 0.9.1 clients
53
-
* AMQP 0.9.1and stream clients can write to and read from the same stream, but [Sub-Entry Batching](https://rabbitmq.github.io/rabbitmq-stream-java-client/snapshot/htmlsingle/#sub-entry-batching-and-compression) is not supported.
53
+
* AMQP 0.9.1,AMQP 1.0 and stream clients can write to and read from the same stream. [Sub-Entry Batching](https://rabbitmq.github.io/rabbitmq-stream-java-client/snapshot/htmlsingle/#sub-entry-batching-and-compression) is supported without compression.
54
54
* RabbitMQ Stream supports the following section of the AMQP 1.0 message format:
0 commit comments