On Thu, Jan 17, 2019 at 4:20 PM gayan gunawardana <[email protected]> wrote:
> This is a great initiative. > Small clarification, can there be overlapping features between Service > Mesh and APIM such as rate limiting, end user authentication [1][2] ? > I think this is an key point. If Istio provides jwt based authentication, how does our key manager can be placed here with oauth based authentication. Does it have any advantage over the provided jwt based authentication. If Istio provides rate limiting and enable to define custom policies, how does out traffic manager can be placed in this architecture. AFAIU both do the layer7 based rate limiting. So what is the advantage of using our TM > > [1] https://istio.io/docs/tasks/policy-enforcement/rate-limiting/ > [2] https://istio.io/help/ops/security/end-user-auth/ > > Thanks, > Gayan > > On Wed, Jan 16, 2019 at 11:16 PM Youcef HILEM <[email protected]> > wrote: > >> Hi, >> Good news. >> Is there a link / dependency with the project >> https://github.com/wso2/product-vick ? >> >> Thanks >> Youcef HILEM >> >> >> >> -- >> Sent from: >> http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Architecture-f62919.html >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > Gayan > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Rajith Roshan* | Senior Software Engineer | WSO2 Inc. (m) +94-717-064-214 | (e) [email protected] <[email protected]> <https://wso2.com/signature>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
