[Fiware-technical-committee] interesting open source solution for API Management

[Joaquín Salvachúa]

Dear All,

What looks a nice way to go is to enhance the actual Wilma proxy to be compatible with some of this api publishers  (there is a lot of work going on also in fintech and banking https://www.bbvaapimarket.com <https://www.bbvaapimarket.com/> ).

Best Regards

Joaquin

> El 15 mar 2017, a las 18:04, Federico Michele Facca <federico.facca at martel-innovate.com> escribió:
> 
> Dear All,
> here is a short comparison, even though several details on APINF were not provided (so some features may be missing).
> 
> APINF
> - Provide swagger based registration for APIs (which means automatic documentation),
>   including swagger.io <http://swagger.io/> based SDK generation;
> - Provide a basic proxy that protect APIs using an API Key (details about proxy high availability are unclear) 
> - Plans to include “monetisation” aspects
> - Support developer perspective (feature/issues request on API)
> - Support provider perspective (backlog of activities on API)
> - Provide analytics on APIs
> - Its all dockerized and quick to deploy.
> 
> GRAVITEE
> - Provide swagger based registration for APIs (which means automatic documentation) 
> - Provide an advanced gateway/proxy (HA deployed) that support different policies per path, including:
>   - OAuth2
>   - Routing based on users (user x endpoint a, user y endpoint b)
>   - APIKey
>   - From XML to JSON
>   - Whitelist / Blacklist
>   - ... 
> - Provide analytics and health checks on APIs
> - Allows to define specific subscription plans with different policies (e.g. number of query per day), but there is not integrated payment
>   solution AFAIK.
> - Its all dockerized and quick to deploy.
> 
> In general my feeling is that gravitee is more mature in term of configuration policies on APIs, on the other side, it looks more oriented
> toward “private” usage, rather than building a community like in the case of APInf.
> 
> Best,
> Federico
> 
> PS: documentation is not much developed in both cases. too much coding, too little documenting ;)
> 
> Dr. Federico Michele Facca
> Head of Martel Lab
> 
> Martel Innovate
> Dorfstrasse 73 - 3073 Gümligen (Switzerland)
> 0041 78 807 58 38
> 0041 31 994 25 25
> martel-innovate.com <http://martel-innovate.com/>
> 
>> On 13 Mar 2017, at 20:43, Federico Michele Facca <federico.facca at martel-innovate.com <mailto:federico.facca at martel-innovate.com>> wrote:
>> 
>> sure!
>> Dr. Federico Michele Facca
>> Head of Martel Lab
>> 
>> Martel Innovate
>> Dorfstrasse 73 - 3073 Gümligen (Switzerland)
>> 0041 78 807 58 38
>> 0041 31 994 25 25
>> martel-innovate.com <http://martel-innovate.com/>
>> 
>>> On 13 Mar 2017, at 20:28, Juanjo Hierro <juanjose.hierro at fiware.org <mailto:juanjose.hierro at fiware.org>> wrote:
>>> 
>>> 
>>>   Please don't miss the opportunity to join the webinar from our colleagues from APInf and share your vision afterwards about how both frameworks compare!
>>> 
>>>   Cheers,
>>> 
>>>   Juanjo
>>> 
>>> On 13/03/2017 20:20, Federico Michele Facca wrote:
>>>> I recall this topic was discussed in some TSC. Not sure which activities are currently ongoing in that respect, anyhow,
>>>> I am playing with this tool:
>>>> 
>>>> https://gravitee.io/ <https://gravitee.io/>
>>>> 
>>>> and I find it quite interesting and powerful.
>>>> 
>>>> Federico
>>>> Dr. Federico Michele Facca
>>>> Head of Martel Lab
>>>> 
>>>> Martel Innovate
>>>> Dorfstrasse 73 - 3073 Gümligen (Switzerland)
>>>> 0041 78 807 58 38
>>>> 0041 31 994 25 25
>>>> martel-innovate.com <http://martel-innovate.com/>
>>>> 
>>>> 
>>>> 
>>>> __________________________________________________________________________________________
>>>> 
>>>> You can get more information about our cookies and privacy policies on the following links:
>>>> - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy <http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy>
>>>> - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE <http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE>
>>>> 
>>>> Fiware-technical-committee mailing list
>>>> Fiware-technical-committee at lists.fiware.org <mailto:Fiware-technical-committee at lists.fiware.org>
>>>> https://lists.fiware.org/listinfo/fiware-technical-committee <https://lists.fiware.org/listinfo/fiware-technical-committee>
>>>> 
>>> 
>> 
>> __________________________________________________________________________________________
>> 
>> You can get more information about our cookies and privacy policies on the following links:
>> - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy <http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy>
>> - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE <http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE>
>> 
>> Fiware-technical-committee mailing list
>> Fiware-technical-committee at lists.fiware.org <mailto:Fiware-technical-committee at lists.fiware.org>
>> https://lists.fiware.org/listinfo/fiware-technical-committee
>> 
> 
> __________________________________________________________________________________________
> 
> You can get more information about our cookies and privacy policies on the following links:
> - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy
> - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE
> 
> Fiware-technical-committee mailing list
> Fiware-technical-committee at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-technical-committee
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170315/e75e8b8f/attachment.html>