Changes for page Considerations for API Gateway or Messaging
Last modified by Erik Bakker on 2024/09/03 08:20
From version 14.1
edited by Danniar Firdausy
on 2024/08/20 13:31
on 2024/08/20 13:31
Change comment:
There is no comment for this version
To version 15.1
edited by Carlijn Kokkeler
on 2024/08/29 11:02
on 2024/08/29 11:02
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,5 +1,5 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 -In this microlearning we'lltake amoment todiscuss severalconsiderationsfor makinghe right choice between the twopatterns2 +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 3 4 4 Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 5 5