Search: "business"

* With API Gateway we mean: A collection of RESTful API operations that can be published to the outside world to give them access to applications that are linked to your business process == 3. Finishing the Design Phase == In order to be able to move to the Create Phase and the Deploy Phase some steps need to be taken.

To learn about this topic we start with a business question to which we want an answer to make this a little bit more concrete. The business question is as follows: * What were the total sales per event?

. === 3.1 Best practices === * Use the standard as described here to correctly set up the alerting * Always stay in contact with the business, preferable as early as possible on which triggers they deem relevant * eMagiz already provides you, from the start point, with a set of relevant triggers * Always send alerts to generic mailboxes or multiple persons.

Those are used by eMagiz for separate purposes * All business tags are prefixed with Business * Use the deployment plan to tell you which alerts you might need to update based on your Production deployment [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz--deployment-plan-help.png]] === 3.2 Create or Update alerting === 1.

* With entry gate, we mean: The piece of functionality that hosts all endpoints and is responsible for checking the authentication and routing messages to the correct backend operation * With API Gateway we mean: A collection of RESTful API operations that can be published to the outside world to give them access to applications that are linked to your business process == 3. Setting up entry gate == When we talk about the API Gateway in eMagiz, the central part where all data traffic is coming in is called the entry gate.

In this test, not only developers or testers but also end-users or other people from the business side are involved. Therefore, this testing method is more functionally focused than the previously discussed tests. A User Acceptance test aims to let the business (users) accept the solution created. Normally, this is the last step before pushing the solution to production.

But as you can see in the following graph, the eMagiz environment is busy for a small amount of time and has little to do in the remainder of the time.

[[image:Main.Images.RCA-Knowledgebase.WebHome@rca-knowledgebase-aws-burst-credits-development-burst-busy-example-graph.png]] [[image:Main.Images.RCA-Knowledgebase.WebHome@rca-knowledgebase-aws-burst-credits-development-burst-impact-on-birst-credit-balance.png]] * Based on the above example, a bandwidth of 1.5 MiB/s should be sufficient to stabilize the Burst balance. * More information on the calculation can be found here: ** [[Metric math explained>>https://docs.aws.amazon.com/efs/latest/ug/monitoring-metric-math.html||target="blank"]] ** [[Using metric math>>https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/using-metric-math.html||target="blank"]] === 3.4 EFS Burst Performance & Calculation === In case of a structural problem with the throughput being used, additional investigation is warranted.

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.

As a result, this means that when one synchronous process is busy, it can even hold up other synchronous processes.

So in a sense, the webshop has taken the responsibility of handling success and failure responses. === 3.2 Asynchronous vs Synchronous === The decision to handle an integration process in a specific manner depends on various relevant business and technical checks and balances that should be answered before choosing which integration pattern to choose and then subsequently which alternative method within an integration pattern to choose.

** This release blog is small because we have been busy working on items that will be released later.

Understanding Data Pipelines == Imagine you are a global event organizer and want to track which events were hits and misses during the year. To analyze that business question you need a lot of data that tells you something about these events.