Hi All
Intention of this mail is to discuss about API product concept and try to
evaluate how we can apply this for API Manager. As of now we can bundle
APIs together into application at API store and use them. But in this
feature we are mainly focus on API publisher side aspect of it(how
publishe
On Tue, Aug 23, 2016 at 3:07 PM, Sanjeewa Malalgoda
wrote:
> Hi All
>
> Intention of this mail is to discuss about API product concept and try to
> evaluate how we can apply this for API Manager. As of now we can bundle
> APIs together into application at API store and use them. But in this
> fea
Hi Sanjeewa,
In this case how will the API scopes be handled ?
Is it going to be per resource (similar to what we have now) or a scope
would associated for a product ? if scopes are defined per resource when a
given resource is shared between multiple products would there be an impact
?
Thanks,
Sanjeewa,
What if we think similar to creating a feature (Carbon) containing
everything need by selected API(s)?
In that approach, steps that need to happen can be summarised into:
1. create a relational mapping of an API(s) and it's associated constructs
(policies, mediation logic, custom handler
On Tue, Aug 23, 2016 at 3:07 PM, Sanjeewa Malalgoda
wrote:
> Hi All
>
> Intention of this mail is to discuss about API product concept and try to
> evaluate how we can apply this for API Manager. As of now we can bundle
> APIs together into application at API store and use them. But in this
> fea
On Tue, Aug 23, 2016 at 3:07 PM, Sanjeewa Malalgoda
wrote:
> Hi All
>
> Intention of this mail is to discuss about API product concept and try to
> evaluate how we can apply this for API Manager. As of now we can bundle
> APIs together into application at API store and use them. But in this
> fea
On Tue, Aug 23, 2016 at 3:07 PM, Sanjeewa Malalgoda
wrote:
> Hi All
>
> Intention of this mail is to discuss about API product concept and try to
> evaluate how we can apply this for API Manager. As of now we can bundle
> APIs together into application at API store and use them. But in this
> fea
Harsha,
If we take a vanilla API manager distribution and deploy an API there can
we call it an API product?
On Aug 24, 2016 9:27 AM, "Harsha Kumara" wrote:
>
>
> On Tue, Aug 23, 2016 at 3:07 PM, Sanjeewa Malalgoda
> wrote:
>
>> Hi All
>>
>> Intention of this mail is to discuss about API produc
Hi Sanjeewa,
I would like to have couple of clarifications
- When invoking an API product by the user, how will be the mediation
flow happen among the APIs?
- Are we going to allow the API product creator to define it?
On Wed, Aug 24, 2016 at 9:39 AM, Sumedha Rubasinghe
wrote:
> Har
Hi Sumedha,
On Wed, Aug 24, 2016 at 9:39 AM, Sumedha Rubasinghe
wrote:
> Harsha,
> If we take a vanilla API manager distribution and deploy an API there can
> we call it an API product?
>
I think it depends on how we define it. But according to how the market has
defined it, I think the answer t
Hi All,
Thank you for your suggestions. Please find comments in-line.
On Wed, Aug 24, 2016 at 10:33 AM, Thilini Cooray wrote:
> Hi Sanjeewa,
>
> I would like to have couple of clarifications
>
>
>- When invoking an API product by the user, how will be the mediation
>flow happen among the
Hi Pamod.
On Tue, Aug 23, 2016 at 3:38 PM, Pamod Sylvester wrote:
> Hi Sanjeewa,
>
> In this case how will the API scopes be handled ?
>
> Is it going to be per resource (similar to what we have now) or a scope
> would associated for a product ? if scopes are defined per resource when a
> given
Hi Chamara
On Tue, Aug 23, 2016 at 5:39 PM, Chamara Ariyarathne
wrote:
>
>
> On Tue, Aug 23, 2016 at 3:07 PM, Sanjeewa Malalgoda
> wrote:
>
>> Hi All
>>
>> Intention of this mail is to discuss about API product concept and try to
>> evaluate how we can apply this for API Manager. As of now we c
On Wed, Aug 24, 2016 at 11:32 AM, Sanjeewa Malalgoda
wrote:
> Hi All,
> Thank you for your suggestions. Please find comments in-line.
>
> On Wed, Aug 24, 2016 at 10:33 AM, Thilini Cooray
> wrote:
>
>> Hi Sanjeewa,
>>
>> I would like to have couple of clarifications
>>
>>
>>- When invoking an
On Tue, Aug 23, 2016 at 6:00 PM, Nuwan Dias wrote:
>
>
> On Tue, Aug 23, 2016 at 3:07 PM, Sanjeewa Malalgoda
> wrote:
>
>> Hi All
>>
>> Intention of this mail is to discuss about API product concept and try to
>> evaluate how we can apply this for API Manager. As of now we can bundle
>> APIs tog
+1 to allowing subscriptions to API products only, I dont see an advantage
in supporting both subscriptions to APIs and API products(it only
complicates things). This will also eliminate confusion for subscribers.
Yes there will be a migration effort in doing this but its worth it IMO for
the clean
Hi Sanjeewa,
On Tue, Aug 23, 2016 at 3:07 PM, Sanjeewa Malalgoda
wrote:
>
> *Requirement*
>
> As an API provider(creator or publisher), you need to create an API
> product. The API product is the mechanism through which your APIs are
> bundled and published so that developers can consume them. A
Hi Imesh,
Yes the term API Product has already been coined by the industry. It makes
sense to use this term because we allow different API products to have
different policies associated with them. So its not just a grouping of
APIs, you can have the same set of APIs grouped together with different
Thanks, Uvindra! I can only see this concept being used at [1]. Do you have
any other references?
Still, I don't think the product term is well suited for grouping APIs.
[1] http://docs.apigee.com/developer-services/content/what-api-product
On Tue, Aug 30, 2016 at 11:52 AM, Uvindra Dias Jayasinh
Alternatively we could use the term 'API Package' (analogous to a mobile
service provider package) to define a group of APIs with their own set of
policies.
On 30 August 2016 at 13:12, Imesh Gunaratne wrote:
> Thanks, Uvindra! I can only see this concept being used at [1]. Do you
> have any othe
20 matches
Mail list logo
