Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:20
From version 4.1
edited by Erik Bakker
on 2022/06/13 10:13
Change comment: There is no comment for this version
To version 5.1
edited by Erik Bakker
on 2022/10/03 13:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -3,9 +3,6 @@
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 -* Last update: December 2021
7 -* Required reading time: 10 minutes
8 -
9 9  == 1. Prerequisites ==
10 10  
11 11  * Advanced knowledge of the eMagiz platform
... ... @@ -24,22 +24,22 @@
24 24  The following sections are helpful to understand what things to consider in selecting the right pattern.
25 25  
26 26  * **Asynchronous**
27 - * Both patterns are asynchronous in nature. In case a synchronous message is the right choice, pelase refer to the relevant microlearning that compares messaging and API gateway
24 + ** Both patterns are asynchronous in nature. In case a synchronous message is the right choice, pelase refer to the relevant microlearning that compares messaging and API gateway
28 28  * **Data**
29 - * Event Streaming solutions are typically used in large volumes of data whereby each message is relatively small. A typical example is an IoT data stream, but you can use Event Streaming for order, confirmations or other data collections. There is a maximum value for each message on a topic of 1Mb
30 - * Messaging can handle larger messages although 1 Mb message are the average that eMagiz considers. In case larger messages exist, Messaging would be a better option
26 + ** Event Streaming solutions are typically used in large volumes of data whereby each message is relatively small. A typical example is an IoT data stream, but you can use Event Streaming for order, confirmations or other data collections. There is a maximum value for each message on a topic of 1Mb
27 + ** Messaging can handle larger messages although 1 Mb message are the average that eMagiz considers. In case larger messages exist, Messaging would be a better option
31 31  * **Online vs. offline**
32 - * For Messaging, the delivering and receiving system need to be online with high availability ratio's in order to process the messages
33 - * For Event Streaming, producers and consumers can choose their own downtime and for small intervals where messages are not produces or consumed
29 + ** For Messaging, the delivering and receiving system need to be online with high availability ratio's in order to process the messages
30 + ** For Event Streaming, producers and consumers can choose their own downtime and for small intervals where messages are not produces or consumed
34 34  * **Contract & communication**
35 - * Messaging required a fixed contract between the message definitions that are exchanged. A change of definition would result in validation issues and therefore more communication is required
36 - * Event Streaming has a more loosly character in a sense that the producer defines the message that is send and publishes it to the consumer. COnsumer can then consume the message and decide how to process the message
32 + ** Messaging required a fixed contract between the message definitions that are exchanged. A change of definition would result in validation issues and therefore more communication is required
33 + ** Event Streaming has a more loosly character in a sense that the producer defines the message that is send and publishes it to the consumer. COnsumer can then consume the message and decide how to process the message
37 37  * **Technical disqualifiers**
38 - * Use Event Streaming requires the produces and the consumer to have the technical capability to produce and consume messages on a Kafka topic.
39 - * Messaging allows to receive and send messages via many more protocols such as REST, SOAP, File pickup, etc. Please note that eMagiz Messaging can also produce and consume messages from and to topics which can help to support the use of event streaming
35 + ** Use Event Streaming requires the produces and the consumer to have the technical capability to produce and consume messages on a Kafka topic.
36 + ** Messaging allows to receive and send messages via many more protocols such as REST, SOAP, File pickup, etc. Please note that eMagiz Messaging can also produce and consume messages from and to topics which can help to support the use of event streaming
40 40  * **Data Storage**
41 - * In the Messaging pattern, no data is stored and the data is in full transit
42 - * In the Event Streaming pattern, data is persisted for a short time in a storage location. The data is still considered to be in transit, but making choice where data is persisted too often with minimal change to the message could impact data storage. eMagiz has licensed limits for data storage in Event Streaming.
38 + ** In the Messaging pattern, no data is stored and the data is in full transit
39 + ** In the Event Streaming pattern, data is persisted for a short time in a storage location. The data is still considered to be in transit, but making choice where data is persisted too often with minimal change to the message could impact data storage. eMagiz has licensed limits for data storage in Event Streaming.
43 43  
44 44  == 4. Assignment ==
45 45