Hi, As for the moment initially we are planning to maintain a common policy hub in the API microgateway (i.e. a common policy repository). But, it can be further developed in a developer-centric approach as well.
Thanks and regards, Prasadhi Ranasinghe. On Mon, Oct 14, 2019 at 8:17 AM Hasunie Adikari <hasu...@wso2.com> wrote: > When working with a microservice architecture, developers create many > policies to support their applications. These developer teams are often > distributed across multiple locations. It is essential to have a > centralized hub to share and collaborate on these policies. As of my point > of view, it's essential to set up a team-wide policy hab. > How could we plan to maintain a policy hub? Is it a developer-centric hub > or else do we need to maintain common policy hub in API microgateway.? > > Regards, > Hasunie > > On Sat, Oct 12, 2019 at 9:13 PM Prasadi Ranasinghe <prasad...@wso2.com> > wrote: > >> Hi Dushan, >> >> Let me further clarify the description on " Creating a Policy Hub for the >> Microgateway ". >> Here, Interceptors ( i.e. request interceptors and response interceptors >> ) which we add to the Interceptors Folder in a Microgateway project, are >> regarded as policies. >> Moreover, developers will only be able to pull policies from the policy >> repository to the toolkit. >> >> Thanks. >> >> >> On Sat, Oct 12, 2019 at 12:16 AM Dushan Silva <dush...@wso2.com> wrote: >> >>> HI Prasadi, >>> Few questions, >>> 1. When we say policies here i assume we are talking about the >>> throttling policies which we define in policy.yml? >>> 2. Will the developers be able upload the policies directly from the >>> toolkit ? or will they only be able to pull policies from the toolkit >>> >>> On Fri, Oct 11, 2019 at 10:40 AM Prasadi Ranasinghe <prasad...@wso2.com> >>> wrote: >>> >>>> Hi All, >>>> >>>> This is regarding the project which I will be working on. The objective >>>> of this project is to create a developer community around the microgateway. >>>> The problem of interest is that nowadays inconvenience is caused to >>>> developers when they are working with the microgateway and that they have >>>> to write policies according their requirements, but in that case there is a >>>> tendency of need of similar policies (i.e. Policy reuse). >>>> As the solution in this project a policy repository will be built, so >>>> that there will be a capability on the Microgateway toolkit which allows >>>> the developers to share and to reuse policies from the hub. >>>> Also as the deliverables a Policy Hub will be created. It is a web site >>>> to search, upload, list policies from the Policy Repository. Along with >>>> this email, I have attached the pdf document which contains the design >>>> diagram relevant to the project. >>>> >>>> Thanks and regards, >>>> Prasadhi Ranasinghe. >>>> >>>> -- >>>> >>>> *Prasadhi Ranasinghe * | Intern Engineering | WSO2 Inc. >>>> >>>> +94770834441 | prasad...@wso2.com >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>> >>> >>> -- >>> Best Regards >>> Dushan Silva >>> Software Engineer >>> >>> *WSO2, Inc. * >>> >>> lean . enterprise . middleware >>> Mob: +94 774 979042 >>> >> >> >> -- >> >> *Prasadhi Ranasinghe * | Intern Engineering | WSO2 Inc. >> >> +94770834441 | prasad...@wso2.com >> >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > *Hasunie Adikari* > Associate Technical Lead > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > blog http://hasuniea.blogspot.com | https://medium.com/@Hasunie/ > Mobile:+94713095876 > > -- *Prasadhi Ranasinghe * | Intern Engineering | WSO2 Inc. +94770834441 | prasad...@wso2.com
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
