Changes for page Considerations for API Gateway or Messaging
Last modified by Erik Bakker on 2024/09/03 08:20
From version 10.1
edited by Danniar Firdausy
on 2023/10/09 08:32
on 2023/10/09 08:32
Change comment:
There is no comment for this version
To version 2.2
edited by Erik Bakker
on 2022/06/13 10:01
on 2022/06/13 10:01
Change comment:
Update document after refactoring.
Summary
-
Page properties (4 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - Considerationsfor API Gatewayor Messaging1 +advanced-keyconcepts-apigateway-message-vs-apigateway - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Default language
-
... ... @@ -1,1 +1,0 @@ 1 -en - Content
-
... ... @@ -1,8 +1,13 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 += Considerations for API Gateway 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,40 +13,55 @@ 13 13 14 14 Please refer to the following Fundamentals to learn the key concepts of both patterns 15 15 16 -* [ [eMagiz API Gateway>>doc:Main.eMagiz Academy.Fundamentals.fundamental-api-gateway-introduction||target="blank"]]17 -* [ [eMagiz Messaging>>doc:Main.eMagiz Academy.Fundamentals.fundamental-messaging-introduction||target="blank"]]21 +* [eMagiz API Gateway](../../docs/fundamental/fundamental-api-gateway-introduction) 22 +* [eMagiz Messaging](../../docs/fundamental/fundamental-event-streaming-introduction) 18 18 19 -== 3. Considerations for API Gateway or Messaging == 20 20 25 + 26 +== 3. Considerations for selecting Messaging or Event Streaming == 27 + 21 21 The following sections are helpful to understand what things to consider in selecting the right pattern. 22 22 23 23 * **Synchronous** 24 - * *Both patterns in this discussion are synchronous in nature. In case a asynchronous message is the right choice, pelase refer to the relevant microlearning that compares Messaging and Event Streaming31 + * Both patterns in this discussion are synchronous in nature. In case a asynchronous message is the right choice, pelase refer to the relevant microlearning that compares Messaging and Event Streaming 25 25 * **Data** 26 - * *Both patterns can handle similar type data - usually record based33 + * Both patterns can handle similar type data - usually record based 27 27 * **Online vs. offline** 28 - ** For Messaging, the delivering and receiving system need to be online with high availability ratio's in order to process the messages. The same is true for a backend API provider which needs to be online to provide or consume data from API operations 29 29 36 + * For Messaging, the delivering and receiving system need to be online with high availability ratio's in order to process the messages. The same is true for a backend API provider which needs to be online to provide or consume data from API operations 37 + 30 30 * **Error handling** 31 - * *In the case of an API Gateway, the requesting application needs to be handle the error messages that are returned by the API gateway in case there are any. The API Gateway provides the errors from the backend API directly back to the requestor who can then decide how to process the request.32 - * *For Messagaging, the errors that are generated are pushed inside the general error process of eMagiz and displayed in the Error Dashboard in the Manage phase. However, the requestor also gets the error messages back from the Messaging system in order to handle these properly39 + * In the case of an API Gateway, the requesting application needs to be handle the error messages that are returned by the API gateway in case there are any. The API Gateway provides the errors from the backend API directly back to the requestor who can then decide how to process the request. 40 + * For Messagaging, the errors that are generated are pushed inside the general error process of eMagiz and displayed in the Error Dashboard in the Manage phase. However, the requestor also gets the error messages back from the Messaging system in order to handle these properly 33 33 * **Contract & communication** 34 - * *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 required35 - * *For an API Gateway solution, the contract is published via the API Gateway outwards. The basic idea is that the data definition is fixed and standardized, and that requesting application will adapt their request to this definition. In that sense the API Gateway offers standardization in the landscape42 + * 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 43 + * For an API Gateway solution, the contract is published via the API Gateway outwards. The basic idea is that the data definition is fixed and standardized, and that requesting application will adapt their request to this definition. In that sense the API Gateway offers standardization in the landscape 36 36 * **Technical disqualifiers** 37 - ** For an API Gateway, the requestor needs to be able to call a REST based webservice using a supported messaging format 38 - ** Messaging allows other web services such as SOAP, but can also handle XML for instance 45 + 46 + * For an API Gateway, the requestor needs to be able to call a REST based webservice using JSON formatted messages. 47 + * Messaging allows other web services such as SOAP, but can also handle XML for instance 48 + 39 39 * **Centralized User Management** 40 - * *API gateway offers a easy to configure user management capability to protect operations. Users and roles can be designed in the Design phase, and various authentication methods are allowed such as OAuth2.0 and API Keys. eMagiz offers easy to use configurations for that41 - * *For Messaging, no such user management options exit and all needs to be created inside the flows that handle the requests & replies.50 + * API gateway offers a easy to configure user management capability to protect operations. Users and roles can be designed in the Design phase, and various authentication methods are allowed such as OAuth2.0 and API Keys. eMagiz offers easy to use configurations for that 51 + * For Messaging, no such user management options exit and all needs to be created inside the flows that handle the requests & replies. 42 42 43 -== 4. Key takeaways == 44 44 54 + 55 +== 4. Assignment == 56 + 57 +There is no assignment for now in this microlearning 58 + 59 +== 5. Key takeaways == 60 + 45 45 * There are a set of considerations to make decisions for API gateway vs. messaging 46 46 * Make sure to read the eMagiz Fundamentals properly before taking this section into account in your project 47 47 48 -== 5. Suggested Additional Readings == 49 49 50 -Take a moment to read the following [[Usecase>>doc:Main.eMagiz Academy.Use Cases.Pattern Determination.WebHome||target="blank"]] 51 51 52 -)))((({{toc/}}))){{/container}}{{/container}} 66 +== 6. Suggested Additional Readings == 67 + 68 +Take a moment to read the following link https://emagiz.github.io/docs/usecase/index_academy_usecase_pattern_discovery 69 + 70 +== 7. Silent demonstration video == 71 + 72 +As this is a more theoretical microlearning, we have no video that accompanies this microlearning.)))((({{toc/}}))){{/container}}{{/container}}