Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:20
From version 8.1
edited by Bouke Reitsma
on 2023/03/03 14:56
Change comment: There is no comment for this version
To version 7.1
edited by Erik Bakker
on 2023/01/23 11:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.BoukeReitsma
1 +XWiki.ebakker
Content
... ... @@ -34,7 +34,7 @@
34 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 required
35 35   ** 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
37 + ** For an API Gateway, the requestor needs to be able to call a REST based webservice using JSON formatted messages.
38 38   ** Messaging allows other web services such as SOAP, but can also handle XML for instance
39 39  * **Centralized User Management**
40 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