Skip to Content
Last modified by Erik Bakker on 2025/09/12 09:24
From version 8.2
edited by dfirdausy
on 2024/08/14 16:09
Change comment: There is no comment for this version
To version 2.2
edited by Erik Bakker
on 2022/06/13 10:12
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Considerations for Event Streaming or Messaging
1 +advanced-keyconcepts-eventstreaming-message-vs-eventstreaming
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,8 +1,13 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 += Considerations for Event Streaming or Messaging =
3 +
2 2  In this microlearning we'll take a moment to discuss several considerations for making the right choice between the two patterns
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
8 +* Last update: December 2021
9 +* Required reading time: 10 minutes
10 +
6 6  == 1. Prerequisites ==
7 7  
8 8  * Advanced knowledge of the eMagiz platform
... ... @@ -13,44 +13,50 @@
13 13  
14 14  Please refer to the following Fundamentals to learn the key concepts of both patterns
15 15  
16 -* [[eMagiz Event Streaming>>doc:Main.eMagiz Academy.Fundamentals.fundamental-event-streaming-introduction||target="blank"]]
17 -* [[eMagiz Messaging>>doc:Main.eMagiz Academy.Fundamentals.fundamental-messaging-introduction||target="blank"]]
21 +* [eMagiz Event Streaming](../../docs/fundamental/fundamental-event-streaming-introduction)
22 +* [eMagiz Messaging](../../docs/fundamental/fundamental-event-streaming-introduction)
18 18  
24 +
25 +
19 19  == 3. Considerations for selecting Messaging or Event Streaming ==
20 20  
21 21  The following sections are helpful to understand what things to consider in selecting the right pattern.
22 22  
23 23  * **Asynchronous**
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
31 + * 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
25 25  * **Data**
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
33 + * 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
34 + * 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
28 28  * **Online vs. offline**
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
36 + * For Messaging, the delivering and receiving system need to be online with high availability ratio's in order to process the messages
37 + * For Event Streaming, producers and consumers can choose their own downtime and for small intervals where messages are not produces or consumed
31 31  * **Contract & communication**
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
39 + * 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
40 + * 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
34 34  * **Technical disqualifiers**
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
42 + * Use Event Streaming requires the produces and the consumer to have the technical capability to produce and consume messages on a Kafka topic.
43 + * 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
37 37  * **Data Storage**
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.
45 + * In the Messaging pattern, no data is stored and the data is in full transit
46 + * 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.
40 40  
41 -== 4. Key takeaways ==
42 42  
49 +
50 +== 4. Assignment ==
51 +
52 +There is no assignment for now in this microlearning
53 +
54 +== 5. Key takeaways ==
55 +
43 43  * There are a set of considerations to make decisions for event streaming vs. messaging
44 44  * Make sure to read the eMagiz Fundamentals properly before taking this section into account in your project
45 45  
46 -== 5. Suggested Additional Readings ==
47 47  
48 -If you are interested in this topic and want more information on it please see the following links:
49 49  
50 -[[Usecase>>doc:Main.eMagiz Academy.Use Cases.Pattern Determination.WebHome||target="blank"]]
61 +== 6. Suggested Additional Readings ==
51 51  
52 -* [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
53 -** [[Crash Course Event Streaming (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.WebHome||target="blank"]]
54 -*** [[Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-event-streaming-introduction||target="blank"]]
63 +Take a moment to read the following link https://emagiz.github.io/docs/usecase/index_academy_usecase_pattern_discovery
55 55  
56 -)))((({{toc/}}))){{/container}}{{/container}}
65 +== 7. Silent demonstration video ==
66 +
67 +As this is a more theoretical microlearning, we have no video that accompanies this microlearning.)))((({{toc/}}))){{/container}}{{/container}}