Skip to Content
Last modified by Waria on 2026/07/23 10:17
From version 19.1
edited by Waria
on 2026/07/23 10:17
Change comment: There is no comment for this version
To version 15.1
edited by CarlijnKokkeler
on 2024/08/29 11:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.waria
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,6 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this guide, we’ll explore key considerations for choosing between eMagiz API Gateway and eMagiz Messaging. Both patterns offer synchronous data handling, but they differ in aspects such as error management, contract requirements, and user management. We'll review these differences to help you decide which pattern best fits your integration needs.
3 -
2 +In this guide, we’ll explore key considerations for choosing between eMagiz API Gateway and eMagiz Messaging. Both patterns offer synchronous data handling, but they differ in aspects such as error management, contract requirements, and user management. We'll review these differences to help you decide which pattern best fits your integration needs. For a deeper understanding, refer to the eMagiz Fundamentals on API Gateway and Messaging.
3 +
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 6  == 1. Prerequisites ==
... ... @@ -37,8 +37,8 @@
37 37   ** For an API Gateway, the requestor needs to be able to call a REST based webservice using a supported messaging format
38 38   ** Messaging allows other web services such as SOAP, but can also handle XML for instance
39 39  * **Centralized User Management**
40 - ** API gateway offers straightforward user management to protect operations. Users can be designed in the Design phase, and various authentication methods are allowed such as OAuth 2.0, Basic Auth and API Keys. eMagiz offers easy to use configurations for that.
41 - ** For Messaging, no such user management options exist and all needs to be created manually inside the flows that handle the requests & replies.
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 that
41 + ** 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 43  == 4. Key takeaways ==
44 44  
... ... @@ -47,15 +47,11 @@
47 47  
48 48  == 5. Suggested Additional Readings ==
49 49  
50 -* [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
51 -** [[eMagiz API Gateway (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-api-gateway-introduction||target="blank"]]
52 -** [[eMagiz Messaging>>doc:Main.eMagiz Academy.Fundamentals.fundamental-messaging-introduction||target="blank"]]
50 +Take a moment to read the following [[Use Case>>doc:Main.eMagiz Academy.Use Cases.Pattern Determination.WebHome||target="blank"]]. If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following links:
53 53  * [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
54 54  ** [[Crash Course Messaging (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.WebHome||target="blank"]]
55 55  *** [[Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-introduction||target="blank"]]
56 56  ** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]]
57 57  *** [[Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-introduction||target="blank"]]
58 -* [[API Gateway (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22api+gateway%22||target="blank"]]
59 -* [[Messaging (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?highlight=true&r=1&sortOrder=desc&f_space_facet=0%2FMain.&sort=score&text=%22messaging%22&f_type=DOCUMENT&facet=true&f_locale=en&f_locale=&f_locale=en||target="blank"]]
60 -
56 +
61 61  )))((({{toc/}}))){{/container}}{{/container}}