Hi All,
API Manager team planned to add complete REST API support for API
Management operations available in product.
Since initial implementation is done we are thinking about next steps of
REST service.
In this mail we need to discuss about separating API Manager store and
publisher operations.
AFAIU, It will be better to have two separate object model for both store
and publisher.
*Dhanuka Ranasinghe*
Associate TechLead
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 715381915
On Tue, Oct 13, 2015 at 10:46 PM, Sanjeewa Malalgoda
wrote:
> Hi All,
> API Manager
IMHO There should be two API definitions for Store and publisher APIs.
Mainly because even though publisher and store share some resources there
properties generally will be different e.g. data models, permissions. So
managing this in one web app will be difficult and hard to maintain.
So +1 for t
Hi Sanjeewa,
I think in terms of flexibility, cleanliness and manageability, option 1 is
better.
It gives you more control over the deployments. For example, not all
deployments are completely distributed and some of them may contain
components combined together (e.g: Gateway + Store in same JVM)
A GET on a resource returns *the* resource. All that can vary is its
requested representation (i.e. as JSON, XML,... rendering). I.e. if the GET
in Store and the GET in Publisher return different resources (i.e.
different data structures independent from their rendering) we should have
two differen
Hi Sanjeewa,
On Tue, Oct 13, 2015 at 10:46 PM, Sanjeewa Malalgoda
wrote:
> Hi All,
> API Manager team planned to add complete REST API support for API
> Management operations available in product.
> Since initial implementation is done we are thinking about next steps of
> REST service.
> In thi
Thanks Frank ,Amila, Harshana, Jo, Dhanuka for your valuable inputs.
So it seems all are agree on having 2 different APIs/web services for store
and publisher.
@Frank,Jo, actually store and publisher should return tow different data
associated with APIs.
But if need we can have common data model a
Hi Sanjeewa
On Wed, Oct 14, 2015 at 11:55 AM, Sanjeewa Malalgoda
wrote:
>
> Since we all agreed on two different services(store and publisher APIs)
> shall we conclude on data model as well.
> Do we need to have common model shared with both store,publisher and
> refine parameters at service laye
Hi Sanjeewa,
I assume Store and Publisher share the same database although they will
offer different APIs, correct? In that case, a common data model is the
preferred way.
Best regards,
Frank
2015-10-14 8:25 GMT+02:00 Sanjeewa Malalgoda :
> Thanks Frank ,Amila, Harshana, Jo, Dhanuka for your
AFAIU, It would be great to have common data model (entity model) for DAO
layer but separate data models for Service Layer (DTOs). It would be easy
to maintain having two separate layers for separate concerns.
*Dhanuka Ranasinghe*
Associate TechLead
WSO2 Inc. ; http://wso2.com
lean . enterprise .
Hi,
Please note that we will be using the existing database and backend models
currently available in API Manager. These models are common for both Store
and Publisher.
In the REST API layer, we are going to use separate DTO models (which maps
with a common model in the backend) for store and publ
Hi Frank, Dhanuka,
Yes all are shared same database and registry so underlying implementation
will not change at all. Current data access layer written in a way to have
common data model.
But implementation fill only required parameters to object based on given
criteria.
So If we take forward same
12 matches
Mail list logo
