Hi all, Since distributed caches are no longer used in C5, we thought of using this as a local cache. If the token is missing in the cache then it will be validated using the key manager. So having this as a local cache is enough for our scenario. But the only issue we have is if token is revoked from one node, then invalid token can be there in the cache of the other node. We need a way to handle that scenario maybe using notification based cache synchorinization, JMS or using small validity period for tokens. Since IS have a requirement to replicate local cache in real time, Its better to use a platform wise caching mechanism with such capability. WDYT?
Thanks! Rajith On Fri, Feb 24, 2017 at 10:22 PM, Harsha Thirimanna <[email protected]> wrote: > We also did some poc using Memcache and it is like a centralized caching > system rather than distributing cache among the nodes. And it is released > only very light weight engine and we have to implement our own way to > manage it. > Anyway, don't you guys have to replicate loca cache among the other node > in real time ? Because in that case we have to go either centralize or some > notification based local cache synchronizer mechanism. Otherwise we have to > find another solution for IS. Because we have that requirement. I think we > can try out the Redis also if we think about the the cluster. Anyway we > can't think about a distributed cache like Hazelecast again because of it > is giving lot of issues. > > *Harsha Thirimanna* > *Associate Tech Lead | WSO2* > > Email: [email protected] > Mob: +94715186770 <+94%2071%20518%206770> > Blog: http://harshathirimanna.blogspot.com/ > Twitter: http://twitter.com/harshathirimann > Linked-In: linked-in: http://www.linkedin.com/pub/ > harsha-thirimanna/10/ab8/122 > <http://wso2.com/signature> > > On Fri, Feb 24, 2017 at 1:45 PM, Uvindra Dias Jayasinha <[email protected]> > wrote: > >> Its great if we can have some feedback about this, active C5 development >> needs this moving forward. >> >> @Azeez and @Kishanthan, do we have any preferences? >> >> On 24 February 2017 at 13:12, Sagara Gunathunga <[email protected]> wrote: >> >>> >>> >>> >>> >>> >>> On Fri, Feb 24, 2017 at 7:28 AM, Uvindra Dias Jayasinha < >>> [email protected]> wrote: >>> >>>> This will function like any of the local container classes we >>>> use(example: HashMap). I think its fine to use one of the available >>>> implementations(such as Guava since we already have it as a dependency) for >>>> this. Testing will reveal its suitability but I don't anticipate any issues >>>> since this is not as complicated as a distributed cache. >>>> >>> >>> It's ok to pick one of the local cache implementations but make sure you >>> discuss with others without limiting to your own use case and pick a good >>> one so that others can use the same for their local caching requirements, >>> it's really ugly to use several local caching F/W across the platform other >>> than really exceptional cases. >>> >>> Thanks ! >>> >>>> >>>> On 16 February 2017 at 22:45, Maduranga Siriwardena <[email protected] >>>> > wrote: >>>> >>>>> Hi Rajith, >>>>> >>>>> I think this is a generic requirement for all the C5 based products >>>>> rather than for this specific use case. So we need to come up with a >>>>> solution that can be used across the platform. >>>>> >>>>> Thanks, >>>>> >>>>> On Thu, Feb 16, 2017 at 12:37 AM, Rajith Roshan <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> In C5 API Manager back end REST APIs (micro services) are protected >>>>>> using oauth2 token. Every time request comes to micro services, >>>>>> interceptor >>>>>> will validate the access token sent in the authorization header of the >>>>>> request. In order to validate the token we need to do a introspection >>>>>> call >>>>>> to the key manager. We can not do this introspection call to the key >>>>>> manager for each and every request. We need a caching layer at the >>>>>> interceptor level in order to cache the access tokens. >>>>>> >>>>>> We are going to use local cache with small cache timeout periods for >>>>>> this. What are the best caching systems we can use for this. >>>>>> We can use either JCache (javax.cache), google guava cache[1] which >>>>>> are specially used as local caches. "Memcached" [2] is also another >>>>>> option >>>>>> but mostly used in distributed systems. >>>>>> >>>>>> [1] - https://github.com/google/guava/wiki/CachesExplained >>>>>> [2] - https://memcached.org/ >>>>>> -- >>>>>> Rajith Roshan >>>>>> Software Engineer, WSO2 Inc. >>>>>> Mobile: +94-72-642-8350 <%2B94-71-554-8430> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> [email protected] >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Maduranga Siriwardena >>>>> Software Engineer >>>>> WSO2 Inc; http://wso2.com/ >>>>> >>>>> Email: [email protected] >>>>> Mobile: +94718990591 <+94%2071%20899%200591> >>>>> Blog: http://madurangasblogs.blogspot.com/ >>>>> <http://wso2.com/signature> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> Uvindra >>>> >>>> Mobile: 777733962 >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Sagara Gunathunga >>> >>> Associate Director / Architect; WSO2, Inc.; http://wso2.com >>> V.P Apache Web Services; http://ws.apache.org/ >>> Linkedin; http://www.linkedin.com/in/ssagara >>> Blog ; http://ssagara.blogspot.com >>> >>> >> >> >> -- >> Regards, >> Uvindra >> >> Mobile: 777733962 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Rajith Roshan Software Engineer, WSO2 Inc. Mobile: +94-72-642-8350 <%2B94-71-554-8430>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
