Search: "business"

Business Case

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course * Access to integration model that has access to an Event Streaming license & deploy rights * Configured proper access to the training Event Broker - please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. == 2.

To start things off, we will introduce the business case in this exercise that will be used to model out the correct solution in eMagiz. ===2.1 Business Case=== **Read and understand the following business case** As Money Monkey Co. we have a fleet of trucks that hold board computers that continuously send out events.

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course == 2. Exercise == Below the exercises for this part of the crash course. === 2.1 Model the business case === Please to model the business case in Capture & Design depicting the flow of data. == 3.

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course == 2. Exercise == Below the exercises for this part of the crash course. === 2.1 Create detailed architecture === Ensure to create the rights topic configuration in terms of retention. Use the business case description for this purpose. == 3.

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course == 2.

This exercise will explain the business case used throughout all exercises linked to this Crash Course.

Prerequisites == * Have read the business case as the first exercise * Completed the previous microlearnings of this crash course == 2.

Subsequently, it is up to the consuming entities to read the data and process the data in a way that aids their business process. [[image:Main.Images.Microlearning.WebHome@crashcourse-eventstreaming-event-streaming-introduction--centralized-data-set.png]] === 3.2 Publisher and subscriber are de-coupled === Because there is a centralized managed cluster of topics to which a producer can write data without having to wait for acknowledgment of the consumer(s) you can de-couple all publishers and subscribers.

It is further up to the consumer to subscribe to that data and process it in a way that adds value to their specific business application. [[image:Main.Images.Microlearning.WebHome@crashcourse-eventstreaming-event-streaming-introduction--de-coupling-publish-subscribe.jpg]] === 3.3 Data is retained inside the platform === Because publishers and subscribers are unaware of each other a centralized piece of the puzzle needs to make sure that data is kept at that centralized location (the topic) for a certain amount of time.

Topic and Topic Properties == Within the eMagiz platform, you can use the Event Streaming pattern to help solve your business case. A crucial part of that solution is the topics and the accompanying properties.